Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 5332

MPLS Multicast Encapsulations,August 2008

File formats:
icon for text fileicon for PDFicon for HTML
Status:
PROPOSED STANDARD
Updates:
RFC 3032,RFC 4023
Authors:
T. Eckert
E. Rosen, Ed.
R. Aggarwal
Y. Rekhter
Stream:
IETF
Source:
mpls (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5332

Discuss this RFC: Send questions or comments to the mailing listmpls@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5332


Abstract

RFC 3032 established two data link layer codepoints for MPLS, used todistinguish whether the data link layer frame is carrying an MPLSunicast or an MPLS multicast packet. However, this usage was neverdeployed. This specification updates RFC 3032 by redefining themeaning of these two codepoints. Both codepoints can now be used tocarry 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 anupstream-assigned label".

RFC 3032 does not specify the destination address to be placed in the"MAC DA" (Medium Access Layer Destination Address) field of anethernet frame that carries an MPLS multicast packet. This documentprovides that specification.

This document updates RFC 3032 and RFC 4023. [STANDARDS-TRACK]


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp