Cumulative DMZ Link Bandwidth and load-balancing
draft-mohanty-bess-ebgp-dmz-02

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
BESS WorkGroup                                                S. Mohanty
Internet-Draft                                               A. Millisor
Intended status: Informational                             Cisco Systems
Expires: January 14, 2021                                      A. Vayner
                                                                 Nutanix
                                                              A. Gattani
                                                                 A. Kini
                                                         Arista Networks
                                                           July 13, 2020

            Cumulative DMZ Link Bandwidth and load-balancing
                     draft-mohanty-bess-ebgp-dmz-02

Abstract

   The DMZ Link Bandwidth draft provides a way to load-balance traffic
   to a destination (which is in a different AS than the source) which
   is reachable via more than one path.  Typically, the link bandwidth
   (either configured on the link of the EBGP egress interface or set
   via a policy) is encoded in an extended community and then sent to
   the IBGP peer which employs multi-path.  The link-bandwidth value is
   then extracted from the path extended community and is used as a
   weight in the FIB, which does the load-balancing.  This draft extends
   the usage of the DMZ link bandwidth to another setting where the
   ingress BGP speaker requires knowledge of the cumulative bandwidth
   while doing the load-balancing.  The draft also proposes neighbor-
   level knobs to enable the link bandwidth extended community to be
   regenerated and then advertised to EBGP peers to override the default
   behavior of not advertising optional non-transitive attributes to
   EBGP peers.

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 January 14, 2021.

Mohanty, et al.         Expires January 14, 2021                [Page 1]
Internet-Draft        Cumulative DMZ Link Bandwidth            July 2020

Copyright Notice

   Copyright (c) 2020 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem Description . . . . . . . . . . . . . . . . . . . . .   3
   4.  Large Scale Data Centers Use Case . . . . . . . . . . . . . .   6
   5.  Non-Conforming BGP Topologies . . . . . . . . . . . . . . . .   8
   6.  Protocol Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Operational Considerations  . . . . . . . . . . . . . . . . .  10
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The Demilitarized Zone (DMZ) Link Bandwidth (LB) extended community
   along with the multi-path feature can be used to provide unequal cost
   load-balancing as per user control.  In [I-D.ietf-idr-link-bandwidth]
   the EBGP egress link bandwidth is encoded in the link bandwidth
   extended community and sent along with the BGP update to the IBGP
   peer.  It is assumed that either a labeled path exists to each of the
   EBGP links or alternatively the IGP cost to each link is the same.
   When the same prefix/net is advertised into the receiving AS via
   different egress-points or next-hops, the receiving IBGP peer that
   employs multi-path will use the value of the DMZ LB to load-balance
Show full document text