idnits 2.17.1 draft-eastlake-lldp-mac-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 14, 2020) is 1442 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 7042 (Obsoleted by RFC 9542) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT D. Eastlake 2 Intended Status: Proposed Standard Futurewei Technologies 3 Expires: November 13, 2020 May 14, 2020 5 MAC Address for Layer 3 Link Local Discovery Protocol (LLDP) 6 8 Abstract 10 IEEE 802 has defined a number of protocols which operate between 11 adjacent Ethernet stations at Layer 2, including bridges, such as the 12 Link Layer Discover Protocol (IEEE 802.1AB, LLDP). LLDP and other 13 such protocols may be useful between Layer 3 aware stations such as 14 IP routers and hosts. This document specifies a MAC address that can 15 be used for this purpose despite intervening bridges. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Distribution of this document is unlimited. Comments should be sent 23 to the authors. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft 37 Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 Table of Contents 42 1. Introduction............................................3 43 1.1 Notations Used in This Document........................3 45 2. Network Layers and MAC Addresses........................4 47 3. IANA Considerations.....................................6 48 4. Security Considerations.................................7 50 5. Acknowledgements........................................7 52 Normative References.......................................8 53 Informative References.....................................8 55 Appendix A: EUI-48 Assignment Request.....................10 57 1. Introduction 59 IEEE 802 [IEEE802] has defined a number of protocols which operate 60 between adjacent Ethernet stations at Layer 2, including bridges, 61 such as the Link Layer Discover Protocol ([802.1AB] LLDP) and the 62 Link Aggregation Control Protocol ([802.1AX] LACP). LLDP and other 63 such protocols may be useful between adjacent Layer 3 [ISO] aware 64 stations such as IP routers and hosts. This document specifies a MAC 65 address that can be used for that purpose despite intervening 66 bridges. 68 1.1 Notations Used in This Document 70 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 71 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 72 "OPTIONAL" in this document are to be interpreted as described in BCP 73 14 [RFC2119] [RFC8174] when, and only when, they appear in all 74 capitals, as shown here. 76 In this document the terms/acronyms listed below have the indicated 77 meaning: 79 "LACP" Link Aggregation Control Protocol [802.1AX]. 81 "Layer 2" Layer 2 in the ISO model [ISO]. 83 "Layer 3" Layer 3 in the ISO model [ISO]. 85 "LLDP" Link Layer Discovery Protocol [802.1AB]. 87 "MAC" Media Access Control [RFC7042bis] (not Message 88 Authentication Code). 90 PDU Protocol Data Unit. 92 2. Network Layers and MAC Addresses 94 LLDP [802.1AB] is a Layer 2 [ISO] protocol providing for the 95 unacknowledged announcement of information by an Ethernet station to 96 other stations on the same Ethernet link. There are proposals for 97 the use of LLDP between L3 aware stations such as between a host and 98 its first hop IP router or between IP adjacent routers. Examples are 99 [LLDP1] [LLDP2] [LLDP3]. In addition, project [802.1ABdh] is underway 100 in [IEEE802] that may extend the LLDP standard so that stations can 101 announce a larger amount of information. 103 As illustrated in the figure below, uses of LLDP and similar 104 protocols between Ethernet stations have a scope of adjacency 105 controlled by the multicast destination MAC address [RFC7042bis] of 106 the Ethernet frame used to transmit the LLDP PDU. 108 - Customer bridges use 0x0180C2000000 for LLDP and the like. Frames 109 sent to that address are transparently forwarded through any lower 110 level bridges, such as the provider bridges shown below. On the 111 other hand, IP routers do not forward frames sent to unknown 112 multicast addresses unless configured to do so. Thus, frames sent 113 to this address by the customer bridge shown near the bottom of 114 the figure will not reach either of the customer bridges shown 115 higher up in the figure due to the intervening IP router. 117 - Provider bridges use 0x0180C2000008 for LLDP. Frames sent to that 118 address are transparently forwarded by lower level bridges (not 119 shown in the figure) and are blocked by higher level bridges, such 120 as customer bridges. They are also blocked as described in the 121 previous point by IP routers. 123 LLDP or similar Ethernet frames intended to be between adjacent IP 124 routers or between a host and its first hop IP router need to avoid 125 use of a destination MAC address that might be intercepted by any 126 intervening bridge. The multicast destination MAC addresses used by 127 bridges are the block from 0x0180C2000000 to 0x0180C200003F but it 128 would be best to be conservative and avoid all addresses from 129 0x0180C2000000 to 0x0180C2FFFFFF. An address meeting this criterion 130 is specified in Section 3 below and its use is RECOMMENDED. 132 +-------+ 133 | Host | 134 +-------+ 135 | 136 +---------+ 137 |L3 Router| 138 +---------+ 139 . \ 140 . +---------------+ 141 . |Customer Bridge| 142 . +---------------+ 143 . : \ 144 . : +---------------+ 145 . : |Provider Bridge| 146 . : +---------------+ 147 . : | 148 . : +---------------+ 149 . : |Provider Bridge| 150 . : +---------------+ 151 . : / 152 . +---------------+ 153 . |Customer Bridge| 154 . +---------------+ 155 . / 156 +---------+ 157 |L3 Router| 158 +---------+ 159 . \ 160 . +---------------+ 161 . |Customer Bridge| 162 . +---------------+ 163 . / 164 +-------+ 165 | Host | 166 +-------+ 168 Note: The above figure is simplified. For example, where one or two 169 customer bridges or provider bridges are shown, there could be zero 170 or some larger number. There could also be one or more bridges 171 between the host shown at the top of the figure and its first hop IP 172 router. Only two levels of bridge are shown (customer and provider) 173 but [802.1Q] specifies additional levels of bridges. 175 3. IANA Considerations 177 IANA is requested to assign a 48-bit multicast MAC address 178 [0x00000E900004 suggested] under the IANA OUI for use with Link Layer 179 Discovery Protocol and similar protocols between Layer 3 routers as 180 per the request in Appendix A. The entry in the "IANA Multicast 181 48-bit MAC Addresses" registry is as follows: 183 Addresses Usage Reference 184 --------- ------------------------- --------------- 185 [tbd] Layer 3 LLDP and the like [this document] 187 (Alternatively, there could be more than on MAC address assigned for 188 different L3 or higher layer [ISO] purposes.) 190 4. Security Considerations 192 TBD 194 5. Acknowledgements 196 The comments and suggestions of the following people, listed in 197 alphabetic order, are gratefully acknowledged: 199 TBD 201 Normative References 203 [802.1AB] - IEEE 802, "IEEE Standard for Local and metropolitan area 204 networks - Station and Media Access Control Connectivity 205 Discovery", IEEE Std 802.1AB-2016, 29 January 2016. 207 [RFC2119] - Bradner, S., "Key words for use in RFCs to Indicate 208 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, 209 March 1997, . 211 [RFC7042bis] - Eastlake 3rd, D. and J. Abley, "IANA Considerations 212 and IETF Protocol and Documentation Usage for IEEE 802 213 Parameters", BCP 141, RFC 7042, DOI 10.17487/RFC7042, October 214 2013, . 216 [RFC8174] - Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 217 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 218 2017, . 220 Informative References 222 [802.1ABdh] - IEEE 802, "IEEE Standard for Local and Metropolitan 223 Area Networks - Station and Media Access Control Connectivity 224 Discovery Amendment: Support for Multiframe Protocol Data 225 Units", work in progress. 227 [802.1AX] - IEEE 802, "IEEE Standard for Local and metropolitan area 228 networks - Link Aggregation", IEEE Std 802.1AX-2014, 10 229 December 2014. 231 [802.1Q] - IEEE 802, "IEEE Standard for Local and metropolitan area 232 networks - Bridges and Bridged Networks", IEEE Std 802.1Q-2014, 233 3 November 2014. 235 [IEEE802] - IEEE 802 LAN/MAN Standards Committee, 236 . 238 [ISO] - ISO/IEC, "Information technology - Open Systems 239 Interconnection - Basic Reference Model: The Basic Model", 240 ISO/IEC 7498-1:1994(E), 15 June 1996. 242 [LLDP1] - A. Lindem, K. Patel, S. Zandi, J. Haas, X. Xu, "BGP Logical 243 Link Discovery Protocol (LLDP) Peer Discovery", draft-acee-idr- 244 lldp-peer-discovery, work in progress. 246 [LLDP2] - P. Congdon, P. Bottorff, "LSVR IETF Organizationally 247 Specific TLVs for IEEE Std 802.1AB (LLDP)", draft-congdon-lsvr- 248 lldp-tlvs, work in progress. 250 [LLDP3] - M. Richardson, L. Xia, "IPv6 over Link-Local Discovery 251 Protocol", draft-richardson-anima-ipv6-lldp, work in progress. 253 Appendix A: EUI-48 Assignment Request 255 (not yet submitted) 257 Applicant Name: Donald E. Eastlake, III 259 Applicant Email: d3e3e3@gmail.com 261 Applicant Telephone: +1-508-333-2270 263 Use Name: L3-LLDP 265 Document: [this document] 267 Specify whether this is an application for EUI-48 or EUI-64 268 identifiers: EUI-48 270 Size of Block requested: 1 272 Specify multicast, unicast, or both: multicast 274 Authors' Addresses 276 Donald E. Eastlake 3rd 277 Futurewei Technologies 278 2386 Panoramic Circle 279 Apopka, FL 32703 USA 281 Phone: +1-508-333-2270 282 EMail: d3e3e3@gmail.com 284 Copyright, Disclaimer, and Additional IPR Provisions 286 Copyright (c) 2020 IETF Trust and the persons identified as the 287 document authors. All rights reserved. 289 This document is subject to BCP 78 and the IETF Trust's Legal 290 Provisions Relating to IETF Documents 291 (http://trustee.ietf.org/license-info) in effect on the date of 292 publication of this document. Please review these documents 293 carefully, as they describe your rights and restrictions with respect 294 to this document. Code Components extracted from this document must 295 include Simplified BSD License text as described in Section 4.e of 296 the Trust Legal Provisions and are provided without warranty as 297 described in the Simplified BSD License. This Internet-Draft is 298 submitted in full conformance with the provisions of BCP 78 and BCP 299 79.