draft-ietf-mpls-multicast-encaps-00.txt   draft-ietf-mpls-multicast-encaps-01.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: August 2006 Cisco Systems, Inc. Expiration Date: March 2007 Cisco Systems, Inc.
Updates RFCs 3032 and 4023 Updates RFCs 3032 and 4023
Rahul Aggarwal Rahul Aggarwal
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
February 2006 September 2006
MPLS Multicast Encapsulations MPLS Multicast Encapsulations
draft-ietf-mpls-multicast-encaps-00.txt draft-ietf-mpls-multicast-encaps-01.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 5, line 11 skipping to change at page 5, line 11
assigned. This means that all the receivers on the MPLS or IP assigned. This means that all the receivers on the MPLS or IP
tunnel must know a priori whether upstream-assigned or tunnel must know a priori whether upstream-assigned or
downstream-assigned labels are being used in the tunnel. How downstream-assigned labels are being used in the tunnel. How
this is known is outside the scope of this document. this is known is outside the scope of this document.
- Multipoint-to-Multipoint. A multipoint-to-multipoint link or - Multipoint-to-Multipoint. A multipoint-to-multipoint link or
tunnel associates n systems, such that any of them can transmit tunnel associates n systems, such that any of them can transmit
on the link or tunnel, and the transmissions may be received by on the link or tunnel, and the transmissions may be received by
the other n-1 systems. the other n-1 systems.
If a set of MPLS packets are transmitted on a multipoint-to- If MPLS packets are transmitted on a particular multipoint-to-
multipoint link, their top labels (before applying the data link multipoint link or tunnel, one of the following scenarios
or tunnel encapsulation) MAY be of different types, i.e., there applies:
may be a mixture of upstream-assigned and downstream-assigned top
labels.
However, if upstream-assigned labels are to be used, the data 1. It is known (by methods outside the scope of this document)
link or tunnel encapsulation MUST provide a codepoint which that the top label of every MPLS packet on the link or
specifies whether the top label of the encapsulated MPLS packet tunnel is downstream-assigned
is upstream-assigned or downstream-assigned. If a particular
type of data link or tunnel does not provide such a codepoint, 2. It is known (by methods outside the scope of this document)
then upstream-assigned labels MUST NOT be used. that the top label of every MPLS packet on the link or
tunnel is upstream-assigned
3. Some MPLS packets on the link may have upstream-assigned
top labels while some may have downstream-assigned top
labels
If (and only if) the third scenario applies, the data link or
tunnel encapsulation MUST provide a codepoint which specifies
whether the top label of the encapsulated MPLS packet is
upstream-assigned or downstream-assigned. If a particular type
of data link or tunnel does not provide such a codepoint, then
the third scenario MUST NOT be used.
The remainder of this document specifies procedures for setting the The remainder of this document specifies procedures for setting the
data link layer codepoints and address fields. data link layer codepoints and address fields.
3. Ethernet Codepoints 3. Ethernet Codepoints
Ethernet is an example of a multipoint-to-multipoint data link. Ethernet is an example of a multipoint-to-multipoint data link.
Ethertype 0x8847 is used whenever a unicast ethernet frame carries an Ethertype 0x8847 is used whenever a unicast ethernet frame carries an
MPLS packet. MPLS packet.
skipping to change at page 7, line 9 skipping to change at page 7, line 9
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.
7. Ethernet MAC DA for Multicast MPLS 7. Ethernet MAC DA for Multicast MPLS
When a multicast MPLS packet is carried in a multicast ethernet When a multicast MPLS packet is carried in a multicast ethernet
frame, the Destination MAC Address shall be set to the value 01-00- frame, the Destination MAC Address shall be set to the value 01-00-
5e-8a-bc-de, where abcde is the twenty-bit (4-nibble) value of the 5e-8a-bc-de, where abcde is the twenty-bit (5-nibble) value of the
topmost MPLS label of the MPLS packet. topmost MPLS label of the MPLS packet.
8. IANA Considerations 8. 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 01-00- 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 MPLS 5e-8f-ff-ff for use when an ethernet multicast frame carries an MPLS
 End of changes. 6 change blocks. 
15 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/