Hi, I just re-published the segment-routing use cases draft with the appropriate name (with -spring- on it) and updated references.
Thanks. s. Begin forwarded message: > From: <[email protected]> > Subject: New Version Notification for > draft-filsfils-spring-segment-routing-use-cases-00.txt > Date: March 27, 2014 1:52:55 PM GMT+01:00 > To: Sriganesh Kini <[email protected]>, Rob Shakir > <[email protected]>, Pierre Francois <[email protected]>, "Wim > Henderickx" <[email protected]>, Stefano Previdi > <[email protected]>, Saku Ytti <[email protected]>, Edward Crabbe > <[email protected]>, Jeff Tantsura <[email protected]>, "Clarence > Filsfils" <[email protected]>, Edward Crabbe <[email protected]>, Saku Ytti > <[email protected]>, Stefano Previdi <[email protected]>, Wim Henderickx > <[email protected]>, Bruno Decraene > <[email protected]>, Stephane Litkowski > <[email protected]>, Clarence Filsfils <[email protected]>, > Bruno Decraene <[email protected]>, Igor Milojevic > <[email protected]>, Sriganesh Kini <[email protected]>, > Martin Horneffer <[email protected]>, Jeff Tantsura > <[email protected]>, Rob Shakir <[email protected]>, Igor Milojevic > <[email protected]>, Pierre Francois <[email protected]>, Mart in Horneffer <[email protected]>, Stephane Litkowski <[email protected]> > > > A new version of I-D, draft-filsfils-spring-segment-routing-use-cases-00.txt > has been successfully submitted by Stefano Previdi and posted to the > IETF repository. > > Name: draft-filsfils-spring-segment-routing-use-cases > Revision: 00 > Title: Segment Routing Use Cases > Document date: 2014-03-27 > Group: Individual Submission > Pages: 36 > URL: > http://www.ietf.org/internet-drafts/draft-filsfils-spring-segment-routing-use-cases-00.txt > Status: > https://datatracker.ietf.org/doc/draft-filsfils-spring-segment-routing-use-cases/ > Htmlized: > http://tools.ietf.org/html/draft-filsfils-spring-segment-routing-use-cases-00 > > > Abstract: > Segment Routing (SR) leverages the source routing and tunneling > paradigms. 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. Segment > Routing can also be applied to IPv6 with a new type of routing > extension header. > > > > > > 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 > _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
