Hi Les, Many thanks for your reply. Please find inline >>Yali.
Best regards, Yali -----Original Message----- From: Les Ginsberg (ginsberg) [mailto:[email protected]] Sent: Wednesday, February 24, 2021 11:54 AM To: wangyali <[email protected]>; [email protected] Cc: Huzhibo <[email protected]>; Aijun Wang <[email protected]>; Tianran Zhou <[email protected]> Subject: RE: New Version Notification for draft-wang-lsr-isis-mfi-00.txt 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. >>Yali: The advertisement of application information using IS-IS has been >>defined in RFC6823. The MFI mechanism as specified in our draft can be >>applicable to the advertisement of both routing information and application >>information. Each MFI is associated with a Update process and a MFI-specific >>LSDB, which support isolation of application information flooding from the >>routing information flooding. 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. >>Yali: The purpose of RFC 8202 is to allow multiple IS-IS protocol instances >>operate on the same circuit, and each instance will form its own adjacency. >>While the MFI mechanism is to provide multiple separate update process within >>a single protocol instance, each Update process can be associated with a >>flooding topology and a LSDB, and the flooding parameters of each Update >>process can be different and customized based on different information needed >>to be advertised in the associated Flooding Instance. These are significant differences to RFC8202 and RFC6823. 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 <[email protected]> On Behalf Of wangyali > Sent: Monday, February 22, 2021 11:11 PM > To: [email protected] > Cc: Huzhibo <[email protected]>; Aijun Wang > <[email protected]>; Tianran Zhou <[email protected]> > 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: [email protected] [mailto:[email protected]] > Sent: Monday, February 22, 2021 9:59 AM > To: Aijun Wang <[email protected]>; Tianran Zhou > <[email protected]>; wangyali <[email protected]>; Huzhibo > <[email protected]> > 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 > [email protected] > https://www.ietf.org/mailman/listinfo/lsr _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
