give to clue to the vendors to implement it /s give no clue to the vendors to implement it.
-----邮件原件----- 发件人: [email protected] [mailto:[email protected]] 代表 Aijun Wang 发送时间: 2024年8月5日 9:56 收件人: [email protected] 主题: [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 ----邮件原件----- 发件人: [email protected] [mailto:[email protected]] 代表 [email protected] 发送时间: 2024年8月3日 9:08 收件人: [email protected] 抄送: [email protected] 主题: [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 -- [email protected] To unsubscribe send an email to [email protected] _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected] _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
