draft-ietf-mpls-multicast-encaps-06.txt   draft-ietf-mpls-multicast-encaps-07.txt 
Network Working Group Toerless Eckert Network Working Group Toerless Eckert
Internet Draft Eric C. Rosen (editor) Internet Draft Eric C. Rosen (editor)
Expiration Date: December 2007 Cisco Systems, Inc. Intended Status: Standards Track Cisco Systems, Inc.
Updates RFCs 3032 and 4023 Expires: May 1, 2008
Rahul Aggarwal Updates: RFCs 3032 and 4023 Rahul Aggarwal
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
November 1, 2007
MPLS Multicast Encapsulations MPLS Multicast Encapsulations
draft-ietf-mpls-multicast-encaps-06.txt draft-ietf-mpls-multicast-encaps-07.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 2, line 16 skipping to change at page 2, line 17
determined by looking up the top label, rather than by the codepoint. determined by looking up the top label, rather than by the codepoint.
RFC 3032 does not specify the destination address to be placed in the RFC 3032 does not specify the destination address to be placed in the
"MAC DA" field of an ethernet frame which carries an MPLS multicast "MAC DA" field of an ethernet frame which carries an MPLS multicast
packet. This document provides that specification. packet. This document provides that specification.
This document updates RFC 3032 and RFC 4023. This document updates RFC 3032 and RFC 4023.
Contents Contents
1 Specification of Requirements ........................... 2 1 Specification of Requirements ........................... 3
2 Introduction ............................................ 3 2 Introduction ............................................ 3
3 Upstream-Assigned vs. Downstream-Assigned ............... 4 3 Upstream-Assigned vs. Downstream-Assigned ............... 4
4 Ethernet Codepoints ..................................... 6 4 Ethernet Codepoints ..................................... 6
5 PPP Protocol Field ...................................... 6 5 PPP Protocol Field ...................................... 6
6 GRE Protocol Type ....................................... 6 6 GRE Protocol Type ....................................... 6
7 IP Protocol Number ...................................... 7 7 IP Protocol Number ...................................... 7
8 Ethernet MAC DA for Multicast MPLS ...................... 7 8 Ethernet MAC DA for Multicast MPLS ...................... 7
9 IANA Considerations ..................................... 8 9 IANA Considerations ..................................... 8
10 Security Considerations ................................. 8 10 Security Considerations ................................. 8
11 Normative References .................................... 8 11 Normative References .................................... 9
12 Informative References .................................. 9 12 Informative References .................................. 9
13 Authors' Addresses ...................................... 9 13 Authors' Addresses ...................................... 9
14 Full Copyright Statement ................................ 10 14 Full Copyright Statement ................................ 10
15 Intellectual Property ................................... 10 15 Intellectual Property ................................... 10
1. Specification of Requirements 1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
skipping to change at page 7, line 37 skipping to change at page 7, line 37
case, either all encapsulated MPLS packets in the particular tunnel case, either all encapsulated MPLS packets in the particular tunnel
have a downstream-assigned label at the top of the stack, or all have a downstream-assigned label at the top of the stack, or all
encapsulated MPLS packets in that tunnel have an upstream-assigned encapsulated MPLS packets in that tunnel have an upstream-assigned
label at the top of the stack. The means by which this is determined label at the top of the stack. The means by which this is determined
for a particular tunnel is outside the scope of this specification. for a particular tunnel is outside the scope of this specification.
8. Ethernet MAC DA for Multicast MPLS 8. Ethernet MAC DA for Multicast MPLS
When an LSR transmits a multicast MPLS packet in a multicast ethernet When an LSR transmits a multicast MPLS packet in a multicast ethernet
frame, it MUST set the Destination MAC Address to the value frame, it MUST set the Destination MAC Address to the value
01-00-5e-8a-bc-de, where abcde MUST, by default, be the twenty-bit 01-00-5e-8v-wx-yz, where vwxyz is a 20-bit (five-nibble) value set as
(five-nibble) value of the second MPLS label on the packet's label follows:
stack. By "the second label", we mean the label that is in the label
stack entry that immediately follows the topmost label stack entry. 1. vwxyz MAY be set to 0
The LSR MAY, if configured to do so, allow a a label other than the
second to be used for this purpose. However, if the MPLS packet has 2. vwxyz MAY be set to the value of one of the MPLS labels on the
only one label, the value of that label will be used instead of the packet's label stack.
value of the (non-existent) second label.
Which of these procedures is the default procedure in any particular
LSR is implementation-dependent. However, LSRs using the two
different procedures MUST interoperate. That is, an LSR MUST NOT
filter packets for which vwxyz has been set to zero, and it MUST NOT
indiscriminately filter all packets for which vwxyz has not been set
to zero.
If an LSR follows the procedure of setting vwxyz to the value of one
of the MPLS labels on the packet's label stack, and if that label
stack contains two or more labels, then by default, vwxyz MUST be set
to the value of the second MPLS label on the packet's label stack.
By "the second label", we mean the label that is in the label stack
entry that immediately follows the topmost label stack entry. The
LSR MAY, if configured to do so, allow a a label other than the
second to be used for this purpose. If the MPLS packet has only one
label, the value of that label will be used instead of the value of
the (non-existent) second label.
It is expected that the LSR will follow the procedures of [UPSTREAM], It is expected that the LSR will follow the procedures of [UPSTREAM],
pushing on two labels, with the topmost label being a "context label" pushing on two labels, with the topmost label being a "context label"
that is the same for all MPLS packets being transmitted by the LSR that is the same for all MPLS packets being transmitted by the LSR
onto the ethernet, but with the second label being different for onto the ethernet, but with the second label being different for
different LSPs. Thus if the MAC DA value is a function of the second different LSPs. Thus if the MAC DA value is a function of the second
label, more of the LSP-specific information about the packet appears label, more of the LSP-specific information about the packet appears
in the MAC DA field. However, the way in which that information is in the MAC DA field. This can be used to filter multicast packets
used, if any, is outside the scope of this document. with "unexpected" non-zero values of vwxyz. Further discussion of
such filtering or its uses is outside the scope of this document.
9. IANA Considerations 9. IANA Considerations
IANA already owns the set of ethernet multicast addresses in the IANA already owns the set of ethernet multicast addresses in the
range 01-00-5e-00-00-00 to 01-00-5e-ff-ff-ff. Addresses in the range range 01-00-5e-00-00-00 to 01-00-5e-ff-ff-ff. Addresses in the range
01-00-5e-00-00-00 to 01-00-5e-7f-ff-ff are reserved for use when an 01-00-5e-00-00-00 to 01-00-5e-7f-ff-ff are reserved for use when an
ethernet multicast frame carries an IP multicast packet. IANA shall ethernet multicast frame carries an IP multicast packet. IANA shall
reserve ethernet addresses in the range 01-00-5e-80-00-00 to reserve ethernet addresses in the range 01-00-5e-80-00-00 to
01-00-5e-8f-ff-ff for use when an ethernet multicast frame carries an 01-00-5e-8f-ff-ff for use when an ethernet multicast frame carries an
MPLS multicast packet. MPLS multicast packet.
skipping to change at page 9, line 9 skipping to change at page 9, line 19
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,
12. Informative References 12. Informative References
[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-02.txt, March 2007. label-03.txt, November 2007.
13. Authors' Addresses 13. 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
skipping to change at page 10, line 42 skipping to change at page 10, line 47
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
 End of changes. 9 change blocks. 
17 lines changed or deleted 37 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/