--- 1/draft-ietf-mpls-tp-ethernet-addressing-02.txt 2012-12-06 22:18:49.185341881 +0100 +++ 2/draft-ietf-mpls-tp-ethernet-addressing-03.txt 2012-12-06 22:18:49.201371063 +0100 @@ -1,51 +1,45 @@ MPLS D. Frost, Ed. Internet-Draft S. Bryant, Ed. Intended status: Standards Track Cisco Systems -Expires: May 23, 2013 M. Bocci, Ed. +Expires: June 9, 2013 M. Bocci, Ed. Alcatel-Lucent - November 22, 2012 + December 6, 2012 MPLS-TP Next-Hop Ethernet Addressing - draft-ietf-mpls-tp-ethernet-addressing-02 + draft-ietf-mpls-tp-ethernet-addressing-03 Abstract The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP) is the set of MPLS protocol functions applicable to the construction and operation of packet-switched transport networks. This document presents considerations for link-layer addressing of Ethernet frames carrying MPLS-TP packets. - This document is a product of a joint Internet Engineering Task Force - (IETF) / International Telecommunication Union Telecommunication - Standardization Sector (ITU-T) effort to include an MPLS Transport - Profile within the IETF MPLS and PWE3 architectures to support the - capabilities and functionalities of a packet transport network. - Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on May 23, 2013. + This Internet-Draft will expire on June 9, 2013. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -123,34 +117,36 @@ the available options when this is not the case. Each node MAY be statically configured with the MAC address of its peer. Note however that static MAC address configuration can present an administrative burden and lead to operational problems. For example, replacement of an Ethernet interface to resolve a hardware fault when this approach is used requires that the peer node be manually reconfigured with the new MAC address. This is especially problematic if the peer is operated by another provider. - The Ethernet broadcast address FF-FF-FF-FF-FF-FF MAY be used as the - 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 - excessive frame distribution and processing at the Ethernet layer. - Broadcast traffic may also be treated specially by some devices and - this may not be desirable for MPLS-TP data frames. + Another approach which may be considered is to use the Ethernet + broadcast address FF-FF-FF-FF-FF-FF as the 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 excessive frame + distribution and processing at the Ethernet layer. Broadcast traffic + may also be treated specially by some devices and this may not be + desirable for MPLS-TP data frames. - The approach which SHOULD be used, in view of these considerations, - is therefore to use as the destination MAC address an Ethernet - multicast address reserved for MPLS-TP for use over point-to-point - links. The address allocated for this purpose by the Internet - Assigned Numbers Authority (IANA) is 01-00-5E-90-00-00. An MPLS-TP - implementation MUST process Ethernet frames received over a point-to- - point link with this destination MAC address by default. + In view of the above considerations, the approach which SHOULD be + used, is therefore to configure both nodes to use the method + described in this document which uses, as a destination MAC address, + an Ethernet multicast address reserved for MPLS-TP for use over + point-to-point links. The address allocated for this purpose by the + Internet Assigned Numbers Authority (IANA) is 01-00-5E-90-00-00. An + MPLS-TP implementation MUST process Ethernet frames received over a + point-to-point link with this destination MAC address by default. The use of broadcast or multicast addressing for the purpose described in this section, i.e. as a placeholder for the unknown 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 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 to declare that a link is point-to-point if it supports these addressing modes. Moreover, the operator is cautioned that it is not always clear whether a given link is, or will remain, strictly point- @@ -212,59 +208,61 @@ that no devices are attached to the link that are not authorized to receive the frames, or take steps to mitigate the possibility of excessive frame distribution, for example by configuring the Ethernet switch to appropriately restrict the delivery of multicast frames to authorized ports. 6. IANA Considerations 6.1. Ethernet Multicast Address Allocation - IANA has allocated an Ethernet multicast address from the IANA - 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 - Section 2. The allocated address is 01-00-5E-90-00-00. + IANA has allocated an Ethernet multicast address from the "IANA + Multicast 48-bit MAC Addresses" address block in the "Ethernet + Numbers" registry for use by MPLS-TP LSRs over point-to-point links + as described in Section 2. The allocated address is + 01-00-5E-90-00-00. 6.2. G-ACh Advertisement Protocol Allocation IANA is requested to allocate a new Application ID in the "G-ACh Advertisement Protocol Applications" registry - [I-D.ietf-mpls-gach-adv], as follows: + [I-D.ietf-mpls-gach-adv] (currently located in the "Pseudowire Name + Spaces (PWE3)"), as follows: Application ID Description Reference -------------- ----------------------------- ------------ 0x0001 Ethernet Interface Parameters (this draft) 6.3. Creation of Ethernet Interface Parameters Registry IANA is requested to create a new registry, "G-ACh Advertisement - Protocol: Ethernet Interface Parameters", with fields and initial - allocations as follows: + Protocol: Ethernet Interface Parameters" within the "Pseudowire Name + Spaces (PWE3)" 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. + The allocation policy for this registry is IETF Review. 7. References 7.1. Normative References [I-D.ietf-mpls-gach-adv] - Frost, D., Bocci, M., and S. Bryant, "MPLS Generic + Frost, D., Bryant, S., and M. Bocci, "MPLS Generic Associated Channel (G-ACh) Advertisement Protocol", - draft-ietf-mpls-gach-adv-03 (Work in progress), - January 2012. + draft-ietf-mpls-gach-adv-03 (work in progress), + October 2012. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 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., Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack