BGP Neighbor Auto-Discovery
draft-xu-idr-neighbor-autodiscovery-09

Document Type Active Internet-Draft (idr WG)
Last updated 2018-07-16
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                              X. Xu
Internet-Draft                                               Alibaba Inc
Intended status: Standards Track                           K. Talaulikar
Expires: January 17, 2019                                  Cisco Systems
                                                                   K. Bi
                                                                  Huawei
                                                             J. Tantsura
                                                          Nuage Networks
                                                        N. Triantafillis
                                                           July 16, 2018

                      BGP Neighbor Auto-Discovery
                 draft-xu-idr-neighbor-autodiscovery-09

Abstract

   BGP is being used as the underlay routing protocol in some large-
   scaled data centers (DCs).  Most popular design followed is to do
   hop-by-hop external BGP (eBGP) session configurations between
   neighboring routers on a per link basis.  The provisioning of BGP
   neighbors in routers across such a DC brings its own operational
   complexity.

   This document introduces a BGP neighbor discovery mechanism that
   greatly simplifies BGP operations in such DC and other networks by
   automatic setup of BGP sessions between neighbor routers using this
   mechanism.

Requirements Language

   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 2119 [RFC2119].

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 https://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

Xu, et al.              Expires January 17, 2019                [Page 1]
Internet-Draft                                                 July 2018

   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 January 17, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  UDP Message Header  . . . . . . . . . . . . . . . . . . . . .   5
   5.  Hello Message Format  . . . . . . . . . . . . . . . . . . . .   6
   6.  Hello Message TLVs  . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Accepted ASN List TLV . . . . . . . . . . . . . . . . . .   8
     6.2.  Peering Address TLV . . . . . . . . . . . . . . . . . . .   9
     6.3.  Local Prefix TLV  . . . . . . . . . . . . . . . . . . . .  10
     6.4.  Link Attributes TLV . . . . . . . . . . . . . . . . . . .  12
     6.5.  Neighbor TLV  . . . . . . . . . . . . . . . . . . . . . .  14
     6.6.  Cryptographic Authentication TLV  . . . . . . . . . . . .  15
   7.  Neighbor Discovery Procedure  . . . . . . . . . . . . . . . .  17
     7.1.  Interface State . . . . . . . . . . . . . . . . . . . . .  17
     7.2.  Adjacency State Machine . . . . . . . . . . . . . . . . .  18
     7.3.  Peering Route . . . . . . . . . . . . . . . . . . . . . .  19
   8.  Interactions with Base BGP Protocol . . . . . . . . . . . . .  20
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   10. Manageability Considerations  . . . . . . . . . . . . . . . .  22
     10.1.  Operational Considerations . . . . . . . . . . . . . . .  22
     10.2.  Management Considerations  . . . . . . . . . . . . . . .  23
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  23
     11.1.  BGP Hello Message  . . . . . . . . . . . . . . . . . . .  24
     11.2.  TLVs of BGP Hello Message  . . . . . . . . . . . . . . .  24
Show full document text