Supported RSVP Standards

The JUNOS software substantially supports the following RSVP standards:

• 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 (updated by 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 Null Service Object for maximum transmission unit [MTU] signaling in RSVP is not supported)
• RFC 3473, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation [sic] 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 (except for node protection in facility backup)
• 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
• Internet draft draft-ietf-mpls-rsvp-te-p2mp-01.txt, Extensions to RSVP-TE for Point to Multipoint TE LSPs (expires June 2005)

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.