draft-ietf-mpls-tp-ethernet-addressing-08.txt   rfc7213.txt 
MPLS D. Frost Internet Engineering Task Force (IETF) D. Frost
Internet-Draft S. Bryant Request for Comments: 7213 Blue Sun
Intended status: Standards Track Cisco Systems Category: Standards Track S. Bryant
Expires: January 25, 2014 M. Bocci ISSN: 2070-1721 Cisco Systems
M. Bocci
Alcatel-Lucent Alcatel-Lucent
July 24, 2013 June 2014
MPLS-TP Next-Hop Ethernet Addressing MPLS Transport Profile (MPLS-TP) Next-Hop Ethernet Addressing
draft-ietf-mpls-tp-ethernet-addressing-08
Abstract Abstract
The Multiprotocol Label Switching (MPLS) Transport Profile (MPLS-TP) The MPLS Transport Profile (MPLS-TP) is the set of MPLS protocol
is the set of MPLS protocol functions applicable to the construction functions applicable to the construction and operation of packet-
and operation of packet-switched transport networks. This document switched transport networks. This document presents considerations
presents considerations for link-layer addressing of Ethernet frames for link-layer addressing of Ethernet frames carrying MPLS-TP
carrying MPLS-TP packets. packets.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on January 25, 2014. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7213.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 20 skipping to change at page 2, line 18
functions that meet the requirements [RFC5654] for the application of functions that meet the requirements [RFC5654] for the application of
MPLS to the construction and operation of packet-switched transport MPLS to the construction and operation of packet-switched transport
networks. The MPLS-TP data plane consists of those MPLS-TP functions networks. The MPLS-TP data plane consists of those MPLS-TP functions
concerned with the encapsulation and forwarding of MPLS-TP packets concerned with the encapsulation and forwarding of MPLS-TP packets
and is described in [RFC5960]. and is described in [RFC5960].
This document presents considerations for link-layer addressing of This document presents considerations for link-layer addressing of
Ethernet frames carrying MPLS-TP packets. Since MPLS-TP packets are Ethernet frames carrying MPLS-TP packets. Since MPLS-TP packets are
MPLS packets, existing procedures ([RFC3032], [RFC5332]) for the MPLS packets, existing procedures ([RFC3032], [RFC5332]) for the
encapsulation of MPLS packets over Ethernet apply. Because IP encapsulation of MPLS packets over Ethernet apply. Because IP
functionality is only optional in an MPLS-TP network, IP-based functionality is optional in an MPLS-TP network, IP-based protocols
protocols for Media Access Control (MAC) address learning, such as for Media Access Control (MAC) address learning, such as the Address
the Address Resolution Protocol (ARP) [RFC0826] and IP version 6 Resolution Protocol (ARP) [RFC826] and IPv6 Neighbor Discovery
Neighbor Discovery [RFC4861], may not be available. This document [RFC4861], may not be available. This document specifies the options
specifies the options for the determination and selection of the for the determination and selection of the next-hop Ethernet MAC
next-hop Ethernet MAC address when MPLS-TP is used between nodes that address when MPLS-TP is used between nodes that do not have an IP
do not have an IP dataplane. data plane.
1.1. Terminology 1.1. Terminology
Term Definition Term Definition
------- --------------------------- ------- ---------------------------
ARP Address Resolution Protocol ARP Address Resolution Protocol
G-ACh Generic Associated Channel G-ACh Generic Associated Channel
LSP Label Switched Path LSP Label Switched Path
LSR Label Switching Router LSR Label Switching Router
MAC Media Access Control MAC Media Access Control
skipping to change at page 3, line 4 skipping to change at page 2, line 47
Additional definitions and terminology can be found in [RFC5960] and Additional definitions and terminology can be found in [RFC5960] and
[RFC5654]. [RFC5654].
1.2. Requirements Language 1.2. Requirements Language
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].
2. Point-to-Point Link Addressing 2. Point-to-Point Link Addressing
When two MPLS-TP nodes are connected by a point-to-point Ethernet When two MPLS-TP nodes are connected by a point-to-point Ethernet
link, the question arises as to what destination Ethernet Media link, the question arises as to what destination Ethernet Media
Access Control (MAC) address should be specified in Ethernet frames Access Control (MAC) address should be specified in Ethernet frames
transmitted to the peer node over the link. The problem of transmitted to the peer node over the link. The problem of
determining this address does not arise in IP/MPLS networks because determining this address does not arise in IP/MPLS networks because
of the presence of the Ethernet Address Resolution Protocol (commonly of the presence of the Ethernet Address Resolution Protocol (commonly
referred to as Address Resolution Protocol and shortened to referred to as the Address Resolution Protocol and shortened to ARP)
ARP)[RFC0826] or IP version 6 Neighbor Discovery (ND) protocol [RFC826] or IPv6 Neighbor Discovery (ND) protocol [RFC4861], which
[RFC4861], which allow the unicast MAC address of the peer device to allow the unicast MAC address of the peer device to be learned
be learned dynamically. dynamically.
If existing mechanisms are available in an MPLS-TP network to If existing mechanisms are available in an MPLS-TP network to
determine the destination unicast MAC addresses of peer nodes, for determine the destination unicast MAC addresses of peer nodes, for
example, if the network also happens to be an IP/MPLS network, or if example, if the network also happens to be an IP/MPLS network, or if
Link Layer Discovery Protocol (LLDP) [LLDP] is in use, these methods the Link Layer Discovery Protocol (LLDP) [LLDP] is in use, these
SHOULD be used. If ARP, ND and LLDP are not available, and both methods SHOULD be used. If ARP, ND, and LLDP are not available, and
peers implement the procedures in Section 4 of this document, then both peers implement the procedures in Section 4 of this document,
the GAP mechanism described in this memo SHOULD be used. The then the GAP mechanism described in this memo SHOULD be used. The
remainder of this section discusses alternative options that might be remainder of this section discusses alternative options that might be
employed when none of the preceding MAC address learning mechanism employed when none of the preceding mechanisms for learning MAC
are available. addresses are available.
One common approach is for each node to be statically configured with One common approach is for each node to be statically configured with
the MAC address of its peer. However static MAC address the MAC address of its peer. However, static MAC address
configuration can present an administrative burden and lead to configuration can present an administrative burden and lead to
operational problems. For example, replacement of an Ethernet operational problems. For example, replacement of an Ethernet
interface to resolve a hardware fault when this approach is used interface to resolve a hardware fault when this approach is used
requires that the peer node be manually reconfigured with the new MAC requires that the peer node be manually reconfigured with the new MAC
address. This is especially problematic if the peer is operated by address. This is especially problematic if the peer is operated by
another provider. another provider.
Another approach which may be considered is to use the Ethernet Another approach that may be considered is to use the Ethernet
broadcast address FF-FF-FF-FF-FF-FF as the destination MAC address in 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 frames carrying MPLS-TP packets over a link that is known to be
point-to-point. This may, however, lead to excessive frame point-to-point. This may, however, lead to excessive frame
distribution and processing at the Ethernet layer. Broadcast traffic distribution and processing at the Ethernet layer. Broadcast traffic
may also be treated specially by some devices and this may not be may also be treated specially by some devices, and this may not be
desirable for MPLS-TP data frames. desirable for MPLS-TP data frames.
In view of the above considerations, this document recommends that, In view of the above considerations, this document recommends that,
if a non-negotiated address is to be used, both nodes are configured if a non-negotiated address is to be used, both nodes are configured
to use as a destination MAC address an Ethernet multicast address to use as a destination MAC address an Ethernet multicast address
reserved for MPLS-TP for use over point-to-point links. The address reserved for MPLS-TP for use over point-to-point links. The address
allocated for this purpose by the Internet Assigned Numbers Authority allocated for this purpose by the Internet Assigned Numbers Authority
(IANA) is 01-00-5E-90-00-00. An MPLS-TP implementation MUST default (IANA) is 01-00-5E-90-00-00. An MPLS-TP implementation MUST default
to passing MPLS packets received from a point-to-point Ethernet link to passing to the MPLS sub-system any MPLS packets received from a
with this destination MAC address to the MPLS sub-system. point-to-point Ethernet link with this destination MAC address.
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 broadcast or multicast not known to be point-to-point, these forms of broadcast or multicast
addressing MUST NOT be used. Thus the implementation MUST provide a 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 means for the operator to declare that a link is point-to-point if it
supports these addressing modes. Moreover, the operator is cautioned supports these addressing modes. Moreover, the operator is cautioned
that it is not always clear whether a given link is, or will remain, that it is not always clear whether a given link is, or will remain,
strictly point-to-point, particularly when the link is supplied by an strictly point-to-point, particularly when the link is supplied by an
external provider; point-to-point declarations therefore need to be external provider; point-to-point declarations therefore need to be
used with care. Because of these caveats it is RECOMMENDED that used with care. Because of these caveats, it is RECOMMENDED that
implementations support the procedures in Section 4 so that unicast implementations support the procedures in Section 4 so that unicast
addressing can be used. addressing can be used.
3. Multipoint Link Addressing 3. Multipoint Link Addressing
When a multipoint Ethernet link serves as a section [RFC5960] for a When a multipoint Ethernet link serves as a section [RFC5960] for a
point-to-multipoint MPLS-TP LSP, and multicast destination MAC point-to-multipoint MPLS-TP LSP, and multicast destination MAC
addressing at the Ethernet layer is used for the LSP, the addressing addressing at the Ethernet layer is used for the LSP, the addressing
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 to When a multipoint Ethernet link (that is, a link that is not known to
be point-to-point, serves as a section for a point-to-point MPLS-TP be point-to-point) serves as a section for a point-to-point MPLS-TP
LSP, unicast destination MAC addresses MUST be used for Ethernet LSP, unicast destination MAC addresses MUST be used for Ethernet
frames carrying packets of the LSP. According to the discussion in frames carrying packets of the LSP. According to the discussion in
the previous section, this implies the use of either static MAC the previous section, this implies the use of either static MAC
address configuration or a protocol that enables peer MAC address address configuration or a protocol that enables peer MAC address
discovery. discovery.
4. MAC Address Discovery via the G-ACh Advertisement Protocol 4. MAC Address Discovery via the G-ACh Advertisement Protocol
The G-ACh Advertisement Protocol (GAP) [I-D.ietf-mpls-gach-adv] The G-ACh Advertisement Protocol (GAP) [RFC7212] provides a simple
provides a simple means of informing listeners on a link of the means of informing listeners on a link of the sender's capabilities
sender's capabilities and configuration. When used for this purpose and configuration. When used for this purpose on an Ethernet link,
on an Ethernet link, GAP messages are multicast to the address GAP messages are multicast to the address 01-00-5e-80-00-0d (see
01-00-5e-80-00-0d (see [I-D.ietf-mpls-gach-adv] Section 7). If these Section 7 of [RFC7212]). If these messages contain the unicast MAC
messages contain the unicast MAC address of the sender, then address of the sender, then listeners can learn this address and use
listeners can learn this address and use it in the future when it in the future when transmitting frames containing MPLS-TP packets.
transmitting frames containing MPLS-TP packets. Since the GAP does Since the GAP does not rely on IP, this provides a means of unicast
not rely on IP, this provides a means of unicast MAC discovery for MAC discovery for MPLS-TP nodes without IP support.
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" (TBD1), to support the advertisement of Ethernet-specific Parameters" (0x0001) to support the advertisement of Ethernet-
parameters associated with the sending interface. The following specific parameters associated with the sending interface. The
Type-Length-Value (TLV) objects are defined for this application; the following Type-Length-Value (TLV) objects are defined for this
TLV format is as defined in [I-D.ietf-mpls-gach-adv]: application; the TLV format is as defined in [RFC7212]:
Source MAC Address (type = 0, length = 8): The Value of this Source MAC Address (type = 0, length = 8): The Value of this
object is an EUI-64 [EUI-64] unicast MAC address assigned to one object is an EUI-64 [EUI-64] unicast MAC address assigned to one
of the interfaces of the sender that is connected to this data of the interfaces of the sender that is connected to this data
link. The IEEE-defined mapping from 48-bit MAC addresses to link. The IEEE-defined mapping from 48-bit MAC addresses to
EUI-64 form is used. EUI-64 form is used.
Maximum Frame Size (MFS) (type = 1, length = 4): The Value of this Maximum Frame Size (MFS) (type = 1, length = 4): The Value of this
object is a 32-bit unsigned integer encoded in network byte order object is a 32-bit unsigned integer encoded in network byte order
that specifies the maximum frame size in octets of an Ethernet that specifies the maximum frame size in octets of an Ethernet
skipping to change at page 5, line 29 skipping to change at page 5, line 23
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=0 | Reserved | Length=8 | | Type=0 | Reserved | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address in EUI-64 Format | | MAC Address in EUI-64 Format |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Source MAC Address Object Format Source MAC Address Object Format
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=1 | Reserved | Length=4 | | Type=1 | Reserved | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum Frame Size (MFS) | | Maximum Frame Size (MFS) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: MFS Object Format MFS Object Format
Per [I-D.ietf-mpls-gach-adv], MAC Address Discovery information needs Per [RFC7212], MAC address discovery information needs to be
to be periodically retransmitted and is to be retained by a receiver periodically retransmitted and is to be retained by a receiver based
based on the period of time indicated by the associated Lifetime on the period of time indicated by the associated Lifetime field. To
field. To expedite the initialization of a link it is RECOMMENDED expedite the initialization of a link, it is RECOMMENDED that a node
that a node that has been reconfigured, rebooted or is aware that it that has been reconfigured, rebooted, or is aware that it has been
have been disconnected from its peer send a GAP Ethernet Interface disconnected from its peer send a GAP Ethernet Interface Parameters
Parameter message, and that it issues a GAP request message for the message, and that it issue a GAP Request message for the Ethernet
Ethernet parameters at the earliest opportunity. Interface Parameters of its peers, at the earliest opportunity.
When the MAC address in the received Source MAC Address TLV changes When the MAC address in the received Source MAC Address TLV changes,
the new MAC address MUST be used (see Section 5.2 of the new MAC address MUST be used (see Section 5.2 of [RFC7212]).
[I-D.ietf-mpls-gach-adv]).
If a minimum MFS is configured for a link and the MFS advertised by If a minimum MFS is configured for a link and the MFS advertised by
the peer is lower than that minimum, the operator MUST be notified of the peer is lower than that minimum, the operator MUST be notified of
the MFS mismatch. Under these circumstances the operator may choose the MFS mismatch. Under these circumstances, the operator may choose
to configure the LSR to shut the link, thereby triggering a fault, to configure the LSR to shut down the link, thereby triggering a
and hence causing the end-to-end path to be repaired. Alternatively fault and causing the end-to-end path to be repaired. Alternatively,
the operator may choose to configure the LSR to leave the link up so the operator may choose to configure the LSR to leave the link up so
that an OAM message can be used to verify the actual MFS. that an OAM message can be used to verify the actual MFS.
A peer node could cease transmission of G-ACh advertisements, or A peer node could cease transmission of G-ACh advertisements, or
cease to include a Source MAC Address TLV in advertisements, or cease cease to include a Source MAC Address TLV in advertisements, or cease
to be connected, any of which will cause the TLV lifetime to expire. to be connected, any of which will cause the TLV lifetime to expire.
After the Source MAC Address TLV lifetime has expired, this MAC After the Source MAC Address TLV lifetime has expired, this MAC
Address MUST NOT be used as the peer MAC address. The node MUST Address MUST NOT be used as the peer MAC address. The node MUST
return to selecting MAC addresses as though no advertisements were return to selecting MAC addresses as though no advertisements were
received, using the method configured for this eventuality. received, using the method configured for this eventuality.
5. Manageability Considerations 5. Manageability Considerations
The values sent and received by this protocol MUST be made accessible The values sent and received by this protocol MUST be made accessible
for inspection by network operators, and where local configuration is for inspection by network operators, and where local configuration is
updated by the received information, it MUST be clear why the updated by received information, it MUST be clear why the configured
configured value has been changed. The information being advertised value has been changed. If the received values change, the new
SHOULD be persistent across restarts. To ensure correct operation values MUST be used and the change made visible to the network
when an equipment restarts in a new environment, previously received operators.
advertisements MUST be discarded across restarts. If the received
values change, the new values MUST be used and the change made
visible to the network operators.
Where the link changes to a new type, i.e. from point-to-point to The Ethernet address and associated parameters advertised for an
point-to-multipoint the network operator SHOULD be informed. If the interface SHOULD be persistent across restarts. In the event of a
new link type is incompatible with the addressing Ethernet method in system restart, any data that has been retained as a consequence of
use the system MUST take the action that is configured under those prior Ethernet Interface Parameters advertisements from GAP peers
MUST be discarded; this prevents incorrect operation on the basis of
stale data.
Where the link changes to a new type, i.e., from point-to-point to
point-to-multipoint, the network operator SHOULD be informed. If the
new link type is incompatible with the Ethernet addressing method in
use, the system MUST take the action that is configured under those
circumstances. circumstances.
6. Security Considerations 6. 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
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
switch to appropriately restrict the delivery of multicast frames to Ethernet switch to appropriately restrict the delivery of multicast
authorized ports. frames to authorized ports).
An attacker could disrupt communications by modifying the Source MAC An attacker could disrupt communications by modifying the Source MAC
Address or the MFS values, however this is mitigated by the use of Address or the MFS values; however, this is mitigated by the use of
cryptographic authentication as described in [I-D.ietf-mpls-gach-adv] cryptographic authentication as described in [RFC7212], which also
which also describes other considerations applicable to the GAP describes other considerations applicable to the GAP protocol.
protocol. Visibility into the contents of either of the TLVs could Visibility into the contents of either of the TLVs could provide
provide information that is useful for an attacker. This is best information that is useful for an attacker. This is best addressed
addressed by physical security of the links. by physical security of the links.
7. IANA Considerations 7. IANA Considerations
7.1. Ethernet Multicast Address Allocation 7.1. Ethernet Multicast Address Allocation
IANA has allocated an Ethernet multicast address from the "IANA IANA has allocated an Ethernet multicast address from the "IANA
Multicast 48-bit MAC Addresses" address block in the "Ethernet Multicast 48-bit MAC Addresses" address block in the "Ethernet
Numbers" registry for use by MPLS-TP LSRs over point-to-point links Numbers" registry for use by MPLS-TP LSRs over point-to-point links
as described in Section 2. The allocated address is as described in Section 2. The allocated address is
01-00-5E-90-00-00. IANA is requested to update the reference to 01-00-5E-90-00-00. IANA has updated the reference to point to the
point to the RFC number assigned to this document. RFC number assigned to this document.
7.2. G-ACh Advertisement Protocol Allocation 7.2. G-ACh Advertisement Protocol Allocation
IANA is requested to allocate a new Application ID in the "G-ACh IANA has allocated a new Application ID in the "G-ACh Advertisement
Advertisement Protocol Applications" registry Protocol Application Registry", as follows:
[I-D.ietf-mpls-gach-adv] (currently located in the "Pseudowire Name
Spaces (PWE3)"), as follows:
Application ID Description Reference Application ID Description Reference
------------------------- --------------------------- --------------- -------------- ----------------------------- ---------
TBD1 to be assigned by Ethernet Interface (this draft) 0x0001 Ethernet Interface Parameters This RFC
IANA Parameters
7.3. Creation of Ethernet Interface Parameters Registry 7.3. Creation of Ethernet Interface Parameters Registry
IANA is requested to create a new registry, "G-ACh Advertisement IANA has created a new registry, "G-ACh Advertisement Protocol:
Protocol: Ethernet Interface Parameters" within the "Pseudowire Name Ethernet Interface Parameters" within the "Generic Associated Channel
Spaces (PWE3)" with fields and initial allocations as follows: (G-ACh) Parameters" registry with fields and initial allocations as
follows:
Type Name Type ID Reference Type Name Type ID Reference
------------------ ------- ------------ ------------------ ------- ---------
Source MAC Address 0 (this draft) Source MAC Address 0 This RFC
Maximum Frame Size 1 (this draft) Maximum Frame Size 1 This RFC
The range of the Type ID field is 0 - 255. The range of the Type ID field is 0 - 255.
The allocation policy for this registry is IETF Review or IESG The allocation policy for this registry is IETF Review or IESG
approval. Approval.
8. Acknowledgements 8. Acknowledgements
We thank Adrian Farrel for his valuable review comments on this We thank Adrian Farrel for his valuable review comments on this
document. document.
9. References 9. References
9.1. Normative References 9.1. Normative References
[EUI-64] , "[EUI64] IEEE, "Guidelines for 64-bit Global Identifier [EUI-64] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)
(EUI-64) Registration Authority", http:// Registration Authority", March 1997,
standards.ieee.org/regauth/oui/tutorials/EUI64.html, March <http://standards.ieee.org/regauth/oui/tutorials/
1997.", . EUI64.html>.
[I-D.ietf-mpls-gach-adv]
Frost, D., Bryant, S., and M. Bocci, "MPLS Generic
Associated Channel (G-ACh) Advertisement Protocol", draft-
ietf-mpls-gach-adv-08 (work in progress), June 2013.
[LLDP] , "IEEE, "Station and Media Access Control Connectivity [LLDP] IEEE, "Station and Media Access Control Connectivity
Discovery (802.1AB)", September 2009.", . Discovery", IEEE 802.1AB, September 2009.
[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.
[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.
9.2. Informative References [RFC7212] Frost, D., Bryant, S., and M. Bocci, "MPLS Generic
Associated Channel (G-ACh) Advertisement Protocol", RFC
7212, June 2014.
[RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or 9.2. Informative References
converting network protocol addresses to 48.bit Ethernet
address for transmission on Ethernet hardware", STD 37,
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.
Berger, "A Framework for MPLS in Transport Networks", RFC Berger, "A Framework for MPLS in Transport Networks", RFC
5921, July 2010. 5921, July 2010.
[RFC826] Plummer, D., "Ethernet Address Resolution Protocol: Or
converting network protocol addresses to 48.bit Ethernet
address for transmission on Ethernet hardware", STD 37,
RFC 826, November 1982.
Authors' Addresses Authors' Addresses
Dan Frost Dan Frost
Cisco Systems Blue Sun
Email: danfrost@cisco.com EMail: frost@mm.st
Stewart Bryant Stewart Bryant
Cisco Systems Cisco Systems
Email: stbryant@cisco.com EMail: stbryant@cisco.com
Matthew Bocci Matthew Bocci
Alcatel-Lucent Alcatel-Lucent
Email: matthew.bocci@alcatel-lucent.com EMail: matthew.bocci@alcatel-lucent.com
 End of changes. 47 change blocks. 
139 lines changed or deleted 137 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/