Hi,

There appears to be no explicit typing for the SID.

Clearly it can be a MPLS label, an IPv6 address, but in the future it might be something else. How does a parser know the SID type?

Thanks

Stewart


On 15/12/2017 18:30, Jeff Tantsura wrote:
Les,

Thanks for doing that, great!

Cheers,
Jeff

-----Original Message-----
From: Isis-wg <[email protected]> on behalf of "Les Ginsberg (ginsberg)" 
<[email protected]>
Date: Friday, December 15, 2017 at 10:09
To: "[email protected]" <[email protected]>
Subject: Re: [Isis-wg] I-D Action: 
draft-ietf-isis-segment-routing-extensions-14.txt

     I have assumed the editor role from Stefano.
This new version restores the support for SID/Label sub-TLV in the SID/Label Binding TLV - needed to support Mirror Context (as requested by Chris Bowers).
     It also addresses some IANA related issues - including the conflicting 
code point w the MSD draft.
Some other minor editorial changes have been made. Thanx. Les > -----Original Message-----
     > From: Isis-wg [mailto:[email protected]] On Behalf Of internet-
     > [email protected]
     > Sent: Friday, December 15, 2017 9:37 AM
     > To: [email protected]
     > Cc: [email protected]
     > Subject: [Isis-wg] I-D Action: 
draft-ietf-isis-segment-routing-extensions-
     > 14.txt
     >
     >
     > A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
     > This draft is a work item of the IS-IS for IP Internets WG of the IETF.
     >
     >         Title           : IS-IS Extensions for Segment Routing
     >         Authors         : Stefano Previdi
     >                           Les Ginsberg
     >                           Clarence Filsfils
     >                           Ahmed Bashandy
     >                           Hannes Gredler
     >                           Stephane Litkowski
     >                           Bruno Decraene
     >                           Jeff Tantsura
     >       Filename        : draft-ietf-isis-segment-routing-extensions-14.txt
     >       Pages           : 34
     >       Date            : 2017-12-15
     >
     > 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).
     >
     >    This draft describes the necessary IS-IS extensions that need to be
     >    introduced for Segment Routing operating on an MPLS data-plane.
     >
     >
     >
     > The IETF datatracker status page for this draft is:
     > 
https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/
     >
     > There are also htmlized versions available at:
     > https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-14
     > https://datatracker.ietf.org/doc/html/draft-ietf-isis-segment-routing-
     > extensions-14
     >
     > A diff from the previous version is available at:
     > https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-segment-routing-
     > extensions-14
     >
     >
     > 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.
     >
     > Internet-Drafts are also available by anonymous FTP at:
     > ftp://ftp.ietf.org/internet-drafts/
     >
     > _______________________________________________
     > Isis-wg mailing list
     > [email protected]
     > https://www.ietf.org/mailman/listinfo/isis-wg
_______________________________________________
     Isis-wg mailing list
     [email protected]
     https://www.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/isis-wg

Reply via email to