refreshed with fixed typo's. s.
Begin forwarded message: > From: <[email protected]> > Subject: New Version Notification for > draft-filsfils-spring-segment-routing-ldp-interop-02.txt > Date: September 12, 2014 2:14:10 PM GMT+02:00 > > A new version of I-D, draft-filsfils-spring-segment-routing-ldp-interop-02.txt > has been successfully submitted by Stefano Previdi and posted to the > IETF repository. > > Name: draft-filsfils-spring-segment-routing-ldp-interop > Revision: 02 > Title: Segment Routing interoperability with LDP > Document date: 2014-09-12 > Group: Individual Submission > Pages: 16 > URL: > http://www.ietf.org/internet-drafts/draft-filsfils-spring-segment-routing-ldp-interop-02.txt > Status: > https://datatracker.ietf.org/doc/draft-filsfils-spring-segment-routing-ldp-interop/ > Htmlized: > http://tools.ietf.org/html/draft-filsfils-spring-segment-routing-ldp-interop-02 > Diff: > http://www.ietf.org/rfcdiff?url2=draft-filsfils-spring-segment-routing-ldp-interop-02 > > Abstract: > A Segment Routing (SR) 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 to the SR domain. > > The Segment Routing architecture can be directly applied to the MPLS > data plane with no change in the forwarding plane. This drafts > describes how Segment Routing operates in a network where LDP is > deployed and in the case where SR-capable and non-SR-capable nodes > coexist. > > > > > > 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
