BGP Link Bandwidth Extended Community
draft-ietf-idr-link-bandwidth-07

Document Type Active Internet-Draft (idr WG)
Last updated 2018-03-05
Replaces draft-rfernando-idr-link-bandwidth
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       P. Mohapatra
Internet-Draft                                          Sproute Networks
Intended status: Standards Track                             R. Fernando
Expires: September 6, 2018                                 Cisco Systems
                                                           March 5, 2018

                 BGP Link Bandwidth Extended Community
                  draft-ietf-idr-link-bandwidth-07.txt

Abstract

   This document describes an application of BGP extended communities
   that allows a router to perform unequal cost load balancing.

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 September 6, 2018.

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.

Mohapatra & Fernando    Expires September 6, 2018               [Page 1]
Internet-Draft               Link Bandwidth                   March 2018

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Link Bandwidth Extended Community . . . . . . . . . . . . . .   2
   3.  Deployment Considerations . . . . . . . . . . . . . . . . . .   3
   4.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   When a BGP speaker receives multiple paths from its internal peers,
   it could select more than one path to send traffic to.  In doing so,
   it might be useful to provide the speaker with information that would
   help it distribute the traffic based on the bandwidth of the external
   (DMZ) link.  This document suggests that the external link bandwidth
   be carried in the network using a new extended community [RFC4360]  -
   the link bandwidth extended community.

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

2.  Link Bandwidth Extended Community

   When a BGP speaker receives a route from an external neighbor and
   advertises this route (via IBGP) to internal neighbors, as part of
   this advertisement the router may carry the cost to reach the
   external neighbor.  The cost can be either configured per neighbor or
   derived from the bandwidth of the link that connects the router to a
   directly connected external neighbor.  This value is carried in the

Mohapatra & Fernando    Expires September 6, 2018               [Page 2]
Internet-Draft               Link Bandwidth                   March 2018

   Link Bandwidth Extended Community.  No more than one link bandwidth
Show full document text