Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Supported RSVP Standards

Junos OS substantially supports the following RFCs and Internet drafts, which define standards for RSVP.

  • RFC 2205, Resource ReSerVation Protocol (RSVP)—Version 1 Functional Specification

  • RFC 2210, The Use of RSVP with IETF Integrated Services

  • RFC 2211, Specification of the Controlled-Load Network Element Service

  • RFC 2212, Specification of Guaranteed Quality of Service

  • RFC 2215, General Characterization Parameters for Integrated Service Network Elements

  • RFC 2745, RSVP Diagnostic Messages

  • RFC 2747, RSVP Cryptographic Authentication (updated by RFC 3097)

  • RFC 2750, RSVP Extensions for Policy Control (RFC is not supported. Fully compliant with devices that support this RFC).

  • RFC 2961, RSVP Refresh Overhead Reduction Extensions

  • RFC 3097, RSVP Cryptographic Authentication—Updated Message Type Value

  • RFC 3209, RSVP-TE: Extensions to RSVP for LSP Tunnels

    The Null Service Object for maximum transmission unit (MTU) signaling in RSVP is not supported.

  • RFC 3210, Applicability Statement for Extensions to RSVP for LSP-Tunnels

  • RFC 3473, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions

    Only Section 9, “Fault Handling,” is supported.

  • RFC 3477, Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)

  • RFC 4090, Fast Reroute Extensions to RSVP-TE for LSP Tunnels

  • RFC 4203, OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)

    (OSPF extensions can carry traffic engineering information over unnumbered links.)

  • RFC 4558, Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement

  • RFC 4561, Definition of a Record Route Object (RRO) Node-Id Sub-Object

    The RRO node ID subobject is for use in inter-AS link and node protection configurations.

  • RFC 4875, Extensions to RSVP-TE for Point-to-Multipoint TE LSPs

  • RFC 5151, Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions

  • RFC 5420, Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)

    Only the LSP_ATTRIBUTES object is supported.

  • RFC 6437, IPv6 Flow Label Specification

  • RFC 6510, Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes Objects

  • RFC 7570, Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)

  • RFC 8370, Techniques to Improve the Scalability of RSVP-TE Deployments

  • RFC 8577, Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane

  • RFC 8796, RSVP-TE Summary Fast Reroute Extensions for Label Switched Path (LSP) Tunnels

  • draft-ietf-mpls-ri-rsvp-frr-05, Refresh Interval Independent FRR Facility Protection

The following RFCs do not define standards, but provide information about RSVP and related technologies. The IETF classifies them variously as “Experimental” or “Informational.”

  • RFC 2209, Resource ReSerVation Protocol (RSVP)—Version 1 Message Processing Rules

  • RFC 2216, Network Element Service Specification Template

  • RFC 4125, Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering

  • RFC 4127, Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering

  • RFC 8577, Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane (Fully compliant)