metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 6368: Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)

Still current, but amended. Parts of this document are changed or extended by RFC 7606, RFC 9494. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6368
Published
September 2011
Authors
P. Marques; R. Raszuk; K. Patel; K. Kumaki; T. Yamagata
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
14
Also known as
—
Updated by:
RFC 7606, RFC 9494

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/6368-internal-bgp-as-the-provider-customer-edge-protocol-for-bgp-mpls-ip-virtual-priv