Support for the Resource Reservation Protocol in Layer 3 VPNs
RFC 6016, “Support for the Resource Reservation Protocol in Layer 3 VPNs”, is a Proposed Standard document published in October 2010 by B. Davie, F. Le Faucheur, A. Narayanan. The canonical text is published by the RFC Editor.
Abstract
RFC 4364 and RFC 4659 define an approach to building provider-provisioned Layer 3 VPNs (L3VPNs) for IPv4 and IPv6. It may be desirable to use Resource Reservation Protocol (RSVP) to perform admission control on the links between Customer Edge (CE) routers and Provider Edge (PE) routers. This document specifies procedures by which RSVP messages traveling from CE to CE across an L3VPN may be appropriately handled by PE routers so that admission control can be performed on PE-CE links. Optionally, admission control across the provider's backbone may also be supported. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6016 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6015 RTP Payload Format for 1-D Interleaved Parity Forward Error Correction
- RFC 6017 Electronic Data Interchange - Internet Integration Features Header Field
- RFC 6014 Cryptographic Algorithm Identifier Allocation for DNSSEC
- RFC 6018 IPv4 and IPv6 Greynets
- RFC 6019 BinaryTime: An Alternate Format for Representing Date and Time in ASN.1
- RFC 6012 Datagram Transport Layer Security Transport Mapping for Syslog
- RFC 6020 YANG - A Data Modeling Language for the Network Configuration Protocol
- RFC 6011 Session Initiation Protocol User Agent Configuration