Hi Paul, Many thanks! I have uploaded .18 version that should address your comments. Please let me know.
Thanks! Cheers, Jeff On 8/28/18, 07:59, "Paul Kyzivat" <[email protected]> wrote: On 8/27/18 6:18 PM, Jeff Tantsura wrote: > Hi Paul, > > Yes, I completely agree with you, outside of routing context the document is quite difficult to parse, but so are most routing protocol extensions documents, they built on top of "well known" (to routing community) data. Yes. I've also reviewed a couple of others, and it is difficult to get to the point that I can make any sense of the docs, even without trying to understand the subtleties that are being addressed. But that isn't necessarily a problem as long as the docs make sense to the intended audience. > MSD (Type) is a particular capability as supported and configured by a node or a link on a node. > While the most obvious use case is SR indeed (SR stacks MPLS labels that define characteristics of a path thought the network), number of labels a system can impose is finite and that is the number advertised by BMI-MSD (as defined in isis draft) . There are other types, some of them already defined (max readable depth for entropy), some of them are going to be defined on the future. > So there could be another application (not SR) that could use the data(MSDs) distributed thru OSPF/ISIS. > > > Please note - there's. text in isis draft, that is a response to the comment similar to your > > "Note that in a non-SR MPLS network, label depth is what is defined by the MSD advertisements." > > Would this comment work for you? > Many thanks! I've raised the issue. I'll be satisfied with whatever you think is the right fix, if any. Thanks, Paul > Cheers, > Jeff > > On 8/27/18, 12:50, "Paul Kyzivat" <[email protected]> wrote: > > Jeff, > > On 8/27/18 2:18 PM, Jeff Tantsura wrote: > > > 2) MINOR: > > > > Section 1 also says: > > > > Although MSD > > advertisements are associated with Segment Routing, the > > advertisements MAY be present even if Segment Routing itself is not > > enabled. > > > > I found nothing else in the document that elaborated on this. Further > > explanation is needed, in a section other than the introduction. > > [jeff] the meaning of the statement is that MSD MAY be advertised even if Segment Routing is not enabled, ie MSD(s) advertisement could be used by any other application that would find the data provided of value. I would appreciate, if you could be more specific about what's missing. > > Perhaps this is obvious to the likely readers, but not to me... > > (As someone with absolutely no knowledge of OSPF I found the specifics > of the document to be nearly impenetrable. But I'm not part of the > target audience.) > > I thought this information was specific to segment routing (whatever > that is), so what is the point of having this information if segment > routing isn't enabled? How would it be used? For me some discussion of > that would be helpful. > > In any case, AFAIK an "introduction" serves to introduce the material > that is covered in more depth later in the document. In this case it > isn't introducing anything that comes later. If it is to only appear in > one place, then I would expect it to be later in the document. > > Thanks, > Paul > > > > _______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
