Multi Instance BGP
draft-raszuk-mi-bgp-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
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                        October 22, 2018
Expires: April 25, 2019

                           Multi Instance BGP
                         draft-raszuk-mi-bgp-00

Abstract

   As the number of operational use cases of BGP grows there is demand
   to increase the level of separation and processing independence
   between various address families carried by BGP today.  This document
   augments base BGP specification in allowing local configuration of
   BGP port number by the operator to run parallel fully disjoined BGP
   instances allowing full processing separation between them.

   While local BGP implementation may already assure BGP process or
   thread robustnes the general aim here is to allow similar level of
   groups of BGP address families independence when running BGP code on
   general purpose hardware as well as x86 based route reflectors.

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 April 25, 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

Raszuk                   Expires April 25, 2019                 [Page 1]
Internet-Draft                   mi-bgp                     October 2018

   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.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Today's operation . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Related work  . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Multi Instance Proposal . . . . . . . . . . . . . . . . . . .   4
     5.1.  Protocol changes  . . . . . . . . . . . . . . . . . . . .   5
     5.2.  BGP Identifier BGP peering address  . . . . . . . . . . .   5
   6.  Summary of benefits . . . . . . . . . . . . . . . . . . . . .   5
   7.  Applications  . . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security considerations . . . . . . . . . . . . . . . . . . .   6
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Contributors

   The current document has been created based on parent document
   Transport Instance BGP.  Below is the list of contributors who
   contributed to the previous document:

      Keyur Patel, Arrcus Inc., 2077 Gateway Place Suite 400, San Jose,
      CA, 95119, US, Email: keyur@arrcus.com

      Bruno Decraene, France Telecom, 38 rue du General Leclerc, Issy
      Moulineaux cedex 9, France, Email: bruno.decraene@orange-
      ftgroup.com

      Jakob Heitz, Cisco, 170 Tasman Dr, San Jose, CA 95134, US Email:
      jheitz@cisco.com

      Thomas D.  Nadeau

      Jie Dong, Huawei Technologies Co.,Ltd, KuiKe Building, No.9 Xinxi
      Rd., Beijing, Hai-Dian District, 100085, P.R.  China, Email:
      dongjie_dj@huawei.com

Raszuk                   Expires April 25, 2019                 [Page 2]
Internet-Draft                   mi-bgp                     October 2018

      Yoshinobu Matsuzaki, Internet Initiative Japan Inc., Jinbocho
      Mitsui Bldg., 1-105 Kanda Jinbo-cho, Tokyo, Chiyoda-ku, Japan,
      Email: maz@iij.ad.jp

2.  Introduction
Show full document text