[Idr] WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt - WG consensus pending

["Susan Hares" <[e-mail]>]

The WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt concludes on
8/8/2019.

 

At this point, we have about 12 people who have participated in this last
call by making comments.   All comments regarding publication appear to be
positive.   If you wish to make additional comments, please make your
comments by 8/8/2019. 

 

The implementations come from a single vendor (cisco).  A 1 week query will
be made (starting on 8/8/2019)  to determine if the WG will accept 2
implementations from the same vendor to meet IDR requirement for 2
implementations.  

 

The authors of this draft (Jeff,  Uma, Ketan, Greg, Nikos) need to do the
following: 

1)      Post an -06.txt  revision that addresses any comments received at
IETF 105 or on the WG list, 

2)      Upgrade the interoperability report at 

 
https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-segment-routing-ms
d%20implementations

 

With details on the following MUST Clause support 

 

Reference are:  section 3  

 

      *  MSD-Value : a number in the range of 0-255.  For all MSD-Types,

         0 represents the lack of ability to impose an MSD stack of any

         depth; any other value represents that of the node.  This value

         MUST represent the lowest value supported by any link

         configured for use by the advertising protocol instance.] 



Reference in section 4: - a similar definition 



      *  MSD-Value : a number in the range of 0-255.  For all MSD-Types,
         0 represents the lack of ability to impose an MSD stack of any
         depth; any other value represents that of the link when used as
         an outgoing interface.] 

 

 

Expected addition to Wiki document is the following information

----------------------------------------------------------------------------
--

Support for zero MSD-value:   

    Node MSD TLV:  yes/no

    Link MSD TLV: yes/no

 

Mechanism for reporting zero-value: 

      

Error handling of MSD TLV  (according to RFC7752):    

  Node MSD TLV:  yes/no 

  Link MSD TLV :    yes /no 

 

 

Mechanism for reporting errors on MSD TLV:  (log error in log file)