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

Les,

Thanks for updating the text.  Below are a few proposed changes/additions
to the current text that are mainly to clarify a few things.

Thanks,
Chris

=============
2.4.4.  Mapping Server Prefix-SID

   The Prefix-SID sub-TLV (suggested value 3) is defined in Section 2.1
   and contains the SID/index/label value associated with the prefix and
   range.  The Prefix-SID SubTLV MUST be present in the SID/Label
   Binding TLV.

Proposed last sentence:

The Prefix-SID Sub-TLV MUST be present in the SID/Label Binding TLV unless the
the M-flag is set in the Flags field of the parent TLV.

=============
Existing text:

   The SID/Label sub-TLV may be present in the following TLVs/sub-TLVs
   defined in this document:

   SR Capability (Section 3.1)

   SRLB (Section 3.3)

   Binding TLV (Section 2.4)

   MT Binding TLV (Section 2.5)

   Note that when used in the SR Capability and SRLB sub-TLVs the code
   point used is the same as the sub-TLV code point assigned by IANA in
   the sub-TLVs for TLV 149 and 150 registry.

Proposed text:

   The SID/Label sub-TLV may be present in the following TLVs/sub-TLVs
   defined in this document:

   SR-Capabilities Sub-TLV (Section 3.1)

   SR Local Block Sub-TLV (Section 3.3)

   SID/Label Binding TLV (Section 2.4)

   Multi-Topology SID/Label Binding TLV (Section 2.5)

Note that the code point used for the SID/Label Sub-TLV in the
SR-Capabilities Sub-TLV and the SR Local Block sub-TLV is the same as
the code point used for the SID/Label Sub-TLV in the SID/Label Binding TLV
and the Multi-Topology SID/Label Binding TLV. This code point is assigned
by IANA in the “sub-TLVs for TLV 149 and 150” registry

===============
3.3.  SR Local Block Sub-TLV

(add after first paragraph)
   The SR Local Block sub-TLV is inserted into the IS-IS Router Capability
   TLV-242 that is defined in [RFC7981].

===============
3.3.  SR Local Block Sub-TLV

(add after first paragraph)
   The SRMS Preference sub-TLV is inserted into the IS-IS Router Capability
   TLV-242 that is defined in [RFC7981].

===============
5.3.  Sub TLVs for Type 242
…
         Description: Segment Routing Local Base (SRLB)   <<<< OLD

         Description: Segment Routing Local Block (SRLB)  <<<< NEW

===============

On Fri, Dec 15, 2017 at 12:09 PM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
>
> 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:isis-wg-bounces@ietf.org] On Behalf Of internet-
> > drafts@ietf.org
> > Sent: Friday, December 15, 2017 9:37 AM
> > To: i-d-announce@ietf.org
> > Cc: isis-wg@ietf.org
> > 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
> > Isis-wg@ietf.org
> > https://www.ietf.org/mailman/listinfo/isis-wg
>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg