Hi Tony, Thanks for your comments.
My current understanding is TLV 25 could reference the associated L3 link advertised in either TLV 22 or 222. With your proposal of keeping things orthogonal, does it mean that TLV 25 would only be used to advertise the member link attributes of the associated L3 link in TLV 22, and a new TLV 225 needs to be defined for advertising member link attributes of the associated L3 link in corresponding TLV 222? Then if an L3 link is advertised with multiple TLV 222 for different topologies, does its member link attributes also need be advertised multiple times in multiple TLV 225? Best regards, Jie From: Tony Przygienda [mailto:[email protected]] Sent: Monday, March 30, 2020 12:29 AM To: Les Ginsberg (ginsberg) <[email protected]> Cc: Aijun Wang <[email protected]>; Peter Psenak <[email protected]>; [email protected]; Dongjie (Jimmy) <[email protected]>; [email protected]; Les Ginsberg (ginsberg) <[email protected]>; [email protected] Subject: Re: [Lsr] Using IS-IS Multi-Topology (MT) for Segment Routing basedVirtual Transport Network As usual +1 Les Simply think what is the _L3 construct_ ISIS runs over which is easily identified as the same thing that adjacency runs over. If adjacency runs over each constituent of L2 bundel we don't have L2, we have L3 with confused naming. If adjacency runs over the L2 bundle the bundle is an L3 construct and hence MTID applies again, to keep things orthogonal (mostly on the encoding side but also underlying architecture) I would derive 225 the same way we run 222. Otherwise we end up in funky places like "what happens if this bundle has more than one MTID and if it runs on no MT and a MTID" as well and what does it mean if it's missing and what if someone doesn't understand it and so on and so on. That stuff has been pretty well reviewed and thought out when it was done and all the tlv/subtlv discussions had then ... --- tony On Sun, Mar 29, 2020 at 8:57 AM Les Ginsberg (ginsberg) <[email protected]<mailto:[email protected]>> wrote: Peter/Aijun - We are in agreement. I never said that an L2 Bundle member could/should be associated with a specific MTID. It is the L3 adjacency that has the MTID association. If we were going to support MTID in TLV 25 the correct place to put it would be as part of the " Parent L3 Neighbor Descriptor". Les > -----Original Message----- > From: Lsr <[email protected]<mailto:[email protected]>> On Behalf Of > Aijun Wang > Sent: Sunday, March 29, 2020 3:46 AM > To: Peter Psenak > <[email protected]<mailto:[email protected]>> > Cc: [email protected]<mailto:[email protected]>; Dongjie (Jimmy) > <[email protected]<mailto:[email protected]>>; > [email protected]<mailto:[email protected]>; Les Ginsberg (ginsberg) > <[email protected]<mailto:[email protected]>>; > [email protected]<mailto:[email protected]>; Tony Przygienda > <[email protected]<mailto:[email protected]>> > Subject: Re: [Lsr] Using IS-IS Multi-Topology (MT) for Segment Routing > basedVirtual Transport Network > > I have the same consideration as Peter. > > Aijun Wang > China Telecom > > > On Mar 29, 2020, at 17:10, Peter Psenak > <[email protected]<mailto:[email protected]>> wrote: > > > > Hi Les, > > > >> On 29/03/2020 00:00, Les Ginsberg (ginsberg) wrote: > >> Tony – > >> There are a few misunderstandings in your post. > >> Let me try to correct them. > >> RFC 8668 defines a new top-level TLV (25). This is NOT a sub-TLV(sic) of > TLVs 22,23,141,222,223. > >> Conceptually, it could have been defined as a sub-TLV, but because of the > limited length of a TLV in IS-IS (255 octets) and the likelihood that > advertising > L2Bundle member attributes would consume a significant amount of space, > we decided to use a new top-level TLV which references the associated L3 > adjacency advertised in TLV 22. This means TLV22 advertisements are not > impacted by the presence of TLV 25. In particular, the use of TLV 25 does not > lead to multiple TLV 22 advertisements for the same adjacency, which we > thought was a desirable outcome. > >> The equivalent OSPF draft (https://tools.ietf.org/html/draft-ketant-lsr- > ospf-l2bundles-01 ) takes the sub-TLV approach, but since OSPF has a 16 bit > length for TLVs it does not face the same encoding issues. > >> I fully agree with you that an L2 bundle is a Layer 3 construct – and as > >> such > can be associated with any Layer 3 MTID in theory. However, when writing > RFC 8668 we did not consider that there was a use case for topology specific > link attributes. The current encoding does not support MTID. > > > > RFC 8668 defines a TLV to advertise attributes of the individual L2 link > members. While the TLV itself can be considered as L3 construct (and have > MT associated with it), the individual L2 Bundle Member Links inside this TLV > are not L3 constructs IMHO and should never have a MTID associated with > them. The ask here is to advertise different MTID for each individual L2 > bundle member link. > > > > MTID is used to construct a topology. I do not see how a L2 bundle link > member would ever become part of the L3 topology. > > > > my 2c, > > Peter > > > > > >> At this point, if we needed to extend RFC 8668 to support MTID we would > need to allocate an additional TLV code point that included MTID – similar to > the distinction between TLV 22 and TLV 222. > >> HTH > >> Les > >> *From:* Lsr <[email protected]<mailto:[email protected]>> *On Behalf > >> Of * Tony Przygienda > >> *Sent:* Saturday, March 28, 2020 10:25 AM > >> *To:* peng.shaofu@<mailto:peng.shaofu@> > > _______________________________________________ > Lsr mailing list > [email protected]<mailto:[email protected]> > https://www.ietf.org/mailman/listinfo/lsr
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
