BGP Automated Session Setup (BGP-ASS)
draft-raszuk-idr-bgp-auto-session-setup-00

Document Type Active Internet-Draft (individual)
Last updated 2018-07-16
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)
IDR Working Group                                         R. Raszuk, Ed.
Internet-Draft                                              Bloomberg LP
Intended status: Standards Track                           July 16, 2018
Expires: January 17, 2019

                 BGP Automated Session Setup (BGP-ASS)
               draft-raszuk-idr-bgp-auto-session-setup-00

Abstract

   This document proposes a solution for BGP deployments in some
   specific environments to automatically establish BGP sessions without
   need for manual peer configuration.

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 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.

Raszuk                  Expires January 17, 2019                [Page 1]
Internet-Draft   draft-raszuk-idr-bgp-auto-session-setup       July 2018

Table of Contents

   1.  Definitions of Terms Used in This Memo  . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Proposed Solution . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Loopbacks reachability bootstrapping  . . . . . . . . . . . .   3
   5.  ECMP routes recursion . . . . . . . . . . . . . . . . . . . .   4
   6.  Scalability . . . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Advantages to alternative proposals . . . . . . . . . . . . .   4
   8.  Changes to BGP Finite State Machine . . . . . . . . . . . . .   5
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   5
     12.2.  Informative References . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Definitions of Terms Used in This Memo

   NLRI -   Network Layer Reachability Information.

   RIB -   Routing Information Base.

   AS -   Autonomous System number.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "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.

2.  Introduction

   The popularity of use of BGP in number of data centers or campus
   deployments where BGP is being used as/instead of IGP brings
   operational challenges associated with setup of BGP peering relations

   This proposal aims on automating the BGP session bring-up without
   aprior knowledge of the peer's IP addresses by use of existing BGP
   protocol.

3.  Proposed Solution

   When BGP attempts to establish the EBGP sessions with unknown peers
   router will start sending BGP Session Explorer (BSE) packets which
   are to be regular BGP session establishment packets containing plain
   BGP OPEN Message except instead of regular peer address a multicast

Raszuk                  Expires January 17, 2019                [Page 2]
Internet-Draft   draft-raszuk-idr-bgp-auto-session-setup       July 2018

   address will be used 224.0.0.2 "All Routers on this Subnet" as UDP
   destination address.  Destination port of this UDP packets is to be
   assigned by IANA.  Source address will be selected by the operator
   either local interface address (when establishing plain p2p relation)
   or loopback address (when establishing peering between loopback
Show full document text