Architecture for Use of BGP as Central Controller
draft-cth-rtgwg-bgp-control-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)
Network Working Group                                             Y. Luo
Internet-Draft                                                     L. Qu
Intended status: Informational                    China Telcom Co., Ltd.
Expires: April 25, 2019                                         X. Huang
                                                                 Tencent
                                                                 H. Chen
                                                               S. Zhuang
                                                                   Z. Li
                                                                  Huawei
                                                        October 22, 2018

           Architecture for Use of BGP as Central Controller
                     draft-cth-rtgwg-bgp-control-00

Abstract

   BGP is a core part of a network including Software-Defined Networking
   (SDN) system.  It has the traffic engineering information on the
   network topology and can compute optimal paths for a given traffic
   flow acrosss the network.

   This document describes the architecture for BGP as a central
   controller.  A BGP-based central controller can simplify the
   operations on the network and use network resources efficiently for
   providing services with high quality.

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
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Luo, et al.              Expires April 25, 2019                 [Page 1]
Internet-Draft       Architecture for BGP Controller        October 2018

   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
   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 . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Building Blocks . . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  TEDB  . . . . . . . . . . . . . . . . . . . . . . . .   5
       3.1.2.  SLDB  . . . . . . . . . . . . . . . . . . . . . . . .   5
       3.1.3.  TPDB  . . . . . . . . . . . . . . . . . . . . . . . .   5
       3.1.4.  CSPF  . . . . . . . . . . . . . . . . . . . . . . . .   6
       3.1.5.  TM  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  One Controller  . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Controller Cluster  . . . . . . . . . . . . . . . . . . .   8
     3.4.  Hierarchical Controllers  . . . . . . . . . . . . . . . .  10
   4.  Application Scenarios . . . . . . . . . . . . . . . . . . . .  11
     4.1.  Business-oriented Traffic Steering  . . . . . . . . . . .  11
       4.1.1.  Preferential Users  . . . . . . . . . . . . . . . . .  11
       4.1.2.  Preferential Services . . . . . . . . . . . . . . . .  12
     4.2.  Traffic Congestion Mitigation . . . . . . . . . . . . . .  13
       4.2.1.  Congestion Mitigation in Core . . . . . . . . . . . .  14
       4.2.2.  Congestion Mitigation among ISPs  . . . . . . . . . .  14
       4.2.3.  Congestion Mitigation at International Edge . . . . .  15
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  16
Show full document text