It is the job of the WG chairs to determine consensus. T
> On Aug 4, 2024, at 11:53 PM, Aijun Wang <wangai...@tsinghua.org.cn> wrote: > > Hi, Tony: > > You agree also the IETF operates on "rough consensus". Then Let's examine > carefully the last call responses of this > draft(https://mailarchive.ietf.org/arch/browse/lsr/?gbt=1&index=pxypKxuH2PtQ2Jd9DE8Q_tBg0Co): > > There are totally 16 replies to this WGLC: > 9 from the authors(include none-IPR declarations), > 1 from Yingzhen to call the IPR responses > 2 from Ketan(with similar "key definition" suggestions), 1 from > Peter(friendship support), 1 from Acee(friendship support), 2 from Mine(with > objecting its forwarding) > > Does the above statists represent "Rough Consensus"? I don't think so, I > think you can't easily call it "Rough Consensus", right? > > Even the author himself admitted it was difficult to elaborate the "key > fields" of each code > point(https://mailarchive.ietf.org/arch/msg/lsr/pxypKxuH2PtQ2Jd9DE8Q_tBg0Co/,), > then what's the value of this document? > > As my suggestions, it will be more easy to declare "Every code point may > emerge multiple times within one LSA, and it depends the vendor to implement > it". > > To answer your question "Where to start", my replies is that we need other > creative solution to solve such issue in one extensible manner. > > Best Regards > > Aijun Wang > China Telecom > > > -----邮件原件----- > 发件人: forwardingalgori...@ietf.org [mailto:forwardingalgori...@ietf.org] 代表 > Tony Li > 发送时间: 2024年8月5日 12:40 > 收件人: Aijun Wang <wangai...@tsinghua.org.cn> > 抄送: lsr@ietf.org > 主题: [Lsr] Re: 答复: 【What's the reason to move forward this document to be > published?】答复: I-D Action: draft-ietf-lsr-multi-tlv-03.txt > > > Hi Aijun, > > Where to start? > > There is no hurry for this document. It started in Jan. 2022. It has evolved, > been discussed, and evolved some more, to the point where almost everyone is > happy with it and it’s time to publish it. > > We recognize that you don’t like it. That’s fine. The IETF operates on > rough consensus and we are very happy to progress without your assent. > > We’ve discussed these points with you before and made no progress. I see no > point in repeating myself. > > Regards, > Tony > > >> On Aug 4, 2024, at 7:01 PM, Aijun Wang <wangai...@tsinghua.org.cn> wrote: >> >> give to clue to the vendors to implement it /s give no clue to the vendors >> to implement it. >> >> -----邮件原件----- >> 发件人: forwardingalgori...@ietf.org [mailto:forwardingalgori...@ietf.org] 代表 >> Aijun Wang >> 发送时间: 2024年8月5日 9:56 >> 收件人: lsr@ietf.org >> 主题: [Lsr] 【What's the reason to move forward this document to be >> published?】答复: I-D Action: draft-ietf-lsr-multi-tlv-03.txt >> >> Hi, WG chairs and authors of this draft: >> >> I have reviewed again the evolution of this draft, and am struggled to >> understand what's the reason for this WG to move forward this document to be >> adopted, to be WG LCed and even to be published, in such hurry manner? >> >> As pointed out during its adoption call, its WGLC process, if it doesn't >> address(or can't be, as Les expressed in >> https://mailarchive.ietf.org/arch/msg/lsr/pxypKxuH2PtQ2Jd9DE8Q_tBg0Co/) the >> definition of key part of each code point, how to assure the >> interoperability? >> >> What's the differences that we just state simply that every TLV, sub-TLV >> within IS-IS is multi-part applicable instead of the authors list onerously >> almost for every TLV, sub-TLV for its applicability? >> >> And, as stated in abstract of this document, it "codifies the common >> mechanism", where is it, please point me out clearly which part in this >> document describe the "common mechanism"? >> >> Yes, The Chairs has the right to put forward it, even to publish it as RFC. >> BUT, as the person from the operator, I can assert that this document bring >> no benefit to the operators who want to deploy it, give to clue to the >> vendors to implement it. >> >> >> Look forward the WG, or IESG abandon it. >> >> Best Regards >> >> Aijun Wang >> China Telecom >> >> >> ----邮件原件----- >> 发件人: forwardingalgori...@ietf.org [mailto:forwardingalgori...@ietf.org] 代表 >> internet-dra...@ietf.org >> 发送时间: 2024年8月3日 9:08 >> 收件人: i-d-annou...@ietf.org >> 抄送: lsr@ietf.org >> 主题: [Lsr] I-D Action: draft-ietf-lsr-multi-tlv-03.txt >> >> Internet-Draft draft-ietf-lsr-multi-tlv-03.txt is now available. It is a >> work item of the Link State Routing (LSR) WG of the IETF. >> >> Title: Multi-part TLVs in IS-IS >> Authors: Parag Kaneriya >> Tony Li >> Antoni Przygienda >> Shraddha Hegde >> Les Ginsberg >> Name: draft-ietf-lsr-multi-tlv-03.txt >> Pages: 26 >> Dates: 2024-08-02 >> >> Abstract: >> >> New technologies are adding new information into IS-IS while >> deployment scales are simultaneously increasing, causing the contents >> of many critical TLVs to exceed the currently supported limit of 255 >> octets. Extensions exist that require significant IS-IS changes that >> could help address the problem, but a less drastic solution would be >> beneficial. This document codifies the common mechanism of extending >> the TLV content space through multiple TLVs. >> >> The IETF datatracker status page for this Internet-Draft is: >> https://datatracker.ietf.org/doc/draft-ietf-lsr-multi-tlv/ >> >> There is also an HTMLized version available at: >> https://datatracker.ietf.org/doc/html/draft-ietf-lsr-multi-tlv-03 >> >> A diff from the previous version is available at: >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-multi-tlv-03 >> >> Internet-Drafts are also available by rsync at: >> rsync.ietf.org::internet-drafts >> >> >> _______________________________________________ >> Lsr mailing list -- lsr@ietf.org >> To unsubscribe send an email to lsr-le...@ietf.org >> >> _______________________________________________ >> Lsr mailing list -- lsr@ietf.org >> To unsubscribe send an email to lsr-le...@ietf.org >> >> _______________________________________________ >> Lsr mailing list -- lsr@ietf.org >> To unsubscribe send an email to lsr-le...@ietf.org > > _______________________________________________ > Lsr mailing list -- lsr@ietf.org > To unsubscribe send an email to lsr-le...@ietf.org > _______________________________________________ Lsr mailing list -- lsr@ietf.org To unsubscribe send an email to lsr-le...@ietf.org
