just refreshed the draft. Comments are appreciated.
Thanks. s. > Begin forwarded message: > > From: <internet-dra...@ietf.org> > Subject: New Version Notification for > draft-filsfils-spring-sr-recursing-info-02.txt > Date: April 26, 2016 at 6:18:35 AM GMT+2 > To: Clarence Filsfils <cfils...@cisco.com>, Peter Psenak <ppse...@cisco.com>, > Les Ginsberg <ginsb...@cisco.com>, Stefano Previdi <sprev...@cisco.com> > > > A new version of I-D, draft-filsfils-spring-sr-recursing-info-02.txt > has been successfully submitted by Stefano Previdi and posted to the > IETF repository. > > Name: draft-filsfils-spring-sr-recursing-info > Revision: 02 > Title: Segment Routing Recursive Information > Document date: 2016-04-25 > Group: Individual Submission > Pages: 8 > URL: > https://www.ietf.org/internet-drafts/draft-filsfils-spring-sr-recursing-info-02.txt > Status: > https://datatracker.ietf.org/doc/draft-filsfils-spring-sr-recursing-info/ > Htmlized: > https://tools.ietf.org/html/draft-filsfils-spring-sr-recursing-info-02 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-filsfils-spring-sr-recursing-info-02 > > Abstract: > Segment Routing (SR) allows for a flexible definition of end-to-end > paths within IGP topologies by encoding paths as sequences of > topological sub-paths, called "segments". These segments are > advertised by the link-state routing protocols (IS-IS and OSPF). > > There are use cases where it is desirable to utilize a SID associated > with a given node in order to transport traffic destined to different > local services supported by such node. This document defines the > mechanism to do so and illustrates it. > > > > > > 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 spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
