Subject: [spring] Fwd: New Version Notification for draft-filsfils-spring-segment-routing-central-epe-02.txt

From: "Stefano Previdi (sprevidi)" <[email-masked]>
Date: Fri, 4 Jul 2014 06:54:51 +0000

All,

This is the Segment Routing Egress Peer Engineering draft.

Thanks.
s.

Begin forwarded message:

> From: <[email-masked]>
> Subject: New Version Notification for draft-filsfils-spring-segment-routing-central-epe-02.txt
> Date: July 4, 2014 8:48:23 AM GMT+02:00
> To: Stefano Previdi <[email-masked]>, "[email-masked]" <[email-masked]>, "Steve Shaw" <[email-masked]>, Dmitry Afanasiev <[email-masked]>, Ebben Aries <[email-masked]>, Dmitry Afanasiev <[email-masked]>, Clarence Filsfils <[email-masked]>, Daniel Ginsburg <[email-masked]>, Keyur Patel <[email-masked]>, Stefano Previdi <[email-masked]>, Keyur Patel <[email-masked]>, Clarence Filsfils <[email-masked]>, Ebben Aries <[email-masked]>, Daniel Ginsburg <[email-masked]>
> 
> 
> A new version of I-D, draft-filsfils-spring-segment-routing-central-epe-02.txt
> has been successfully submitted by Stefano Previdi and posted to the
> IETF repository.
> 
> Name:		draft-filsfils-spring-segment-routing-central-epe
> Revision:	02
> Title:		Segment Routing Centralized Egress Peer Engineering
> Document date:	2014-07-04
> Group:		Individual Submission
> Pages:		19
> URL:            http://www.ietf.org/internet-drafts/draft-filsfils-spring-segment-routing-central-epe-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-filsfils-spring-segment-routing-central-epe/
> Htmlized:       http://tools.ietf.org/html/draft-filsfils-spring-segment-routing-central-epe-02
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-filsfils-spring-segment-routing-central-epe-02
> 
> 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 Egress Peer Engineering (EPE) requirement.  The SR-based EPE
>   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.
> 
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
>