RFC 4023: Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)
In plain English — editorial summary, not part of the RFC
Various applications of MPLS make use of label stacks with multiple entries. In some cases, it is possible to replace the top label of the stack with an IP-based encapsulation, thereby enabling the application to run over networks that do not have MPLS enabled in their core routers. This document specifies two IP-based encapsulations: MPLS-in-IP and MPLS-in-GRE (Generic Routing Encapsulation). Each of these is applicable in some circumstances. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4023
- Published
- March 2005
- Authors
- T. Worster; Y. Rekhter; E. Rosen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
- Updated by:
- RFC 5332
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4026Provider Provisioned Virtual Private Network (VPN) TerminologyCurrent
March 2005
- RFC 4031Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs)Current
April 2005
- RFC 4003GMPLS Signaling Procedure for Egress ControlCurrent
February 2005
- RFC 4045Extensions to Support Efficient Carrying of Multicast Traffic in Layer-2 Tunneling Protocol (L2TP)Current
April 2005
- RFC 3988Maximum Transmission Unit Signalling Extensions for the Label Distribution ProtocolCurrent
February 2005
- RFC 3985Pseudo Wire Emulation Edge-to-Edge (PWE3) ArchitectureUpdated
March 2005
- RFC 3973Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)Updated
January 2005
- RFC 4090Fast Reroute Extensions to RSVP-TE for LSP TunnelsUpdated
May 2005
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?