support adoption. This draft is de-facto implemented and deployed already where it became unavoidable. And it gets us further down the road without forcing flag day on the networks lest older deployed versions break to best degree achievable (which is a very important consideration these days, especially on largest networks in existence). The reason I helped push this draft into the light of day is that situation was becoming bits wild and forcing TLVs to explain what multi-part semantics mean semantically is a necessary hygiene we have to start to apply to the protocol (and yes, every draft should have a normative section now for the multi-part just we had to introduce the "duplicate-handling" in lots RFC based on bitter experience [no great surprise if you think through protocol design clearly but IETF was and is a bit of a juvenile learning by running a car into the ditch and standing dazzled by the wreck after not having heeded the warnings about ice on the road. Excuse my simile, probably too much caffeine this morning ;-) ]). And as such all this is ultimately the failing of the original ISO spec even (so my gripe about IETF is bit misguided in this very case ;-), no matter whether we keep pushing the creaking existing isis envelope or we design a brand-new ISIS-for-IP-v2 we end up in the same problem due to limited PDU size in flooding. Hence for any encoding using flooding to be =semantically disambiguated the problem of repetition in different contexts (within same parent TLV or new parent TLV etc in recursion) must be handled.
How we discover/advertise which MP-TLV is supported on an implementation is still under debate as it should and draft is malleable but I think the direction is the de-facto best way to deal with the situation as we have it and dragging things into the future. On Wed, Nov 22, 2023 at 1:00 PM Shraddha Hegde <shrad...@juniper.net> wrote: > Support the adoption as co-author of this draft. > > > > Juniper Business Use Only > > *From:* Les Ginsberg (ginsberg) <ginsb...@cisco.com> > *Sent:* Saturday, November 18, 2023 12:01 AM > *To:* Tony Przygienda <tonysi...@gmail.com>; Tony Li <tony...@tony.li> > *Cc:* Yingzhen Qu <yingzhen.i...@gmail.com>; > draft-pkaneria-lsr-multi-...@ietf.org; lsr <lsr@ietf.org> > *Subject:* RE: [Lsr] WG Adoption Call - draft-pkaneria-lsr-multi-tlv > (11/17/2023 - 12/09/2023) > > > > *[External Email. Be cautious of content]* > > > > +2 support adoption as coauthor > > > > (Chairs – is it really necessary for the authors to express support for > their own draft? 😊) > > > > Les > > > > *From:* Tony Przygienda <tonysi...@gmail.com> > *Sent:* Friday, November 17, 2023 10:29 AM > *To:* Tony Li <tony...@tony.li> > *Cc:* Yingzhen Qu <yingzhen.i...@gmail.com>; > draft-pkaneria-lsr-multi-...@ietf.org; lsr <lsr@ietf.org> > *Subject:* Re: [Lsr] WG Adoption Call - draft-pkaneria-lsr-multi-tlv > (11/17/2023 - 12/09/2023) > > > > +1, support adoptoinb as co-author > > > > On Fri, Nov 17, 2023 at 6:58 PM Tony Li <tony...@tony.li> wrote: > > > > I support adoption as co-author. > > > > T > > > > > > On Nov 17, 2023, at 9:23 AM, Yingzhen Qu <yingzhen.i...@gmail.com> wrote: > > > > Hi, > > > > This begins a WG adoption call for draft-pkaneria-lsr-multi-tlv: > draft-pkaneria-lsr-multi-tlv-04 > - Multi-part TLVs in IS-IS (ietf.org) > <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-pkaneria-lsr-multi-tlv/__;!!NEt6yMaO-gk!GnuXZMa1l9V6gtK9gJ8eWmBcBcGdB2ZexW9CRp0WfFb_xnY2hFmutQD8PRfiypCOldw44Ef06oQ_JPaz$> > > > > Please send your support or objection to the list before December 9th, > 2023. An extra week is allowed for the US Thanksgiving holiday. > > > > Thanks, > > Yingzhen > > > > _______________________________________________ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/lsr__;!!NEt6yMaO-gk!GnuXZMa1l9V6gtK9gJ8eWmBcBcGdB2ZexW9CRp0WfFb_xnY2hFmutQD8PRfiypCOldw44Ef06tw2lzt3$> > >
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
