Oops, I meant "if the Node MSD is < any of the Link MSDs."  So the question
is:

Should it be considered a misconfiguration if, for a certain MSD type, the
Node MSD is < any of the corresponding Link MSDs?

If so, how should that be handled?

Anoop


On Wed, Jan 10, 2018 at 5:02 PM, Anoop Ghanwani <[email protected]>
wrote:

> Should it be considered a misconfiguration if, for a certain MSD type, the
> Node MSD is > any of the Link MSDs?
>
> Thanks,
> Anoop
>
> On Wed, Jan 10, 2018 at 10:45 AM, Jeff Tantsura <[email protected]>
> wrote:
>
>> Hi,
>>
>> The draft has been significantly updated to address all the comments
>> received and make the draft more generic.
>> The authors would appreciate your comments, as well as a quick note to
>> whether the comments posted have been addressed, and if not, what is still
>> missing.
>>
>> Many thanks!
>>
>> Cheers,
>> Jeff
>>
>> On 1/10/18, 10:29, "[email protected] on behalf of
>> [email protected]" <[email protected] on behalf of
>> [email protected]> wrote:
>>
>>
>>     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           : Signaling MSD (Maximum SID Depth) using
>> IS-IS
>>             Authors         : Jeff Tantsura
>>                               Uma Chunduri
>>                               Sam Aldrin
>>                               Les Ginsberg
>>         Filename        : draft-ietf-isis-segment-routing-msd-09.txt
>>         Pages           : 9
>>         Date            : 2018-01-10
>>
>>     Abstract:
>>        This document defines a way for an IS-IS Router to advertise
>> multiple
>>        types of supported Maximum SID Depths (MSDs) at node and/or link
>>        granularity.  Such advertisements allow entities (e.g., centralized
>>        controllers) to determine whether a particular SID stack is
>>        supportable in a given network.  This document only defines one
>> type
>>        of MSD (maximum label imposition) - but defines an encoding which
>> can
>>        support other MSD types.
>>
>>
>>     The IETF datatracker status page for this draft is:
>>     https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-msd/
>>
>>     There are also htmlized versions available at:
>>     https://tools.ietf.org/html/draft-ietf-isis-segment-routing-msd-09
>>     https://datatracker.ietf.org/doc/html/draft-ietf-isis-segmen
>> t-routing-msd-09
>>
>>     A diff from the previous version is available at:
>>     https://www.ietf.org/rfcdiff?url2=draft-ietf-isis-segment-ro
>> uting-msd-09
>>
>>
>>     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

Reply via email to