Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-14.txt

["Les Ginsberg (ginsberg)" <[e-mail]>]

Stewart -

The draft is only covering the extensions for SR-MPLS - so IPv6 address is NOT an option for the SID advertisements defined in this draft.
(This restriction is explicitly stated in the Abstract and the Introduction.)

In the case of the Prefix-SID sub-TLV (https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-15#section-2.1 ) the state of the V-flag indicates whether we are advertising a 20 bit MPLS label or a 32 bit index.

In the case of the SID/Label sub-TLV (https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-15#section-2.3 ) the length indicates whether the value is a label or an index.

For SRv6 there is separate draft (https://datatracker.ietf.org/doc/draft-bashandy-isis-srv6-extensions/ ) and a new TLV is defined to advertise an IPv6 SID.

   Les

> -----Original Message-----
> From: Stewart Bryant [mailto:[e-mail]]
> Sent: Friday, December 22, 2017 9:30 AM
> To: Jeff Tantsura <[e-mail]>; Les Ginsberg (ginsberg)
> <[e-mail]>; [e-mail]
> Subject: Re: [Isis-wg] I-D Action: draft-ietf-isis-segment-routing-extensions-
> 14.txt
> 
> 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 <[e-mail]> on behalf of "Les Ginsberg
> > (ginsberg)" <[e-mail]>
> > Date: Friday, December 15, 2017 at 10:09
> > To: "[e-mail]" <[e-mail]>
> > 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:[e-mail]] On Behalf Of internet-
> >      > [e-mail]
> >      > Sent: Friday, December 15, 2017 9:37 AM
> >      > To: [e-mail]
> >      > Cc: [e-mail]
> >      > 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
> >      > [e-mail]
> >      > https://www.ietf.org/mailman/listinfo/isis-wg
> >
> >      _______________________________________________
> >      Isis-wg mailing list
> >      [e-mail]
> >      https://www.ietf.org/mailman/listinfo/isis-wg
> >
> >
> >
> > _______________________________________________
> > Isis-wg mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/isis-wg