Segment Routing Egress Peer Engineering BGP-LS Extensions
draft-ietf-idr-bgpls-segment-routing-epe-01

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2015-12-03
Replaces draft-previdi-idr-bgpls-segment-routing-epe
Stream IETF
Intended RFC status Proposed Standard
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                                    S. Previdi, Ed.
Internet-Draft                                               C. Filsfils
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: June 5, 2016                                             S. Ray
                                                  Individual Contributor
                                                                K. Patel
                                                     Cisco Systems, Inc.
                                                                 J. Dong
                                                                 M. Chen
                                                     Huawei Technologies
                                                        December 3, 2015

       Segment Routing Egress Peer Engineering BGP-LS Extensions
              draft-ietf-idr-bgpls-segment-routing-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 outline a BGP-LS extension for exporting BGP egress
   point topology information (including its peers, interfaces and
   peering ASs) in a way that is exploitable in order to compute
   efficient Egress Point Engineering policies and strategies.

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

Previdi, et al.           Expires June 5, 2016                  [Page 1]
Internet-Draft    Segment Routing EPE BGP-LS Extensions    December 2015

   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 June 5, 2016.

Copyright Notice

   Copyright (c) 2015 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.  Segment Routing Documents . . . . . . . . . . . . . . . . . .   3
   3.  BGP Peering Segments  . . . . . . . . . . . . . . . . . . . .   3
   4.  Link NLRI for EPE Connectivity Description  . . . . . . . . .   4
     4.1.  BGP Router ID and Member ASN  . . . . . . . . . . . . . .   5
     4.2.  EPE Node Descriptors  . . . . . . . . . . . . . . . . . .   5
     4.3.  Link Attributes . . . . . . . . . . . . . . . . . . . . .   6
   5.  Peer Node and Peer Adjacency Segments . . . . . . . . . . . .   8
     5.1.  Peer Node Segment (Peer-Node-SID) . . . . . . . . . . . .   9
     5.2.  Peer Adjacency Segment (Peer-Adj-SID) . . . . . . . . . .  10
     5.3.  Peer Set Segment  . . . . . . . . . . . . . . . . . . . .  11
   6.  Illustration  . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Reference Diagram . . . . . . . . . . . . . . . . . . . .  11
       6.1.1.  Peer Node Segment for Node D  . . . . . . . . . . . .  13
       6.1.2.  Peer Node Segment for Node H  . . . . . . . . . . . .  14
       6.1.3.  Peer Node Segment for Node E  . . . . . . . . . . . .  14
       6.1.4.  Peer Adjacency Segment for Node E, Link 1 . . . . . .  14
       6.1.5.  Peer Adjacency Segment for Node E, Link 2 . . . . . .  15
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
Show full document text