RFC 5332: MPLS Multicast Encapsulations
In plain English — editorial summary, not part of the RFC
RFC 3032 established two data link layer codepoints for MPLS, used to distinguish whether the data link layer frame is carrying an MPLS unicast or an MPLS multicast packet. However, this usage was never deployed. This specification updates RFC 3032 by redefining the meaning of these two codepoints. Both codepoints can now be used to carry multicast packets. The second codepoint (formerly the "multicast codepoint") is now to be used only on multiaccess media, and it is to mean "the top label of the following label stack is an upstream-assigned label". RFC 3032 does not specify the destination address to be placed in the "MAC DA" (Medium Access Layer Destination Address) field of an ethernet frame that carries an MPLS multicast packet. This document provides that specification. This document updates RFC 3032 and RFC 4023. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5332
- Published
- August 2008
- Authors
- T. Eckert; E. Rosen; R. Aggarwal; Y. Rekhter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5331MPLS Upstream Label Assignment and Context-Specific Label SpaceUpdated
August 2008
- RFC 5330A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a LinkCurrent
October 2008
- RFC 5329Traffic Engineering Extensions to OSPF Version 3Current
September 2008
- RFC 5339Evaluation of Existing GMPLS Protocols against Multi-Layer and Multi-Region Networks (MLN/MRN)Current
September 2008
- RFC 5340OSPF for IPv6Updated
July 2008
- RFC 5316ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic EngineeringObsoleted
December 2008
- RFC 5311Simplified Extension of Link State PDU (LSP) Space for IS-ISCurrent
February 2009
- RFC 5310IS-IS Generic Cryptographic AuthenticationUpdated
February 2009
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?