draft-ietf-mpls-multicast-encaps-08.txt   draft-ietf-mpls-multicast-encaps-09.txt 
Network Working Group Toerless Eckert Network Working Group Toerless Eckert
Internet Draft Eric C. Rosen (editor) Internet Draft Eric C. Rosen (editor)
Intended Status: Standards Track Cisco Systems, Inc. Intended Status: Standards Track Cisco Systems, Inc.
Expires: October 28, 2008 Expires: November 1, 2008
Updates: RFCs 3032 and 4023 Rahul Aggarwal Updates: RFCs 3032 and 4023 Rahul Aggarwal
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
April 28, 2008 May 1, 2008
MPLS Multicast Encapsulations MPLS Multicast Encapsulations
draft-ietf-mpls-multicast-encaps-08.txt draft-ietf-mpls-multicast-encaps-09.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 3, line 46 skipping to change at page 3, line 46
In particular, there is no need for the codepoint to indicate whether In particular, there is no need for the codepoint to indicate whether
the top MPLS label is a multicast label. When the receiver of an the top MPLS label is a multicast label. When the receiver of an
MPLS packet looks up the top label, the NHLFE will specify whether MPLS packet looks up the top label, the NHLFE will specify whether
the label is a multicast label or not. the label is a multicast label or not.
This document updates RFC 3032 and RFC 4023 by re-specifying the use This document updates RFC 3032 and RFC 4023 by re-specifying the use
of the codepoints. Note that an implementation that does MPLS of the codepoints. Note that an implementation that does MPLS
multicast according to RFC 3032 and/or 4023 will be unable to multicast according to RFC 3032 and/or 4023 will be unable to
interoperate with implementations that do MPLS multicast according to interoperate with implementations that do MPLS multicast according to
this document. Any attempt to interoperate two such implementations this document. Any attempt to interoperate two such implementations
will result either in black holes or in misrouted packets. It is will result either in black holes or in misrouted packets. However,
believed though that this does not present a problem in practice. since to the best of our knowledge MPLS multicast done according to
RFC 3032 has never been deployed, it is believed though that this
does not present a problem in practice. This document specifically
deprecates the multicast data plane as specified in RFC 3032.
While RFC 3032 allows an MPLS packet to be carried in an ethernet While RFC 3032 allows an MPLS packet to be carried in an ethernet
multicast frame, it fails to specify how the Medium Access Layer multicast frame, it fails to specify how the Medium Access Layer
Destination Address (MAC DA) field is to be set in that case. This Destination Address (MAC DA) field is to be set in that case. This
document provides that specification. document provides that specification.
3. Upstream-Assigned vs. Downstream-Assigned 3. Upstream-Assigned vs. Downstream-Assigned
According to RFC 3031 [RFC3031], if two MPLS Label Switching Routers According to RFC 3031 [RFC3031], if two MPLS Label Switching Routers
(LSRs) are adjacent in a label switched path (LSP), with respect to (LSRs) are adjacent in a label switched path (LSP), with respect to
skipping to change at page 9, line 28 skipping to change at page 9, line 28
[RFC2119] "Key words for use in RFCs to Indicate Requirement [RFC2119] "Key words for use in RFCs to Indicate Requirement
[RFC3031] "Multiprotocol Label Switching Architecture", Rosen, [RFC3031] "Multiprotocol Label Switching Architecture", Rosen,
Viswanathan, Callon, January 2001 Viswanathan, Callon, January 2001
[RFC3032] "MPLS Label Stack Encoding", Rosen, et. al., January 2001 [RFC3032] "MPLS Label Stack Encoding", Rosen, et. al., January 2001
[RFC4023] "Encapsulating MPLS in IP or GRE", Worster, Rekhter, Rosen, [RFC4023] "Encapsulating MPLS in IP or GRE", Worster, Rekhter, Rosen,
[UPSTREAM] "MPLS Upstream Label Assignment and Context Specific Label [UPSTREAM] "MPLS Upstream Label Assignment and Context Specific Label
Space", Aggarwal, Rekhter, Rosen, draft-ietf-mpls-upstream- Space", Aggarwal, Rekhter, Rosen, draft-ietf-mpls-upstream-
label-04.txt, February 2008. label-05.txt, March 2008.
12. Authors' Addresses 12. Authors' Addresses
Toerless Eckert Toerless Eckert
Cisco Systems, Inc. Cisco Systems, Inc.
170 Tasman Drive 170 Tasman Drive
San Jose, CA, 95134 San Jose, CA, 95134
Email: eckert@cisco.com Email: eckert@cisco.com
Eric C. Rosen Eric C. Rosen
 End of changes. 5 change blocks. 
6 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/