[spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-09.txt

internet-drafts@ietf.org Thu, 21 December 2017 14:17 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: spring@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151386583789.12883.13963256301639338142@ietfa.amsl.com>
Date: Thu, 21 Dec 2017 06:17:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/bCSJuWNVW_qt41s71XhZoFzUug0>
Subject: [spring] I-D Action: draft-ietf-spring-segment-routing-central-epe-09.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Source Packet Routing in Networking WG of the IETF.

        Title           : Segment Routing Centralized BGP Egress Peer Engineering
        Authors         : Clarence Filsfils
                          Stefano Previdi
                          Gaurav Dawra
                          Ebben Aries
                          Dmitry Afanasiev
	Filename        : draft-ietf-spring-segment-routing-central-epe-09.txt
	Pages           : 19
	Date            : 2017-12-21

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 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 a
   minor extension to the existing link-state routing protocols.

   This document illustrates the application of Segment Routing to solve
   the BGP Egress Peer Engineering (BGP-EPE) requirement.  The SR-based
   BGP-EPE solution allows a centralized (Software Defined Network, SDN)
   controller to program any egress peer policy at ingress border
   routers or at hosts within the domain.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-central-epe/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-spring-segment-routing-central-epe-09
https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-central-epe-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-central-epe-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[spring] I-D Action: draft-ietf-spring-segment-ro… internet-drafts