Requirements and Considerations in BGP Peer Auto-Configuration
draft-ietf-idr-bgp-autoconf-considerations-00

Document Type Active Internet-Draft (idr WG)
Authors Randy Bush  , Jie Dong  , Jeffrey Haas  , Warren Kumari 
Last updated 2021-03-08
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
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                                            R. Bush
Internet-Draft                  Arrcus, Inc. & Internet Initiative Japan
Intended status: Informational                                   J. Dong
Expires: September 9, 2021                           Huawei Technologies
                                                            J. Haas, Ed.
                                                        Juniper Networks
                                                          W. Kumari, Ed.
                                                                  Google
                                                           March 8, 2021

     Requirements and Considerations in BGP Peer Auto-Configuration
             draft-ietf-idr-bgp-autoconf-considerations-00

Abstract

   This draft is an exploration of the requirements, the alternatives,
   and trade-offs in BGP peer auto-discovery at various layers in the
   stack.  It is based on discussions in the IDR Working Group BGP
   Autoconf Design Team.  The current target environment is the
   datacenter.

   This document is not intended to become an RFC.

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 BCP 14 [RFC2119]
   [RFC8174] when, and only when, they appear in all capitals, as shown
   here.

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
   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 9, 2021.

Bush, et al.            Expires September 9, 2021               [Page 1]
Internet-Draft          BGP Peer Auto-Config Reqs             March 2021

Copyright Notice

   Copyright (c) 2021 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.  Design Team Determinations  . . . . . . . . . . . . . . . . .   3
     2.1.  Problem Scope . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Simplicity  . . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  BGP Auto-Discovery Protocol State Requirements  . . . . .   3
       2.3.1.  BGP Session Transport State . . . . . . . . . . . . .   4
       2.3.2.  BGP Session Protocol State  . . . . . . . . . . . . .   4
     2.4.  BGP Auto-Discovery Protocol Transport Requirements  . . .   5
     2.5.  Operator Configuration  . . . . . . . . . . . . . . . . .   5
   3.  Design Principle Considerations . . . . . . . . . . . . . . .   6
     3.1.  Transport Considerations  . . . . . . . . . . . . . . . .   6
     3.2.  Auto-Discovery Protocol Timing Considerations . . . . . .   6
     3.3.  Relationship with BGP . . . . . . . . . . . . . . . . . .   7
     3.4.  Session Selection Considerations  . . . . . . . . . . . .   7
     3.5.  Operational Trust Considerations  . . . . . . . . . . . .   7
     3.6.  Error Handling Considerations . . . . . . . . . . . . . .   9
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
     5.1.  BGP Transport Security Considerations . . . . . . . . . .  10
     5.2.  Auto-discovery Protocol Considerations  . . . . . . . . .  10
       5.2.1.  Potential Scopes of an Auto-discovery Protocol  . . .  10
       5.2.2.  Desired Security Properties of the Auto-discovery
               Protocols . . . . . . . . . . . . . . . . . . . . . .  11
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  12
Show full document text