Hi Yali, 

Speaking as WG member:

So this rather simplistic draft can be summarized as separate out the 
non-routing info into different LSPs, tag the corresponding LSPs, and then 
implementations can "do the right thing". As we already have RFC 8202 which 
offers clean separation, I don't know why we'd consider this under specified 
proposal. 

Using a separate instance offers other advantages such only requiring those 
IS-IS routers that need the non-routing information to be in the topology and 
providing a separate LSPs space for the new instances.

Speaking as WG Co-chair:

Given the feedback you've received thus far, do you still want to present this 
draft at IETF 110?

Thanks,
Acee



On 2/23/21, 2:11 AM, "Lsr on behalf of wangyali" <lsr-boun...@ietf.org on 
behalf of wangyal...@huawei.com> wrote:

    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

Reply via email to