RFC 6016: Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC6016
- Published
- October 2010
- Authors
- B. Davie; F. Le Faucheur; A. Narayanan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6368Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Updated
September 2011
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 6565OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing ProtocolCurrent
June 2012
- RFC 7439Gap Analysis for Operating IPv6-Only MPLS NetworksCurrent
January 2015
- RFC 7611BGP ACCEPT_OWN Community AttributeCurrent
August 2015
- RFC 4031Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs)Current
April 2005
- RFC 4026Provider Provisioned Virtual Private Network (VPN) TerminologyCurrent
March 2005
- RFC 8049YANG Data Model for L3VPN Service DeliveryObsoleted
February 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?