FYI, just a refresh.
s. Begin forwarded message: > From: <[email protected]> > Subject: New Version Notification for > draft-filsfils-spring-segment-routing-use-cases-01.txt > Date: October 21, 2014 2:28:34 PM GMT+02:00 > > > A new version of I-D, draft-filsfils-spring-segment-routing-use-cases-01.txt > has been successfully submitted by Stefano Previdi and posted to the > IETF repository. > > Name: draft-filsfils-spring-segment-routing-use-cases > Revision: 01 > Title: Segment Routing Use Cases > Document date: 2014-10-21 > Group: Individual Submission > Pages: 35 > URL: > http://www.ietf.org/internet-drafts/draft-filsfils-spring-segment-routing-use-cases-01.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-01 > Diff: > http://www.ietf.org/rfcdiff?url2=draft-filsfils-spring-segment-routing-use-cases-01 > > 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
