<BGP Support for Fast Link Status Notification>
draft-sun-idr-bgp-ls-notification-00

Document Type Active Internet-Draft (individual)
Last updated 2017-06-27
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)
INTERNET-DRAFT                                                    M. Sun
Intended Status: <Standard Track>                            B.Pithawala
Expires: December 30,2017                            HUAWEI Technologies
                                                                   F.Gao
                                                               Baidu Inc
                                                            June 28,2017

            <BGP Support for Fast Link Status Notification> 
                  draft-sun-idr-bgp-ls-notification-00

Abstract

   This document describes the use of Border Gateway Protocol (BGP)
   community. This optional transitive community will instruct router to
   monitor itself ports . With this community, controller only needs to
   send route update message once and will get the feedback only if link
   status changes. In particular this community can help controller get
   the link status changing notification much faster than current
   method.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors. All rights reserved.
 

Marcus, et al.          Expires December 30,2017                [Page 1]
INTERNET DRAFT       Fast Link Status Notification          June 28,2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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
     1.1  Large-scale DC Routing Solution . . . . . . . . . . . . . .  3
     1.2 BFD protocol and Hellos Protocol . . . . . . . . . . . . . .  5
   2.  Another Centralized Link Detection Method Based on BGP . . . .  5
     2.1 Basic Principle  . . . . . . . . . . . . . . . . . . . . . .  5
     2.2 Advantages and Benefits of this solution . . . . . . . . . .  7
   3  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  7
   4  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     4.1  Normative References  . . . . . . . . . . . . . . . . . . .  8
     4.2  Informative References  . . . . . . . . . . . . . . . . . .  8
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  8

 

Marcus, et al.          Expires December 30,2017                [Page 2]
INTERNET DRAFT       Fast Link Status Notification          June 28,2017

1  Introduction

   With the advent of micro services application architecture and the
   continued advances in massively scaled distributed systems, majority
   of traffic traversing the data center network is within the data
   center (east-west). This necessitates the data center network to have
   deterministic latency (preferably ultra-low), high scalability, high
   availability and low cost. For those requirements, current large-
   scale data center network is mostly based on CLOS architecture,
   [RFC7938] shows a typical 3 layer(5 stages) CLOS architecture(in
   Figure 1,3 layer means Leaf-Agg-Spine ).

                                     Spine
                                    +-----+
                                    |     |
                                 +--|     |--+
                                 |  +-----+  | +-----------------------+
                     Agg         |           | | Agg              POD  |
                    +-----+      |  +-----+  | |+-----+                |
      +-------------| DEV |------+--|     |--+-+|     |-------------+  |
      |       +-----|  C  |------+  |     |  +-+|     |-----+       |  |
      |       |     +-----+         +-----+    |+-----+     |       |  |
Show full document text