draft-ietf-mpls-tp-ethernet-addressing-00.txt   draft-ietf-mpls-tp-ethernet-addressing-01.txt 
MPLS D. Frost, Ed. MPLS D. Frost, Ed.
Internet-Draft S. Bryant, Ed. Internet-Draft S. Bryant, Ed.
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: July 30, 2012 M. Bocci, Ed. Expires: November 24, 2012 M. Bocci, Ed.
Alcatel-Lucent Alcatel-Lucent
January 27, 2012 May 23, 2012
MPLS-TP Next-Hop Ethernet Addressing MPLS-TP Next-Hop Ethernet Addressing
draft-ietf-mpls-tp-ethernet-addressing-00 draft-ietf-mpls-tp-ethernet-addressing-01
Abstract Abstract
The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP) The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP)
is the set of MPLS protocol functions applicable to the construction is the set of MPLS protocol functions applicable to the construction
and operation of packet-switched transport networks. This document and operation of packet-switched transport networks. This document
presents considerations for link-layer addressing of Ethernet frames presents considerations for link-layer addressing of Ethernet frames
carrying MPLS-TP packets. carrying MPLS-TP packets.
This document is a product of a joint Internet Engineering Task Force This document is a product of a joint Internet Engineering Task Force
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 30, 2012. This Internet-Draft will expire on November 24, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 17 skipping to change at page 4, line 17
destination MAC address in frames carrying MPLS-TP packets over a destination MAC address in frames carrying MPLS-TP packets over a
link that is known to be point-to-point. This may, however, lead to link that is known to be point-to-point. This may, however, lead to
excessive frame distribution and processing at the Ethernet layer. excessive frame distribution and processing at the Ethernet layer.
Broadcast traffic may also be treated specially by some devices and Broadcast traffic may also be treated specially by some devices and
this may not be desirable for MPLS-TP data frames. this may not be desirable for MPLS-TP data frames.
The approach which SHOULD be used, in view of these considerations, The approach which SHOULD be used, in view of these considerations,
is therefore to use as the destination MAC address an Ethernet is therefore to use as the destination MAC address an Ethernet
multicast address reserved for MPLS-TP for use over point-to-point multicast address reserved for MPLS-TP for use over point-to-point
links. The address allocated for this purpose by the Internet links. The address allocated for this purpose by the Internet
Assigned Numbers Authority (IANA) is 01-00-5E-XX-XX-XX. An MPLS-TP Assigned Numbers Authority (IANA) is 01-00-5E-90-00-00. An MPLS-TP
implementation MUST process Ethernet frames received over a point-to- implementation MUST process Ethernet frames received over a point-to-
point link with this destination MAC address by default. point link with this destination MAC address by default.
The use of broadcast or multicast addressing for the purpose The use of broadcast or multicast addressing for the purpose
described in this section, i.e. as a placeholder for the unknown described in this section, i.e. as a placeholder for the unknown
unicast MAC address of the destination, is applicable only when the unicast MAC address of the destination, is applicable only when the
attached Ethernet link is known to be point-to-point. If a link is attached Ethernet link is known to be point-to-point. If a link is
not known to be point-to-point, these forms of addressing MUST NOT be not known to be point-to-point, these forms of addressing MUST NOT be
used. Thus the implementation MUST provide a means for the operator used. Thus the implementation MUST provide a means for the operator
to declare that a link is point-to-point if it supports these to declare that a link is point-to-point if it supports these
skipping to change at page 5, line 5 skipping to change at page 5, line 5
and encapsulation procedures specified in [RFC5332] SHALL be used. and encapsulation procedures specified in [RFC5332] SHALL be used.
When a multipoint Ethernet link -- that is, a link which is not known When a multipoint Ethernet link -- that is, a link which is not known
to be point-to-point -- serves as a section for a point-to-point to be point-to-point -- serves as a section for a point-to-point
MPLS-TP LSP, unicast destination MAC addresses MUST be used for MPLS-TP LSP, unicast destination MAC addresses MUST be used for
Ethernet frames carrying packets of the LSP. According to the Ethernet frames carrying packets of the LSP. According to the
discussion in the previous section, this implies the use of either discussion in the previous section, this implies the use of either
static MAC address configuration or a protocol that enables peer MAC static MAC address configuration or a protocol that enables peer MAC
address discovery. address discovery.
4. MAC Address Determination via the G-ACh Advertisement Protocol 4. MAC Address Discovery via the G-ACh Advertisement Protocol
The G-ACh Advertisement Protocol (GAP) [I-D.fbb-mpls-gach-adv] The G-ACh Advertisement Protocol (GAP) [I-D.ietf-mpls-gach-adv]
provides a simple means of informing listeners on a link of the provides a simple means of informing listeners on a link of the
sender's capabilities and configuration. When used for this purpose sender's capabilities and configuration. When used for this purpose
on an Ethernet link, GAP messages are multicast to the address 01-00- on an Ethernet link, GAP messages are multicast to the address 01-00-
5e-80-00-0d. If these messages contain the unicast MAC address of 5e-80-00-0d. If these messages contain the unicast MAC address of
the sender, then listeners can learn this address and use it in the the sender, then listeners can learn this address and use it in the
future when transmitting frames containing MPLS-TP packets. Since future when transmitting frames containing MPLS-TP packets. Since
the GAP does not rely on IP, this provides a means of unicast MAC the GAP does not rely on IP, this provides a means of unicast MAC
discovery for MPLS-TP nodes without IP support. discovery for MPLS-TP nodes without IP support.
This document defines a new GAP application, "Ethernet Interface This document defines a new GAP application, "Ethernet Interface
Parameters", to support the advertisement of Ethernet-specific Parameters", to support the advertisement of Ethernet-specific
parameters associated with the sending interface. It defines several parameters associated with the sending interface. The following
Type-Length-Value (TLV) objects for this application, as follows: Type-Length-Value (TLV) objects are defined for this application:
Unicast MAC Address: The Value of this object is a canonical 48-
bit Ethernet unicast MAC address assigned to one of the interfaces
of the sender that is connected to this data link.
Maximum Frame Size: The Value of this object is 32-bit unsigned Source MAC Address: The Value of this object is a 48-bit Ethernet
integer encoded in network byte order that specifies the maximum unicast MAC address in canonical form [RFC2469] assigned to one of
frame size supported by the sending interface, in octets. the interfaces of the sender that is connected to this data link.
[Editor's note: Other objects may be added here.] MTU: The Value of this object is a 32-bit unsigned integer encoded
in network byte order that specifies the maximum transmission unit
size of the sending interface, in octets.
5. Security Considerations 5. Security Considerations
The use of broadcast or multicast Ethernet destination MAC addresses The use of broadcast or multicast Ethernet destination MAC addresses
for frames carrying MPLS-TP data packets can potentially result in for frames carrying MPLS-TP data packets can potentially result in
such frames being distributed to devices other than the intended such frames being distributed to devices other than the intended
destination node or nodes when the Ethernet link is not point-to- destination node or nodes when the Ethernet link is not point-to-
point. The operator SHOULD take care to ensure that MPLS-TP nodes point. The operator SHOULD take care to ensure that MPLS-TP nodes
are aware of the Ethernet link type (point-to-point or multipoint). are aware of the Ethernet link type (point-to-point or multipoint).
In the case of multipoint links, the operator SHOULD either ensure In the case of multipoint links, the operator SHOULD either ensure
skipping to change at page 6, line 4 skipping to change at page 5, line 46
point. The operator SHOULD take care to ensure that MPLS-TP nodes point. The operator SHOULD take care to ensure that MPLS-TP nodes
are aware of the Ethernet link type (point-to-point or multipoint). are aware of the Ethernet link type (point-to-point or multipoint).
In the case of multipoint links, the operator SHOULD either ensure In the case of multipoint links, the operator SHOULD either ensure
that no devices are attached to the link that are not authorized to that no devices are attached to the link that are not authorized to
receive the frames, or take steps to mitigate the possibility of receive the frames, or take steps to mitigate the possibility of
excessive frame distribution, for example by configuring the Ethernet excessive frame distribution, for example by configuring the Ethernet
switch to appropriately restrict the delivery of multicast frames to switch to appropriately restrict the delivery of multicast frames to
authorized ports. authorized ports.
6. IANA Considerations 6. IANA Considerations
6.1. Ethernet Multicast Address Allocation 6.1. Ethernet Multicast Address Allocation
IANA is requested to allocate an Ethernet Multicast Address from the IANA has allocated an Ethernet multicast address from the IANA
Ethernet Multicast Addresses table in the ethernet-numbers registry Multicast 48-bit MAC Addresses table in the ethernet-numbers registry
for use by MPLS-TP LSRs over point-to-point links as described in for use by MPLS-TP LSRs over point-to-point links as described in
Section 2. The entry should specify an address of the form 01-00-5E- Section 2. The allocated address is 01-00-5E-90-00-00.
XX-XX-XX, a Type Field of 8847/8848, and a usage "MPLS-TP point-to-
point (this draft)".
6.2. G-ACh Advertisement Protocol Allocation 6.2. G-ACh Advertisement Protocol Allocation
IANA is requested to allocate a new Application ID in the "G-ACh IANA is requested to allocate a new Application ID in the "G-ACh
Advertisement Protocol Applications and Data Types" registry, along Advertisement Protocol Applications" registry
with several associated data types, as follows: [I-D.ietf-mpls-gach-adv], as follows:
Application Description Type Name Type Reference Application ID Description Reference
ID ID -------------- ----------------------------- ------------
----------- ------------------- -------------------- ------ --------- 0x0001 Ethernet Interface Parameters (this draft)
(TBD) Ethernet Interface Unicast MAC Address 0 (this
Parameters draft) 6.3. Creation of Ethernet Interface Parameters Registry
Maximum Frame Size 1 (this
draft) IANA is requested to create a new registry, "G-ACh Advertisement
Protocol: Ethernet Interface Parameters", with fields and initial
allocations as follows:
Type Name Type ID Reference
------------------ ------- ------------
Source MAC Address 0 (this draft)
MTU 1 (this draft)
The range of the Type ID field is 0 - 255.
The allocation policy for this registry is Specification Required.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-mpls-gach-adv]
Frost, D., Bocci, M., and S. Bryant, "MPLS Generic
Associated Channel (G-ACh) Advertisement Protocol",
draft-ietf-mpls-gach-adv-00 (work in progress),
January 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2469] Narten, T. and C. Burton, "A Caution On The Canonical
Ordering Of Link-Layer Addresses", RFC 2469,
December 1998.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, January 2001. Encoding", RFC 3032, January 2001.
[RFC5332] Eckert, T., Rosen, E., Aggarwal, R., and Y. Rekhter, "MPLS [RFC5332] Eckert, T., Rosen, E., Aggarwal, R., and Y. Rekhter, "MPLS
Multicast Encapsulations", RFC 5332, August 2008. Multicast Encapsulations", RFC 5332, August 2008.
[RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., [RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N.,
and S. Ueno, "Requirements of an MPLS Transport Profile", and S. Ueno, "Requirements of an MPLS Transport Profile",
RFC 5654, September 2009. RFC 5654, September 2009.
[RFC5960] Frost, D., Bryant, S., and M. Bocci, "MPLS Transport [RFC5960] Frost, D., Bryant, S., and M. Bocci, "MPLS Transport
Profile Data Plane Architecture", RFC 5960, August 2010. Profile Data Plane Architecture", RFC 5960, August 2010.
7.2. Informative References 7.2. Informative References
[I-D.fbb-mpls-gach-adv]
Frost, D., Bryant, S., and M. Bocci, "MPLS Generic
Associated Channel (G-ACh) Advertisement Protocol",
draft-fbb-mpls-gach-adv-01 (work in progress),
November 2011.
[RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or [RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or
converting network protocol addresses to 48.bit Ethernet converting network protocol addresses to 48.bit Ethernet
address for transmission on Ethernet hardware", STD 37, address for transmission on Ethernet hardware", STD 37,
RFC 826, November 1982. RFC 826, November 1982.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
September 2007. September 2007.
[RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. [RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L.
 End of changes. 18 change blocks. 
37 lines changed or deleted 49 lines changed or added

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