Segment Routing Egress Peer Engineering BGPLS Extensions
draft-previdi-idr-bgpls-segment-routing-epe-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-05-26
Replaced by draft-ietf-idr-bgpls-segment-routing-epe
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)
c

Network Working Group                                    S. Previdi, Ed.
Internet-Draft                                               C. Filsfils
Intended status: Standards Track                                  S. Ray
Expires: November 27, 2014                                      K. Patel
                                                     Cisco Systems, Inc.
                                                            May 26, 2014

        Segment Routing Egress Peer Engineering BGPLS Extensions
             draft-previdi-idr-bgpls-segment-routing-epe-00

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 BGPLS 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
   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

Previdi, et al.         Expires November 27, 2014               [Page 1]
Internet-Draft    Segment Routing EPE BGPLS Extensions          May 2014

   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 November 27, 2014.

Copyright Notice

   Copyright (c) 2014 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.  Peering Segment NLRI-Type . . . . . . . . . . . . . . . . . .   4
     4.1.  Peer Descriptors  . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Peer Attributes . . . . . . . . . . . . . . . . . . . . .   5
   5.  Definition of PeerNode and PeerAdj  . . . . . . . . . . . . .   5
     5.1.  PeerNode Segment (PeerNodeSID)  . . . . . . . . . . . . .   5
     5.2.  PeerAdj Segment (PeerAdjSID)  . . . . . . . . . . . . . .   6
     5.3.  PeerSet Segment (PeerSetSID)  . . . . . . . . . . . . . .   7
   6.  Illustration  . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Reference Diagram . . . . . . . . . . . . . . . . . . . .   7
       6.1.1.  PeerNode for Node D . . . . . . . . . . . . . . . . .   9
       6.1.2.  PeerNode for Node H . . . . . . . . . . . . . . . . .   9
       6.1.3.  PeerNode for Node E . . . . . . . . . . . . . . . . .   9
       6.1.4.  PeerAdj for Node E, Link 1  . . . . . . . . . . . . .  10
       6.1.5.  PeerAdj for Node E, Link 2  . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   8.  Manageability Considerations  . . . . . . . . . . . . . . . .  11
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     11.2.  Informative References . . . . . . . . . . . . . . . . .  11
Show full document text