< draft-acee-idr-lldp-peer-discovery-06.txt   draft-acee-idr-lldp-peer-discovery-07.txt >
Network Working Group A. Lindem Network Working Group A. Lindem
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track K. Patel Intended status: Standards Track K. Patel
Expires: May 24, 2020 Arrcus, Inc Expires: December 5, 2020 Arrcus, Inc
S. Zandi S. Zandi
LinkedIn LinkedIn
J. Haas J. Haas
Juniper Networks, Inc Juniper Networks, Inc
X. Xu X. Xu
Alibaba Alibaba
November 21, 2019 June 3, 2020
BGP Logical Link Discovery Protocol (LLDP) Peer Discovery BGP Logical Link Discovery Protocol (LLDP) Peer Discovery
draft-acee-idr-lldp-peer-discovery-06 draft-acee-idr-lldp-peer-discovery-07
Abstract Abstract
Link Layer Discovery Protocol (LLDP) or IEEE Std 802.1AB is Link Layer Discovery Protocol (LLDP) or IEEE Std 802.1AB is
implemented in networking equipment from many vendors. It is natural implemented in networking equipment from many vendors. It is natural
for IETF protocols to avail this protocol for simple discovery tasks. for IETF protocols to avail this protocol for simple discovery tasks.
This document describes how BGP would use LLDP to discover directly This document describes how BGP would use LLDP to discover directly
connected and 2-hop peers when peering is based on loopback connected and 2-hop peers when peering is based on loopback
addresses. addresses.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 May 24, 2020. This Internet-Draft will expire on December 5, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 33 skipping to change at page 2, line 33
2.2.1. BGP Config OS-TLV - Peering Address Sub-TLV . . . . . 5 2.2.1. BGP Config OS-TLV - Peering Address Sub-TLV . . . . . 5
2.2.2. BGP Config OS-TLV - BGP Local AS Sub-TLV . . . . . . 6 2.2.2. BGP Config OS-TLV - BGP Local AS Sub-TLV . . . . . . 6
2.2.3. BGP Config OS-TLV - BGP Identifier Sub-TLV . . . . . 7 2.2.3. BGP Config OS-TLV - BGP Identifier Sub-TLV . . . . . 7
2.2.4. BGP Config OS-TLV - Session Group-ID Sub-TLV . . . . 8 2.2.4. BGP Config OS-TLV - Session Group-ID Sub-TLV . . . . 8
2.2.5. BGP Config OS-TLV - BGP Session Capabilities Sub-TLV 9 2.2.5. BGP Config OS-TLV - BGP Session Capabilities Sub-TLV 9
2.2.6. BGP Config OS-TLV - Key Chain Sub-TLV . . . . . . . . 10 2.2.6. BGP Config OS-TLV - Key Chain Sub-TLV . . . . . . . . 10
2.2.7. BGP Config OS-TLV - Local Address Sub-TLV . . . . . . 11 2.2.7. BGP Config OS-TLV - Local Address Sub-TLV . . . . . . 11
3. BGP LLDP Peer Discovery Operations . . . . . . . . . . . . . 12 3. BGP LLDP Peer Discovery Operations . . . . . . . . . . . . . 12
3.1. Advertising BGP Speaker . . . . . . . . . . . . . . . . . 12 3.1. Advertising BGP Speaker . . . . . . . . . . . . . . . . . 12
3.2. Receiving BGP Speaker . . . . . . . . . . . . . . . . . . 12 3.2. Receiving BGP Speaker . . . . . . . . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 13 4. LLDP Authentication/Encryption . . . . . . . . . . . . . . . 13
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
5.1. IANA Assigned LLDP Subtype . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
5.2. BGP Config LLDP OS-TLV Sub-TLVs . . . . . . . . . . . . . 14 6.1. IANA Assigned LLDP Subtype . . . . . . . . . . . . . . . 14
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 6.2. BGP Config LLDP OS-TLV Sub-TLVs . . . . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Normative References . . . . . . . . . . . . . . . . . . 16 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.2. Informative References . . . . . . . . . . . . . . . . . 16 8.1. Normative References . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 17 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
Link Layer Discovery Protocol (LLDP) [LLDP] or IEEE Std 802.1AB is Link Layer Discovery Protocol (LLDP) [LLDP] or IEEE Std 802.1AB is
implemented in networking equipment from many vendors. It is natural implemented in networking equipment from many vendors. It is natural
for IETF protocols to avail this protocol for simple discovery tasks. for IETF protocols to avail this protocol for simple discovery tasks.
This document describes how BGP [RFC4271] would use LLDP to discover This document describes how BGP [RFC4271] would use LLDP to discover
directly connected and 2-hop peers when peering is based on loopback directly connected and 2-hop peers when peering is based on loopback
skipping to change at page 13, line 43 skipping to change at page 13, line 43
BGP-OS TLV. A BGP speaker MAY use the received capabilities to BGP-OS TLV. A BGP speaker MAY use the received capabilities to
ensure appropriate local neighbor configuration in order to ensure appropriate local neighbor configuration in order to
facilitate session establishment. facilitate session establishment.
If TCP MD5 authentication [RFC2385]. or TCP Authentication Option If TCP MD5 authentication [RFC2385]. or TCP Authentication Option
(TCP-AO) [RFC5925] is to be used on the session as determined either (TCP-AO) [RFC5925] is to be used on the session as determined either
via the Session Capabilities Sub-TLV, Session Group-ID, or local via the Session Capabilities Sub-TLV, Session Group-ID, or local
policy, the key chain name in the Key Chain Sub-TLV of the BGP-OS TLV policy, the key chain name in the Key Chain Sub-TLV of the BGP-OS TLV
MAY be used to identify the correct key chain [RFC8177]. MAY be used to identify the correct key chain [RFC8177].
4. Security Considerations 4. LLDP Authentication/Encryption
The IEEE 802.1AE [MACsec] standard can be used for encryption and/or
authentication to provide privacy and integrity. MACsec utilizes the
Galois/Counter Mode Advanced Encryption Standard (AES-GCM) for
authenticated encryption and Galois Message Authentication Code
(GMAC) if only authentication, but not encryption is required.
The MACsec Key Agreement (MKA) is included as part of the IEEE
802.1X-20200 Port-Based Network Access Control Standard [MKA]. The
purpose of MKA is to provide a method for discovering MACsec peers
and negotiating the security keys needed to secure the link.
5. Security Considerations
This security considerations for BGP [RFC4271] apply equally to this This security considerations for BGP [RFC4271] apply equally to this
extension. extension.
Additionally, BGP peering address discovery should only be done on Additionally, BGP peering address discovery should only be done on
trusted links (e.g., in a data center network) since LLDP packets are trusted links (e.g., in a data center network) since LLDP packets are
not authenticated or encrypted [LLDP]. not authenticated or encrypted [LLDP].
5. IANA Considerations LLDP Authentication and/or encryption can provided as described in
section Section 4.
5.1. IANA Assigned LLDP Subtype 6. IANA Considerations
6.1. IANA Assigned LLDP Subtype
IANA is requested to create a registry for IANA assigned subtypes in IANA is requested to create a registry for IANA assigned subtypes in
the IETF Organizationally Specific TLV assigned to IANA (OUI of the IETF Organizationally Specific TLV assigned to IANA (OUI of
000-00-53 [RFC7042]. Assignment is requested for 1 for the BGP 000-00-53 [RFC7042]. Assignment is requested for 1 for the BGP
Config OS-TLV. Config OS-TLV.
+-------------+-----------------------------------+ +-------------+-----------------------------------+
| Range | Assignment Policy | | Range | Assignment Policy |
+-------------+-----------------------------------+ +-------------+-----------------------------------+
| 0 | Reserved (not to be assigned) | | 0 | Reserved (not to be assigned) |
skipping to change at page 14, line 40 skipping to change at page 15, line 10
o Types in the range 2-127 are to be assigned subject to IETF o Types in the range 2-127 are to be assigned subject to IETF
Review. New values are assigned only through RFCs that have been Review. New values are assigned only through RFCs that have been
shepherded through the IESG as AD-Sponsored or IETF WG Documents shepherded through the IESG as AD-Sponsored or IETF WG Documents
[RFC5226]. [RFC5226].
o Types in the range 128-254 are reserved and not to be assigned at o Types in the range 128-254 are reserved and not to be assigned at
this time. Before any assignments can be made in this range, this time. Before any assignments can be made in this range,
there MUST be a Standards Track RFC that specifies IANA there MUST be a Standards Track RFC that specifies IANA
Considerations that covers the range being assigned. Considerations that covers the range being assigned.
5.2. BGP Config LLDP OS-TLV Sub-TLVs 6.2. BGP Config LLDP OS-TLV Sub-TLVs
IANA is requested to create a registry for Sub-TLVs of the BGP Config IANA is requested to create a registry for Sub-TLVs of the BGP Config
LLDP OS-TLV. Assignment is requested for 1 for the BGP Peering LLDP OS-TLV. Assignment is requested for 1 for the BGP Peering
Address Sub-TLV. Assignment is also requested for 2 for the Local AS Address Sub-TLV. Assignment is also requested for 2 for the Local AS
Sub-TLV. Additionally, assignment is requested for 3 for the BGP Sub-TLV. Additionally, assignment is requested for 3 for the BGP
Identifier Sub-TLV, 4 for the BGP Session Group-ID, 5 for the Session Identifier Sub-TLV, 4 for the BGP Session Group-ID, 5 for the Session
Capabilities Sub-TLV, and 6 for the Key Chain Name. Capabilities Sub-TLV, and 6 for the Key Chain Name.
+-------------+-----------------------------------+ +-------------+-----------------------------------+
| Range | Assignment Policy | | Range | Assignment Policy |
skipping to change at page 15, line 43 skipping to change at page 16, line 10
o Types in the range 8-127 are to be assigned subject to IETF o Types in the range 8-127 are to be assigned subject to IETF
Review. New values are assigned only through RFCs that have been Review. New values are assigned only through RFCs that have been
shepherded through the IESG as AD-Sponsored or IETF WG Documents shepherded through the IESG as AD-Sponsored or IETF WG Documents
[RFC5226]. [RFC5226].
o Types in the range 128-254 are reserved and not to be assigned at o Types in the range 128-254 are reserved and not to be assigned at
this time. Before any assignments can be made in this range, this time. Before any assignments can be made in this range,
there MUST be a Standards Track RFC that specifies IANA there MUST be a Standards Track RFC that specifies IANA
Considerations that covers the range being assigned. Considerations that covers the range being assigned.
6. Contributors 7. Contributors
Contributors' Addresses Contributors' Addresses
7. References 8. References
7.1. Normative References
8.1. Normative References
[LLDP] IEEE, "IEEE Standard for Local and metropolitan area [LLDP] IEEE, "IEEE Standard for Local and metropolitan area
networks-- Station and Media Access Control Connectivity networks-- Station and Media Access Control Connectivity
Discovery Corrigendum 2: Technical and Editorial Discovery Corrigendum 2: Technical and Editorial
Corrections", IEEE 802.1AB-2009/Cor 2-2015, Corrections", IEEE 802.1AB-2009/Cor 2-2015,
DOI 10.1109/ieeestd.2015.7056401, March 2015. DOI 10.1109/ieeestd.2015.7056401, March 2015.
[MACsec] IEEE, "IEEE Standard for Local and metropolitan area
networks - Media Access Control (MAC) Security",
IEEE Standard 802.1AE-2018, September 2018.
[MKA] IEEE, "IEEE Standard for Local and metropolitan area
networks - Port Based Network Access Control",
IEEE Standard 802.1X-2020, January 2020.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006,
<https://www.rfc-editor.org/info/rfc4271>. <https://www.rfc-editor.org/info/rfc4271>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
7.2. Informative References 8.2. Informative References
[RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5 [RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5
Signature Option", RFC 2385, DOI 10.17487/RFC2385, August Signature Option", RFC 2385, DOI 10.17487/RFC2385, August
1998, <https://www.rfc-editor.org/info/rfc2385>. 1998, <https://www.rfc-editor.org/info/rfc2385>.
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, "Multiprotocol Extensions for BGP-4", RFC 4760,
DOI 10.17487/RFC4760, January 2007, DOI 10.17487/RFC4760, January 2007,
<https://www.rfc-editor.org/info/rfc4760>. <https://www.rfc-editor.org/info/rfc4760>.
 End of changes. 14 change blocks. 
21 lines changed or deleted 47 lines changed or added

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