Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks
RFC 6368, “Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks”, is a Proposed Standard document published in September 2011 by P. Marques, R. Raszuk, K. Patel, K. Kumaki, T. Yamagata. It has since been updated by RFC 7606, RFC 9494. The canonical text is published by the RFC Editor.
Abstract
This document defines protocol extensions and procedures for BGP Provider/Customer Edge router iteration in BGP/MPLS IP VPNs. These extensions and procedures have the objective of making the usage of the BGP/MPLS IP VPN transparent to the customer network, as far as routing information is concerned. [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 6368 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6367 Addition of the Camellia Cipher Suites to Transport Layer Security
- RFC 6369 Forwarding and Control Element Separation Implementation Experience
- RFC 6366 Requirements for an Internet Audio Codec
- RFC 6370 MPLS Transport Profile Identifiers
- RFC 6365 Terminology Used in Internationalization in the IETF
- RFC 6371 Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks
- RFC 6364 Session Description Protocol Elements for the Forward Error Correction Framework
- RFC 6372 MPLS Transport Profile Survivability Framework