< draft-acee-idr-lldp-peer-discovery-05.txt   draft-acee-idr-lldp-peer-discovery-06.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: January 9, 2020 Arrcus, Inc Expires: May 24, 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
July 8, 2019 November 21, 2019
BGP Logical Link Discovery Protocol (LLDP) Peer Discovery BGP Logical Link Discovery Protocol (LLDP) Peer Discovery
draft-acee-idr-lldp-peer-discovery-05 draft-acee-idr-lldp-peer-discovery-06
Abstract Abstract
Link Layer Discovery Protocol (LLDP) or IEEE 802.1AB is implemented Link Layer Discovery Protocol (LLDP) or IEEE Std 802.1AB is
in networking equipment from many vendors. It is natural for IETF implemented in networking equipment from many vendors. It is natural
protocols to avail this protocol for simple discovery tasks. This for IETF protocols to avail this protocol for simple discovery tasks.
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.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 January 9, 2020. This Internet-Draft will expire on May 24, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
skipping to change at page 2, line 21 skipping to change at page 2, line 21
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 3
1.1.1. Requirements Language . . . . . . . . . . . . . . . . 3 1.1.1. Requirements Language . . . . . . . . . . . . . . . . 3
2. LLDP Extensions . . . . . . . . . . . . . . . . . . . . . . . 3 2. LLDP Extensions . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. LLDP Organizationally Specific TLV Format . . . . . . . . 3 2.1. LLDP IETF Organizationally Specific TLV Format . . . . . 3
2.2. BGP Config OS-TLV Format . . . . . . . . . . . . . . . . 4 2.2. BGP Config OS-TLV Format . . . . . . . . . . . . . . . . 4
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
3. BGP LLDP Peer Discovery Operations . . . . . . . . . . . . . 11 2.2.7. BGP Config OS-TLV - Local Address Sub-TLV . . . . . . 11
3.1. Advertising BGP Speaker . . . . . . . . . . . . . . . . . 11 3. BGP LLDP Peer Discovery Operations . . . . . . . . . . . . . 12
3.2. Receiving BGP Speaker . . . . . . . . . . . . . . . . . . 11 3.1. Advertising BGP Speaker . . . . . . . . . . . . . . . . . 12
4. Security Considerations . . . . . . . . . . . . . . . . . . . 12 3.2. Receiving BGP Speaker . . . . . . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 4. Security Considerations . . . . . . . . . . . . . . . . . . . 13
5.1. IANA Assigned LLDP Subtype . . . . . . . . . . . . . . . 13 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
5.2. BGP Config LLDP OS-TLV Sub-TLVs . . . . . . . . . . . . . 13 5.1. IANA Assigned LLDP Subtype . . . . . . . . . . . . . . . 14
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14 5.2. BGP Config LLDP OS-TLV Sub-TLVs . . . . . . . . . . . . . 14
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . 14 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . 15 7.1. Normative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 16 7.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
Link Layer Discovery Protocol (LLDP) [LLDP] or IEEE 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
addresses. addresses.
1.1. Requirements Notation 1.1. Requirements Notation
1.1.1. Requirements Language 1.1.1. 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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. LLDP Extensions 2. LLDP Extensions
2.1. LLDP Organizationally Specific TLV Format 2.1. LLDP IETF Organizationally Specific TLV Format
The format of the LLDP Basic Organizationally Specific TLV (OS-TLV) The format of the LLDP IETF Organizationally Specific TLV (OS-TLV) is
is defined in [LLDP]. It is shown below for completeness. defined in [LLDP]. It is shown below for completeness.
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 (127) | Length | OUI (3 Octets) 00-00-5E | | Type (127) | Length | OUI (3 Octets) 00-00-5E |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OUI Continued | Subtype | Value | | OUI Continued | Subtype | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... (Up to 507 Octets) | | ... (Up to 507 Octets) |
Type Organizationally Specific TLV type value, 127. Type IETF Organizationally Specific TLV type value, 127.
Length The length of the remainder of the TLV. Length The length of the remainder of the TLV.
OUI Organizationally unique identifier for the OUI IETF Organizationally unique identifier for the
organization's OUI. For IANA, this is value is organization's OUI. For IANA, this is value is
00-00-5E as specified in [IEEE-802-IANA]. 00-00-5E as specified in [IEEE-802-IANA].
Subtype IETF specific subtype Subtype IETF specific subtype
Value Value for organizationally specific TLV. The Length of Value Value for organizationally specific TLV. The Length of
the value is 4 octets less than the TLV length. the value is 4 octets less than the TLV length.
LLDP Organizationally Specific TLV LLDP IETF Organizationally Specific TLV
The OUI for IANA was allocated in section 1.4 of [RFC7042]. This The OUI for IANA was allocated in section 1.4 of [RFC7042]. This
document requests creation of a registry for IETF specific sub-types document requests creation of a registry for IETF specific sub-types
for LLDP Organizationally Specific TLVs. for LLDP IETF Organizationally Specific TLVs.
2.2. BGP Config OS-TLV Format 2.2. BGP Config OS-TLV Format
The BGP Config Organizationally Specific TLV (OS-TLV) will be used to The BGP Config IETF Organizationally Specific TLV (OS-TLV) will be
advertise BGP configuration information. The configuration used to advertise BGP configuration information. The configuration
information will be composed of Sub-TLVs. Since the length is information will be composed of Sub-TLVs. Since the length is
limited to 507 octets, multiple BGP Config OS-TLVs could be included limited to 507 octets, multiple BGP Config OS-TLVs could be included
in a single LLDP advertisement. in a single LLDP advertisement.
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 (127) | Length | OUI (3 Octets) 00-00-5E | | Type (127) | Length | OUI (3 Octets) 00-5E-00 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|OUI Continued | 1 | BGP Config Sub-TLVs ... | |OUI Continued | 1 | BGP Config Sub-TLVs ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... (Up to 507 Octets) | | ... (Up to 507 Octets) |
Length The length of the BGP TLV. Length The length of the BGP TLV.
Subtype IETF specific subtype for BGP Config OS-TLV. The Subtype IETF specific subtype for BGP Config OS-TLV. The
value shall be 1. value shall be 1.
skipping to change at page 11, line 5 skipping to change at page 11, line 5
| Key Chain Name | | Key Chain Name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type The Sub-TLV Type value shall be 6. Type The Sub-TLV Type value shall be 6.
Length The Sub-TLV Length will be 1 - 64 octets. Length The Sub-TLV Length will be 1 - 64 octets.
Key Chain Name The name of a key chain to be used for Key Chain Name The name of a key chain to be used for
MD5 or TCP-AO authentication. MD5 or TCP-AO authentication.
2.2.7. BGP Config OS-TLV - Local Address Sub-TLV
The BGP OS-TLV Local Address Sub-TLV will be used to advertise a
local IP addresses used for BGP next-hops. Advertising a local
interface address is useful when the address family is different from
the advertised BGP peering address.
The format of the BGP Local Interface Address Sub-TLV is shown below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (7) | Length | Address Family| IPv4/IPv6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ IPv4/IPv6 Local Address ... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type The Sub-TLV Type value shall be 7.
Length The Sub-TLV length in octets will be 4 for IPv4 or 16
for IPv6 plus 3 times the number of AFI/SAFI tuples.
Address IANA Address family (1 for IPv4 or 2 for IPv6)
Family
Local An IPv4 address (4 octets) or an IPv6 address (16 octets)
Address
3. BGP LLDP Peer Discovery Operations 3. BGP LLDP Peer Discovery Operations
The simple use case is to just use the peer address advertised in the The simple use case is to just use the peer address advertised in the
LLDP Packet Data Unit (PDU) to establish a 1-hop BGP peer session. LLDP Packet Data Unit (PDU) to establish a 1-hop BGP peer session.
This can be used in data centers using BGP as described in [RFC7938]. This can be used in data centers using BGP as described in [RFC7938].
The use case where a loopback address or other local address is The use case where a loopback address or other local address is
advertised as the peering address is also supported. However, advertised as the peering address is also supported. However,
reachabiliy to a peering address other than the interface address is reachabiliy to a peering address other than the interface address is
beyond the scope of this document. beyond the scope of this document.
skipping to change at page 13, line 10 skipping to change at page 14, line 10
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 5. IANA Considerations
5.1. IANA Assigned LLDP Subtype 5.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 Organizationally Specific TLV assigned to IANA (OUI of 000-00-53 the IETF Organizationally Specific TLV assigned to IANA (OUI of
[RFC7042]. Assignment is requested for 1 for the BGP Config OS-TLV. 000-00-53 [RFC7042]. Assignment is requested for 1 for the BGP
Config OS-TLV.
+-------------+-----------------------------------+ +-------------+-----------------------------------+
| Range | Assignment Policy | | Range | Assignment Policy |
+-------------+-----------------------------------+ +-------------+-----------------------------------+
| 0 | Reserved (not to be assigned) | | 0 | Reserved (not to be assigned) |
| | | | | |
| 1 | BGP Configuration | | 1 | BGP Configuration |
| | | | | |
| 2-127 | Unassigned (IETF Review) | | 2-127 | Unassigned (IETF Review) |
| | | | | |
| 128-254 | Reserved (Not to be assigned now) | | 128-254 | Reserved (Not to be assigned now) |
| | | | | |
| 255 | Reserved (not to be assigned) | | 255 | Reserved (not to be assigned) |
+-------------+-----------------------------------+ +-------------+-----------------------------------+
IANA LLDP Organizationally Specific TLV Sub-Types IANA LLDP IETF Organizationally Specific TLV Sub-Types
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.
skipping to change at page 14, line 22 skipping to change at page 15, line 22
| 2 | Local AS | | 2 | Local AS |
| | | | | |
| 3 | BGP Identifier | | 3 | BGP Identifier |
| | | | | |
| 4 | Session Group-ID | | 4 | Session Group-ID |
| | | | | |
| 5 | Session Capabilities | | 5 | Session Capabilities |
| | | | | |
| 6 | Key Chain Name | | 6 | Key Chain Name |
| | | | | |
| 7-127 | Unassigned (IETF Review) | | 7 | Local Address |
| | |
| 8-127 | Unassigned (IETF Review) |
| | | | | |
| 128-254 | Reserved (Not to be assigned now) | | 128-254 | Reserved (Not to be assigned now) |
| | | | | |
| 255 | Reserved (not to be assigned) | | 255 | Reserved (not to be assigned) |
+-------------+-----------------------------------+ +-------------+-----------------------------------+
LLDP BGP Config OS-TLV Types LLDP BGP Config OS-TLV Types
o Types in the range 7-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 6. Contributors
skipping to change at page 16, line 22 skipping to change at page 17, line 26
DOI 10.17487/RFC7938, August 2016, DOI 10.17487/RFC7938, August 2016,
<https://www.rfc-editor.org/info/rfc7938>. <https://www.rfc-editor.org/info/rfc7938>.
[RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J. [RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J.
Zhang, "YANG Data Model for Key Chains", RFC 8177, Zhang, "YANG Data Model for Key Chains", RFC 8177,
DOI 10.17487/RFC8177, June 2017, DOI 10.17487/RFC8177, June 2017,
<https://www.rfc-editor.org/info/rfc8177>. <https://www.rfc-editor.org/info/rfc8177>.
Appendix A. Acknowledgments Appendix A. Acknowledgments
Thanks to Sujay Gupta for review and comments. Thanks to Sujay Gupta and Paul Congdon for review and comments.
The RFC text was produced using Marshall Rose's xml2rfc tool. The RFC text was produced using Marshall Rose's xml2rfc tool.
Authors' Addresses Authors' Addresses
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
301 Midenhall Way 301 Midenhall Way
Cary, NC 27513 Cary, NC 27513
USA USA
 End of changes. 22 change blocks. 
39 lines changed or deleted 71 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/