Support for Resource Reservation Protocol Traffic Engineering in Layer 3 Virtual Private Networks
RFC 6882, “Support for Resource Reservation Protocol Traffic Engineering in Layer 3 Virtual Private Networks”, is an Experimental document published in March 2013 by K. Kumaki, T. Murai, D. Cheng, S. Matsushima, P. Jiang. The canonical text is published by the RFC Editor.
Abstract
IP Virtual Private Networks (VPNs) provide connectivity between sites across an IP/MPLS backbone. These VPNs can be operated using BGP/MPLS, and a single Provider Edge (PE) node may provide access to multiple customer sites belonging to different VPNs.
The VPNs may support a number of customer services, including RSVP and Resource Reservation Protocol Traffic Engineering (RSVP-TE) traffic. This document describes how to support RSVP-TE between customer sites when a single PE supports multiple VPNs and labels are not used to identify VPNs between PEs.
What “Experimental” means
Describes a specification that is part of a research or development effort, published so the community can gain experience with it.
The canonical text of RFC 6882 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6881 Best Current Practice for Communications Services in Support of Emergency Calling
- RFC 6883 IPv6 Guidance for Internet Content Providers and Application Service Providers
- RFC 6880 An Information Model for Kerberos Version 5
- RFC 6884 RTP Payload Format for the Enhanced Variable Rate Narrowband- Wideband Codec
- RFC 6879 IPv6 Enterprise Network Renumbering Scenarios, Considerations, and Methods
- RFC 6885 Stringprep Revision and Problem Statement for the Preparation and Comparison of Internationalized Strings
- RFC 6878 IANA Registry for the Session Initiation Protocol "Priority" Header Field
- RFC 6886 NAT Port Mapping Protocol