RFC 6016
Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs, October 2010
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- B. Davie
F. Le Faucheur
A. Narayanan - Stream:
- IETF
- Source:
- tsvwg (wit)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6016
Discuss this RFC: Send questions or comments to the mailing list tsvwg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6016
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.