Segment Routing Centralized BGP Peer Engineering
draft-ietf-spring-segment-routing-central-epe-01

The information below is for an old version of the document
Document Type Active Internet-Draft (spring WG)
Last updated 2016-09-09 (latest revision 2016-03-21)
Replaces draft-filsfils-spring-segment-routing-central-epe
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Martin Vigoureux
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Martin Vigoureux" <martin.vigoureux@nokia.com>
Network Working Group                                   C. Filsfils, Ed.
Internet-Draft                                           S. Previdi, Ed.
Intended status: Informational                       Cisco Systems, Inc.
Expires: September 22, 2016                                     E. Aries
                                                                Facebook
                                                             D. Ginsburg
                                                            D. Afanasiev
                                                                  Yandex
                                                          March 21, 2016

            Segment Routing Centralized BGP Peer Engineering
            draft-ietf-spring-segment-routing-central-epe-01

Abstract

   Segment Routing (SR) leverages source routing.  A node steers a
   packet through a controlled set of instructions, called segments, by
   prepending the packet with an SR header.  A segment can represent any
   instruction topological or service-based.  SR allows to enforce a
   flow through any topological path and service chain while maintaining
   per-flow state only at the ingress node of the SR domain.

   The Segment Routing architecture can be directly applied to the MPLS
   dataplane with no change on the forwarding plane.  It requires minor
   extension to the existing link-state routing protocols.

   This document illustrates the application of Segment Routing to solve
   the BGP Peer Engineering (BGP-PE) requirement.  The SR-based BGP-PE
   solution allows a centralized (SDN) controller to program any egress
   peer policy at ingress border routers or at hosts within the domain.
   This document is on the informational track.

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/.

Filsfils, et al.       Expires September 22, 2016               [Page 1]
Internet-DraSegment Routing Centralized BGP Peer Engineering  March 2016

   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 22, 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Segment Routing Documents . . . . . . . . . . . . . . . .   3
     1.2.  Problem Statement . . . . . . . . . . . . . . . . . . . .   4
   2.  BGP Peering Segments  . . . . . . . . . . . . . . . . . . . .   6
   3.  Distribution of External Topology and TE Information using
       BGP-LS  . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  BGP-PE Router advertising the Peer D and its PeerNode SID   7
     3.2.  BGP-PE Router advertising the Peer E and its PeerNode SID   7
     3.3.  BGP-PE Router advertising the Peer F and its PeerNode SID   8
     3.4.  BGP-PE Router advertising a first PeerAdj to Peer F . . .   8
     3.5.  BGP-PE Router advertising a second PeerAdj to Peer F  . .   9
     3.6.  Fast Reroute (FRR)  . . . . . . . . . . . . . . . . . . .   9
   4.  BGP-PE Controller . . . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Valid Paths From Peers  . . . . . . . . . . . . . . . . .  10
     4.2.  Intra-Domain Topology . . . . . . . . . . . . . . . . . .  11
     4.3.  External Topology . . . . . . . . . . . . . . . . . . . .  11
     4.4.  SLA characteristics of each peer  . . . . . . . . . . . .  11
     4.5.  Traffic Matrix  . . . . . . . . . . . . . . . . . . . . .  12
     4.6.  Business Policies . . . . . . . . . . . . . . . . . . . .  12
     4.7.  BGP-PE Policy . . . . . . . . . . . . . . . . . . . . . .  12
Show full document text