Egress Peer Engineering using BGP-LU
draft-gredler-idr-bgplu-epe-09

Document Type Active Internet-Draft (individual)
Last updated 2017-04-04
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Inter-Domain Routing                                     H. Gredler, Ed.
Internet-Draft                                              RtBrick Inc.
Intended status: Informational                          K. Vairavakkalai
Expires: October 6, 2017                                 C. Ramachandran
                                                          B. Rajagopalan
                                                                E. Aries
                                                  Juniper Networks, Inc.
                                                                 L. Fang
                                                                    eBay
                                                          April 04, 2017

                  Egress Peer Engineering using BGP-LU
                     draft-gredler-idr-bgplu-epe-09

Abstract

   The MPLS source routing paradigm provides path control for both
   intra- and inter- Autonomous System (AS) traffic.  RSVP-TE is
   utilized for intra-AS path control.  This documents outlines how MPLS
   routers may use the BGP labeled unicast protocol (BGP-LU) for doing
   traffic-engineering on inter-AS 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 RFC 2119 [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 October 6, 2017.

Gredler, et al.          Expires October 6, 2017                [Page 1]
Internet-Draft    Egress Peer Engineering using BGP-LU        April 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
   (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
   2.  Motivation, Rationale and Applicability . . . . . . . . . . .   3
   3.  Sample Topology . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Loopback IP addresses and Router-IDs  . . . . . . . . . .   4
     3.2.  Link IP addresses . . . . . . . . . . . . . . . . . . . .   5
   4.  Service Route Advertisement . . . . . . . . . . . . . . . . .   5
   5.  Egress Next-hop Advertisement . . . . . . . . . . . . . . . .   5
     5.1.  iBGP meshing and BGP nexthop rewrite policy . . . . . . .   6
     5.2.  Single-hop eBGP . . . . . . . . . . . . . . . . . . . . .   7
     5.3.  Multi-hop eBGP  . . . . . . . . . . . . . . . . . . . . .   8
     5.4.  Grouping of Peers . . . . . . . . . . . . . . . . . . . .   9
     5.5.  Supporting Summarization at ASBR  . . . . . . . . . . . .  10
       5.5.1.  Locality forwarding bias  . . . . . . . . . . . . . .  10
       5.5.2.  Label per group of peers sharing a locality . . . . .  10
   6.  Egress Link Protection  . . . . . . . . . . . . . . . . . . .  10
     6.1.  FRR backup routes . . . . . . . . . . . . . . . . . . . .  10
       6.1.1.  Local links . . . . . . . . . . . . . . . . . . . . .  11
       6.1.2.  Remote BGP-LU labels  . . . . . . . . . . . . . . . .  11
       6.1.3.  Local IP forwarding tables  . . . . . . . . . . . . .  11
   7.  Dynamic link utilization  . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  12
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
Show full document text