New definition of ISP internal eBGP border using BGP Roles
draft-ymbk-idr-isp-border-00

Document Type Active Internet-Draft (individual)
Last updated 2016-11-13
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                                          A. Azimov
Internet-Draft                                              E. Bogomazov
Intended status: Standards Track                             Qrator Labs
Expires: May 18, 2017                                            R. Bush
                                               Internet Initiative Japan
                                                                K. Patel
                                                                    ????
                                                               K. Sriram
                                                                 US NIST
                                                       November 14, 2016

       New definition of ISP internal eBGP border using BGP Roles
                      draft-ymbk-idr-isp-border-00

Abstract

   This document proposes a new definition of ISP borders using BGP
   Roles.  It may be used to improve the BGP best path selection
   algorithm for better support of hot-potato routing between different
   internal ASNs of an ISP.  It may also be used to enable transmission
   of local attributes between different internal ASNs of an ISP.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
   be interpreted as described in RFC 2119 [RFC2119] only when they
   appear in all upper case.  They may also appear in lower or mixed
   case as English words, without normative meaning.

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 May 18, 2017.

Azimov, et al.            Expires May 18, 2017                  [Page 1]
Internet-Draft          Network border definition          November 2016

Copyright Notice

   Copyright (c) 2016 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Changes in BGP decision process . . . . . . . . . . . . . . .   3
   3.  Local Attributes Transmission . . . . . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .   3
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   The BGP best path selection algorithm (Section 9.1.2.2 of [RFC4271])
   has a very clear definition of a network border: different ASNs -
   different networks.  It differs from some real world situations when
   two networks become one business entity and want to operate as one
   network.

   Today BGP does not provide any robust or automated support for such
   merging networks:

   o  There is no support for carrying local attributes through this
      border,

   o  Hot-potato routing, implemented by eBGP being preferred to iBGP,
      does not work, and

   o  Route Leak prevention inside such a united network can not be
      easily automated.

   In [I-D.ymbk-idr-bgp-open-policy] BGP Roles were introduced - a
   configuration option that strongly enforces agreement on real-world
   business relations between two BGP speakers.  This configuration
   option can accept values of: Peering, Customer, Provider, Internal,

Azimov, et al.            Expires May 18, 2017                  [Page 2]
Internet-Draft          Network border definition          November 2016
Show full document text