Re: [Lsr] New Version Notification for draft-wang-lsr-isis-mfi-00.txt

wangyali <wangyali11@huawei.com> Mon, 01 March 2021 09:30 UTC

Return-Path: <wangyali11@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D912A3A18BD for <lsr@ietfa.amsl.com>; Mon, 1 Mar 2021 01:30:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L1qWmNC0PjSP for <lsr@ietfa.amsl.com>; Mon, 1 Mar 2021 01:30:34 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A4A53A18BE for <lsr@ietf.org>; Mon, 1 Mar 2021 01:30:34 -0800 (PST)
Received: from fraeml741-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Dpvx10PC9z67tLX for <lsr@ietf.org>; Mon, 1 Mar 2021 17:24:53 +0800 (CST)
Received: from fraeml741-chm.china.huawei.com (10.206.15.222) by fraeml741-chm.china.huawei.com (10.206.15.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 1 Mar 2021 10:30:30 +0100
Received: from DGGEML421-HUB.china.huawei.com (10.1.199.38) by fraeml741-chm.china.huawei.com (10.206.15.222) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Mon, 1 Mar 2021 10:30:30 +0100
Received: from DGGEML524-MBX.china.huawei.com ([169.254.1.65]) by dggeml421-hub.china.huawei.com ([10.1.199.38]) with mapi id 14.03.0509.000; Mon, 1 Mar 2021 17:30:16 +0800
From: wangyali <wangyali11@huawei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
CC: Huzhibo <huzhibo@huawei.com>, Aijun Wang <wangaj3@chinatelecom.cn>, Tianran Zhou <zhoutianran@huawei.com>
Thread-Topic: [Lsr] New Version Notification for draft-wang-lsr-isis-mfi-00.txt
Thread-Index: AQHXDD/jvOSvDlAmT0KIo+Iqe5eLAapu28FQ
Date: Mon, 1 Mar 2021 09:30:18 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F40524222C@dggeml524-mbx.china.huawei.com>
References: <592EA103-CAB1-49FE-8DFF-4D2E6D923D4E@cisco.com>
In-Reply-To: <592EA103-CAB1-49FE-8DFF-4D2E6D923D4E@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.136]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/9ZrqGh_F-tacjLl5XlvvBwp8tw4>
Subject: Re: [Lsr] New Version Notification for draft-wang-lsr-isis-mfi-00.txt
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2021 09:30:38 -0000

Hi Acee,

Many thanks for your feedback and questions.  Please see inline >Yali.

-----Original Message-----
From: Acee Lindem (acee) [mailto:acee@cisco.com] 
Sent: Friday, February 26, 2021 9:04 PM
To: wangyali <wangyali11@huawei.com>om>; lsr@ietf.org
Cc: Huzhibo <huzhibo@huawei.com>om>; Aijun Wang <wangaj3@chinatelecom.cn>cn>; Tianran Zhou <zhoutianran@huawei.com>
Subject: Re: [Lsr] New Version Notification for draft-wang-lsr-isis-mfi-00.txt

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. 
>Yali: This draft intend to propose a different solution, aka MFI, to isolate the non-routing information flooding from routing information flooding in a standard IS-IS standard. So there are no non-zero instances of IS-IS protocol needed to be used. 
Different from RFC8202, MFIs share a common adjacencies and a single LSDB. Each Update process associated with a MFI-specific sub topology operates on a logically subdivided LSDB. For each MFI, it is given a MFI-specific prioritization for processing PDUs and MFI-specific flooding parameters so as to allow different MFIs to consume network-wide resources at different rates. 

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.
>Yali: Each non-zero MFI can also support a sparse sub topology in which there are those IS-IS routers that are interested in the non-routing information. Besides, this draft also specifies that each MFI can has its own sets of LSPs.

Speaking as WG Co-chair:

Given the feedback you've received thus far, do you still want to present this draft at IETF 110?
>Yali: Many thanks for all guys’ comments and questions. Given these feedbacks, I think there are still a lot of points needed to be discussed at IETF 110. If possible, I wish there's time to present.

Thanks,
Acee



On 2/23/21, 2:11 AM, "Lsr on behalf of wangyali" <lsr-bounces@ietf.org on behalf of wangyali11@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-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
    Sent: Monday, February 22, 2021 9:59 AM
    To: Aijun Wang <wangaj3@chinatelecom.cn>cn>; Tianran Zhou <zhoutianran@huawei.com>om>; wangyali <wangyali11@huawei.com>om>; Huzhibo <huzhibo@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