Carry congestion status in BGP extended community
draft-li-idr-congestion-status-extended-community-04

Document Type Active Internet-Draft (individual)
Last updated 2017-03-12
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                                                                Z. Li
Internet-Draft                                              China Mobile
Updates: 4271, 4360, 7153 (if approved)                          J. Dong
Intended status: Standards Track                     Huawei Technologies
Expires: September 13, 2017                               March 12, 2017

           Carry congestion status in BGP extended community
          draft-li-idr-congestion-status-extended-community-04

Abstract

   A new extended community is introduced in this document to carry the
   link congestion status, especially for the exit link of one AS.  It
   is called congestion status extended community.  This extended
   community can be used by the BGP routers or the SDN controllers to
   steer the Internet-access traffic among the exit links.

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 [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 http://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 13, 2017.

Copyright Notice

   Copyright (c) 2017 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

Li & Dong              Expires September 13, 2017               [Page 1]
Internet-Draft    congestion status extended community        March 2017

   (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.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Solution Overview . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Congestion Status Extended Community  . . . . . . . . . . . .   4
   4.  Application Considerations  . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Problem Statement

   Typically the architecture of a large scale ISP's network is multi-
   layered, as illustrated in Figure 1.  The national backbone network
   has its own AS, and each of the province or state network has a
   specific AS.  Backbone network connects all the province or state
   networks together and has several exit links to access the Internet.
   The province or state networks usually have direct exit links to the
   Internet.  The total bandwidth of the backbone exit links is usually
   much bigger than that of the direct exit links in the province or
   state networks.  Thus, the Internet-access traffic is mainly
   transported through the backbone exit links by deploying route
   policies on the ASBR routers in the province or state networks.  The
   ASBR routers in the province or state networks, for example, prefer
   the routes learned from the backbone by setting higher local
   preference for those routes.  However, when the backbone exit links
   are congested due to traffic increasing or delay of the capacity
   expansion, the ASBR routers in the province or state networks do not
   know this, and still deliver Internet-access traffic to the backbone.
   The customer experience deteriorates, the operator, in turn, will
Show full document text