RSVP Standards

RSVP is described in several RFCs and drafts.

The following RFCs provide an overview of RSVP and RSVP features:

• RFC 2205, Resource Reservation Protocol (RSVP), Version 1, Functional Specification
• RFC 2209, Resource Reservation Protocol (RSVP), Version 1, Message Processing Rules
• 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 2216, Network Element Service Specification Template
• RFC 2745, RSVP Diagnostic Messages
• RFC 2747, RSVP Cryptographic Authentication (see also RFC 3097)
• RFC 2961, RSVP Refresh Overhead Reduction Extensions
• RFC 3097, RSVP Cryptographic Authentication -- Updated Message Type Value (see also RFC 2747)
• RFC 3209, RSVP-TE: Extensions to RSVP for LSP Tunnels (the Junos OS does not support the Null Service Object for maximum transmission unit [MTU] signaling in RSVP)
• RFC 3473, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions (only Section 9, Fault Handling)
• RFC 3477, Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)
• RFC 4090, Fast Reroute Extensions to RSVP-TE for LSP Tunnels (except node protection in facility backup)
• RFC 4125, Maximum Allocation Bandwidth Constraints Model for Diff-Serv-aware MPLS Traffic Engineering
• RFC 4127, Russian Dolls Bandwidth Constraints Model for Diff-Serv-aware MPLS Traffic Engineering
• RFC 4203, OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) (OSPF extensions can carry traffic engineering information over unnumbered links)
• RFC 4205, Intermediate System to Intermediate System (IS-IS) Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) (IS-IS 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 Record Route Object [RRO] node ID subobject is for use in inter-AS link and node protection configurations.)

The following Internet draft also provides information about RSVP:

• Internet draft draft-ietf-mpls-rsvp-te-p2mp-01.txt, Extensions to RSVP-TE for Point to Multipoint TE LSPs (expires June 2005)

To access RFCs and drafts, go to the IETF website at http://www.ietf.org.