BGP Logical Link Discovery Protocol (LLDP) Peer Discovery
draft-acee-idr-lldp-peer-discovery-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          A. Lindem
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                                K. Patel
Expires: September 14, 2017                                  Arrcus, Inc
                                                                S. Zandi
                                                                LinkedIn
                                                          March 13, 2017

       BGP Logical Link Discovery Protocol (LLDP) Peer Discovery
               draft-acee-idr-lldp-peer-discovery-00.txt

Abstract

   Link Layer Discovery Protocol (LLDP) or IEEE 802.1AB is implemented
   in networking equipment from many vendors.  It is natural for IETF
   protocols to avail this protocol for simple discovery tasks.  This
   document describes how BGP would use LLDP to discover directly
   connected and 2-hop peers when peering is based on loopback
   addresses.

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 September 14, 2017.

Copyright Notice

   Copyright (c) 2017 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
   carefully, as they describe your rights and restrictions with respect

Lindem, et al.         Expires September 14, 2017               [Page 1]
Internet-Draft           BGP LLDP Peer Discovery              March 2017

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Notation . . . . . . . . . . . . . . . . . .   2
   2.  LLDP Extensions . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  LLDP Organizationally Specific TLV Format . . . . . . . .   3
     2.2.  Local IP Address OS-TLV Format  . . . . . . . . . . . . .   4
     2.3.  BGP Config OS-TLV Format  . . . . . . . . . . . . . . . .   5
       2.3.1.  BGP Config OS-TLV - Peering Address Sub-TLV . . . . .   6
       2.3.2.  BGP Config OS-TLV - BGP Local AS Sub-TLV  . . . . . .   7
       2.3.3.  BGP Config OS-TLV - BGP Capabilities Sub-TLV  . . . .   8
   3.  BGP LLDP Peer Discovery Operations  . . . . . . . . . . . . .   9
     3.1.  Advertising BGP Speaker . . . . . . . . . . . . . . . . .   9
     3.2.  Receiving BGP Speaker . . . . . . . . . . . . . . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     5.1.  IANA Assigned LLDP Subtype  . . . . . . . . . . . . . . .  10
     5.2.  BGP Config LLDP OS-TLV Sub-TLVs . . . . . . . . . . . . .  11
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Link Layer Discovery Protocol (LLDP) [LLDP] or IEEE 802.1AB is
   implemented in networking equipment from many vendors.  It is natural
   for IETF protocols to avail this protocol for simple discovery tasks.
   This document describes how BGP [BGP] would use LLDP to discover
   directly connected and 2-hop peers when peering is based on loopback
   addresses.

1.1.  Requirements Notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC-KEYWORDS].
Show full document text