IMO there is no need for this draft to exist. Before a need for such a draft can be established two things have to happen in the following order:
1)There has to be WG consensus that application info such as VTN should be advertised by the IGPs. To date no such consensus exists and there has been significant resistance to doing so. 2)If such consensus is reached there is already a defined/implemented solution - RFC 8202. Therefore, the need for a different set of protocol extensions would first require WG consensus that there are significant shortcomings to the RFC 8202 solution. No such consensus exists nor has any discussion on this point taken place. If the authors of this new draft want to start by discussing point #1 on the list - fair enough. But the starting point for that discussion should NOT be this draft. Therefore, I will make no comment on the content of the draft. Authors - if your response is to try to explain to me why this draft is needed, then you have not understood what I am saying. Les > -----Original Message----- > From: Lsr <lsr-boun...@ietf.org> On Behalf Of wangyali > Sent: Monday, February 22, 2021 11:11 PM > To: lsr@ietf.org > Cc: Huzhibo <huzh...@huawei.com>; Aijun Wang > <wang...@chinatelecom.cn>; Tianran Zhou <zhoutian...@huawei.com> > Subject: Re: [Lsr] New Version Notification for draft-wang-lsr-isis-mfi-00.txt > > Hi all, > > In order to separate multiple flooding instances for dissemination of routing > information and other types of application-specific information to minimizes > the impact of non-routing information flooding on the routing convergence > and stability, We submitted a new IS-IS flooding mechanism implemented in > the zero IS-IS instance, named as IS-IS Multi-flooding Instances (MFIs). > > An encoding format for IS-IS MFI-ID TLV and MFIs Update Process defined in > this draft could be found in https://datatracker.ietf.org/doc/draft-wang-lsr- > isis-mfi/ . > > Any questions and comments are welcome. > > Thanks, > Yali > > -----Original Message----- > From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] > Sent: Monday, February 22, 2021 9:59 AM > To: Aijun Wang <wang...@chinatelecom.cn>; Tianran Zhou > <zhoutian...@huawei.com>; wangyali <wangyal...@huawei.com>; Huzhibo > <huzh...@huawei.com> > Subject: New Version Notification for draft-wang-lsr-isis-mfi-00.txt > > > A new version of I-D, draft-wang-lsr-isis-mfi-00.txt has been successfully > submitted by Yali Wang and posted to the IETF repository. > > Name: draft-wang-lsr-isis-mfi > Revision: 00 > Title: IS-IS Multi-Flooding Instances > Document date: 2021-02-20 > Group: Individual Submission > Pages: 7 > URL: https://www.ietf.org/archive/id/draft-wang-lsr-isis-mfi-00.txt > Status: https://datatracker.ietf.org/doc/draft-wang-lsr-isis-mfi/ > Htmlized: https://datatracker.ietf.org/doc/html/draft-wang-lsr-isis-mfi > Htmlized: https://tools.ietf.org/html/draft-wang-lsr-isis-mfi-00 > > > Abstract: > This document proposes a new IS-IS flooding mechanism which separates > multiple flooding instances for dissemination of routing information > and other types of application-specific information to minimizes the > impact of non-routing information flooding on the routing convergence > and stability. Due to different flooding information has different > requirements on the flooding rate, these multi-flooding instances > should be given various priorities and flooding parameters. An > encoding format for IS-IS Multi-Flooding Instance Identifier (MFI-ID) > TLV and Update Process are specified in this document. > > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > > _______________________________________________ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr _______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
