RFC 4797: Use of Provider Edge to Provider Edge (PE-PE) Generic Routing Encapsulation (GRE) or IP in BGP/MPLS IP Virtual Private Networks
In plain English — editorial summary, not part of the RFC
This document describes an implementation strategy for BGP/MPLS IP Virtual Private Networks (VPNs) in which the outermost MPLS label (i.e., the tunnel label) is replaced with either an IP header or an IP header with Generic Routing Encapsulation (GRE). The implementation strategy described herein enables the deployment of BGP/MPLS IP VPN technology in networks whose edge devices are MPLS and VPN aware, but whose interior devices are not. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4797
- Published
- January 2007
- Authors
- Y. Rekhter; R. Bonica; E. Rosen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4798Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)Current
February 2007
- RFC 4801Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) ManagementCurrent
February 2007
- RFC 4802Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information BaseCurrent
February 2007
- RFC 4803Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information BaseCurrent
February 2007
- RFC 4783GMPLS - Communication of Alarm InformationCurrent
December 2006
- RFC 4781Graceful Restart Mechanism for BGP with MPLSCurrent
January 2007
- RFC 4816Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport ServiceCurrent
February 2007
- RFC 4817Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3Current
March 2007
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?