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

Gyan Mishra <hayabusagsm@gmail.com> Fri, 05 March 2021 15:14 UTC

Return-Path: <hayabusagsm@gmail.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 6F6573A268A for <lsr@ietfa.amsl.com>; Fri, 5 Mar 2021 07:14:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HZSozLE_JBCY for <lsr@ietfa.amsl.com>; Fri, 5 Mar 2021 07:14:17 -0800 (PST)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C742B3A2689 for <lsr@ietf.org>; Fri, 5 Mar 2021 07:14:07 -0800 (PST)
Received: by mail-pj1-x1035.google.com with SMTP id b15so2047055pjb.0 for <lsr@ietf.org>; Fri, 05 Mar 2021 07:14:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j/ww+H1GEme6/8ESnJKnTgOEEvOUlCjd6EpjXd1RFdA=; b=RXq69MLSNKPkMdycsW2kNenJ9M1UX+3WGYFl0VUfSthCzRYVWOxPJUEILWSlbivzBA v6hH3htR2NuGQHy3Vs74bS6rF/lMuXnuO/oaCFp1o+0v562wSCoik5UEqqRNxtcFb9yW I3uPNdUPWGVsVrQh9JsU0hNCrGijYHrjPuSZh4zbSCuIEsrmzXXC6PCPzxzZ+WEUBhFP HjLs+UqHi308I2s2KzgEz8ILcEl/HMlidk8jRRl67qKbsdMRHFAxcco75aehag+iNg9J 7epKSol2dcKdl8YVCq0ezMM+sGRIncZjnWdqocaUu0+8nkzShvwmKNW+05RguOXcJmfL sCnA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j/ww+H1GEme6/8ESnJKnTgOEEvOUlCjd6EpjXd1RFdA=; b=cTrGUpZAHmnctVyaYhuC6GGhD5rlIqPdWM40OMjX0ulDe+qDI7e8MCiMDoCYMICgFB kWxdIoaKOsK/xSD+pKksS/rvrngKWI16q7q5fm/Pme+uqcxpWboutNfM0KI4r0VFPvq+ /2U6+zmJ1vK4/qnPqbASYpomi2ZiaAxoncHLny0gmkbsrNvJ13SPCUiwqy1SUVpWhxHv 3mDTdbjn5wFORJwN5kVxhnXpyTo/qAVK6OOsCAtOs8DPl4f/30WpyHwIOqn5d3z8PuKL 58kT9dz7QPHiZZtyttpr2oZapQDK2Ji7tOZ5a8zv3G8UKcJQwgucumCutvMWF6oTc3qe VIOQ==
X-Gm-Message-State: AOAM530hmkuPh3a7NiRFNJiMjmlW8iiR26bpU6W3BnvbsI9oj7Q/pGJJ 38IHB/QcXgDXOsJuup+Qgh+UEpSwEQY4AskDmUE=
X-Google-Smtp-Source: ABdhPJw4VOSN9hoHZ82r91uk6c77eti7zS6jTxNXAwvc1su0F7/4pqLgixtLpcHa513ExVMlMkPxwuL5SA8yVaaKt1c=
X-Received: by 2002:a17:902:fe09:b029:e4:951e:2d2e with SMTP id g9-20020a170902fe09b02900e4951e2d2emr9330470plj.22.1614957246014; Fri, 05 Mar 2021 07:14:06 -0800 (PST)
MIME-Version: 1.0
References: <CAOj+MMHsDgfD8avbRtvthhd0=c-X25L9HBc0yQTby4vFQKECLQ@mail.gmail.com> <7D53A65F-7375-43BC-9C4E-2EDCF8E138C8@chinatelecom.cn> <CAOj+MMEAJdqvmhfpVEc+M+v_GJ92hmjggbDWr3=gSAM4y3HkYg@mail.gmail.com> <CABNhwV1EBsej6b-++Ne2OpwMb6DMb9dubjf=M1LrOEHjn4MWmA@mail.gmail.com> <57f50a96-4476-2dc7-ad11-93d5e418f774@cisco.com> <1520992FC97B944A9979C2FC1D7DB0F405242279@dggeml524-mbx.china.huawei.com> <26f29385-eedd-444b-ce02-17facf029bd2@cisco.com> <1520992FC97B944A9979C2FC1D7DB0F4052483BC@dggeml524-mbx.china.huawei.com> <9013a79f-0db9-5ec3-5bfd-8f1ab32644d3@cisco.com> <1520992FC97B944A9979C2FC1D7DB0F40525E441@DGGEML504-MBS.china.huawei.com> <e0bfca37-d9ca-2a06-4fe9-1e6fa3374f45@cisco.com> <1520992FC97B944A9979C2FC1D7DB0F40525E4FF@DGGEML504-MBS.china.huawei.com> <45db4eee-55cf-f09e-1db3-83c30e434213@cisco.com> <1520992FC97B944A9979C2FC1D7DB0F405262C4E@DGGEML504-MBS.china.huawei.com>
In-Reply-To: <1520992FC97B944A9979C2FC1D7DB0F405262C4E@DGGEML504-MBS.china.huawei.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 5 Mar 2021 10:13:46 -0500
Message-ID: <CABNhwV2VF4gONTgT9uN0GS48O6wxc7bkWgwsyo2t+gH_0agYqA@mail.gmail.com>
To: wangyali <wangyali11@huawei.com>
Cc: Aijun Wang <wangaj3@chinatelecom.cn>, Huzhibo <huzhibo@huawei.com>, Peter Psenak <ppsenak@cisco.com>, Robert Raszuk <robert@raszuk.net>, Tianran Zhou <zhoutianran@huawei.com>, Tony Li <tony.li@tony.li>, lsr <lsr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f9ea9c05bccb88f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/1XovysZT69TIRwpvocg0hjOoB3E>
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: Fri, 05 Mar 2021 15:14:22 -0000

Hi Yali

As you have a common LSDB  base MT O and only the flooding mechanism is
broken up into discrete instances with the new MFI TLV, how is the physical
 sub topology mapped to the MFI instances if it’s a common LSDB.  The
flooding is done with separate MFI but that is just the flooding not the
physical topology.  So let’s say you have TEAS NS  network slices you are
provisioning for VPN+ Enhanced VPN and provisioning the underlay
underpinning to VPN+ overlay for a network slice.  How does the underlay
VTN which is a sub topology slice become realized as a slice of the common
LSDB with the MFI instances.

You may have seen this draft now under WG Adoption call using MT for VTN
provisioning.  I agree this would work for VTN provisioning but not sure
how MFI would work as the LSDB is common so the resources are really not
segregated between the network slices.

https://tools.ietf.org/html/draft-xie-lsr-isis-sr-vtn-mt-03


Kind Regards

Gyan

On Fri, Mar 5, 2021 at 9:31 AM wangyali <wangyali11@huawei.com> wrote:

> Hi Pete
> Thanks for your question. Please see inline [yali3].
>
> -----Original Message-----
> From: Peter Psenak [mailto:ppsenak@cisco.com]
> Sent: Thursday, March 4, 2021 11:20 PM
> To: wangyali <wangyali11@huawei.com>om>; Gya Mishra <hayabusagsm@gmail.com>om>;
> Robert Raszuk <robert@raszuk.net>
> Cc: Huzhibo <huzhibo@huawei.com>om>; Aijun Wang <wangaj3@chinatelecom.cn>cn>;
> Tony Li <tony.li@tony.li>li>; lsr <lsr@ietf.org>rg>; Tianran Zhou <
> zhoutianran@huawei.com>
> Subject: Re: [Lsr] New Version Notification for
> draft-wang-lsr-isis-mfi-00.txt
>
> Hi Yali,
>
> On 04/03/2021 14:45, wangyali wrote:
> > Hi Peter,
> >
> > Please see inline [Yali2]. Thanks a lot.
> >
> > -----Original Message-----
> > From: Peter Psenak [mailto:ppsenak@cisco.com]
> > Sent: Thursday, March 4, 2021 6:50 PM
> > To: wangyali <wangyali11@huawei.com>om>; Gyan Mishra
> > <hayabusagsm@gmail.com>om>; Robert Raszuk <robert@raszuk.net>
> > Cc: Huzhibo <huzhibo@huawei.com>om>; Aijun Wang
> > <wangaj3@chinatelecom.cn>cn>; Tony Li <tony.li@tony.li>li>; lsr
> > <lsr@ietf.org>rg>; Tianran Zhou <zhoutianran@huawei.com>
> > Subject: Re: [Lsr] New Version Notification for
> > draft-wang-lsr-isis-mfi-00.txt
> >
> > Hi Yali,
> >
> > On 04/03/2021 11:42, wangyali wrote:
> >> Hi Peter,
> >>
> >> Please review follows tagged by [Yali].
> >>
> >>
> >> -----Original Message-----
> >> From: Peter Psenak [mailto:ppsenak@cisco.com]
> >> Sent: Wednesday, March 3, 2021 5:37 PM
> >> To: wangyali <wangyali11@huawei.com>om>; Gyan Mishra
> >> <hayabusagsm@gmail.com>om>; Robert Raszuk <robert@raszuk.net>
> >> Cc: Huzhibo <huzhibo@huawei.com>om>; Aijun Wang
> >> <wangaj3@chinatelecom.cn>cn>; Tony Li <tony.li@tony.li>li>; lsr
> >> <lsr@ietf.org>rg>; Tianran Zhou <zhoutianran@huawei.com>
> >> Subject: Re: [Lsr] New Version Notification for
> >> draft-wang-lsr-isis-mfi-00.txt
> >>
> >> Yali,
> >>
> >> On 03/03/2021 06:02, wangyali wrote:
> >>> Hi Peter,
> >>>
> >>> Thanks for your comments. Yes. I am improving this sentence. Please
> review the following update.
> >>>
> >>> OLD: " And Level 1/Level 2 PSNP and Level 1/Level 2 CSNP containing
> information about LSPs that transmitted in a specific MFI are generated to
> synchronize the LSDB corresponding to the specific MFI."
> >>>
> >>> NEW: "And Level 1/Level 2 PSNP and Level 1/Level 2 CSNP containing
> information about LSPs that transmitted in a specific MFI are generated to
> synchronize the MFI-specific sub-LSDB. Each MFI-specific sub-LSDB is
> subdivided from a single LSDB."
> >>
> >> please specify sub-LSDB.
> >> [Yali] Thanks for your comment. But to avoid introducing a new term, I
> change to use "MFI-specific LSDB" instead of " MFI-specific sub-LSDB ".
> And we give the explanation that "Each MFI-specific LSDB is subdivided from
> a single LSDB."
> >
> > I wonder what is the difference between "MFI-specific LSDB subdivided
> from a single LSDB" versus the "MFI-specific LSDB".
> > [Yali2]: Actually I am trying to optimize and accurately describe the
> key point that multiple Update processes associated with each MFI operate
> on a common LSDB within the zero IS-IS instance, and each Update process is
> isolated from each other and does not affect each other.
> > So we say "MFI-specific LSDB subdivided from a single LSDB", which may
> explicitly indicate each MFI-specific LSDB shares a common LSDB but each
> Update process associated with a MFI is isolated. However, from your
> previous question and suggestions,  "MFI-specific LSDB" looks like unclear
> and misleading. Any good idea on improving the expression are welcome.
>
>
> it's not the name that is as important. It's the concept that looks
> questionable - how well can you isolate the update processing if the data
> are part of the same LSDB and whether such update process separation would
> prove to be useful at all. I don't know, so far I have not seen any
> evidence.
> [yali3] This draft defines a new TLV, i.e. MFI-ID TLV,  which may be
> included in each Level 1/Level 2 IS-IS LSPs and SNPs. Hence, each Level
> 1/Level 2 LSPs and SNPs associated with each Update Process can be uniquely
> identified by MFI-ID.
> In this draft, each flooding instance has its own separated Update
> process, which isolates the impact of application information flooding on
> the IS-IS protocol operation. So each Level 1/Level 2 LSP associated with a
> specific MFI carries flooding information belonging to the specific MFI.
> And Level 1/Level 2 PSNP and Level 1/Level 2 CSNP containing information
> about LSPs that propagated in the specific MFI are generated to synchronize
> the MFI-specific LSDB.
>
> thanks,
> Peter
>
>
>
>
> >
> > thanks,
> > Peter
> >
> >>
> >> thanks,
> >> Peter
> >>
> >>
> >>>
> >>> Best,
> >>> Yali
> >>>
> >>> -----Original Message-----
> >>> From: Peter Psenak [mailto:ppsenak@cisco.com]
> >>> Sent: Tuesday, March 2, 2021 5:12 PM
> >>> To: wangyali <wangyali11@huawei.com>om>; Gyan Mishra
> >>> <hayabusagsm@gmail.com>om>; Robert Raszuk <robert@raszuk.net>
> >>> Cc: Huzhibo <huzhibo@huawei.com>om>; Aijun Wang
> >>> <wangaj3@chinatelecom.cn>cn>; Tony Li <tony.li@tony.li>li>; lsr
> >>> <lsr@ietf.org>rg>; Tianran Zhou <zhoutianran@huawei.com>
> >>> Subject: Re: [Lsr] New Version Notification for
> >>> draft-wang-lsr-isis-mfi-00.txt
> >>>
> >>> Yali,
> >>>
> >>> On 01/03/2021 10:49, wangyali wrote:
> >>>> Hi Peter,
> >>>>
> >>>> Many thanks for your feedback. First of all, I'm sorry for the
> confusion I had caused you from my previous misunderstanding.
> >>>>
> >>>> And I want to clarify that a single and common LSDB is shared by all
> MFIs.
> >>>
> >>> well, the draft says:
> >>>
> >>> "information about LSPs that transmitted in a
> >>>      specific MFI are generated to synchronize the LSDB corresponding
> to
> >>>      the specific MFI."
> >>>
> >>> If the above has changed, then please update the draft accordingly.
> >>>
> >>> thanks,
> >>> Peter
> >>>
> >>>
> >>>
> >>>>
> >>>> Best,
> >>>> Yali
> >>>>
> >>>> -----Original Message-----
> >>>> From: Peter Psenak [mailto:ppsenak@cisco.com]
> >>>> Sent: Sunday, February 28, 2021 8:23 PM
> >>>> To: Gyan Mishra <hayabusagsm@gmail.com>om>; Robert Raszuk
> >>>> <robert@raszuk.net>
> >>>> Cc: Huzhibo <huzhibo@huawei.com>om>; Aijun Wang
> >>>> <wangaj3@chinatelecom.cn>cn>; Tony Li <tony.li@tony.li>li>; lsr
> >>>> <lsr@ietf.org>rg>; Tianran Zhou <zhoutianran@huawei.com>om>; wangyali
> >>>> <wangyali11@huawei.com>
> >>>> Subject: Re: [Lsr] New Version Notification for
> >>>> draft-wang-lsr-isis-mfi-00.txt
> >>>>
> >>>> Gyan,
> >>>>
> >>>> On 26/02/2021 17:19, Gyan Mishra wrote:
> >>>>>
> >>>>> MFI seems more like flex algo with multiple sub topologies sharing
> >>>>> a common links in a  topology where RFC 8202 MI is separated at
> >>>>> the process level separate LSDB.  So completely different and of
> >>>>> course different goals and use cases for MI versus MFI.
> >>>>
> >>>> I would not use the fle-algo analogy - all flex-algos operate on top
> of a single LSDB, contrary to what is being proposed in MFI draft.
> >>>>
> >>>>>
> >>>>>       MFI also seems to be a flood reduction mechanism by creating
> >>>>> multiple sub topology instances within a common LSDB.  There are a
> >>>>> number of flood reduction drafts and this seems to be another
> >>>>> method of achieving the same.
> >>>>
> >>>> MFI draft proposes to keep the separate LSDB per MFI, so the above
> analogy is not correct either.
> >>>>
> >>>> thanks,
> >>>> Peter
> >>>>
> >>>>
> >>>>>
> >>>>> Gyan
> >>>>>
> >>>>> On Fri, Feb 26, 2021 at 7:10 AM Robert Raszuk <robert@raszuk.net
> >>>>> <mailto:robert@raszuk.net>> wrote:
> >>>>>
> >>>>>         Aijun,
> >>>>>
> >>>>>         How multi instance is implemented is at the discretion of a
> vendor.
> >>>>>         It can be one process N threads or N processes. It can be
> both and
> >>>>>         operator may choose.
> >>>>>
> >>>>>         MFI is just one process - by the spec - so it is inferior.
> >>>>>
> >>>>>         Cheers,
> >>>>>         R.
> >>>>>
> >>>>>
> >>>>>         On Fri, Feb 26, 2021 at 12:44 PM Aijun Wang <
> wangaj3@chinatelecom.cn
> >>>>>         <mailto:wangaj3@chinatelecom.cn>> wrote:
> >>>>>
> >>>>>             Hi, Robert:
> >>>>>
> >>>>>             Separate into different protocol instances can
> accomplish the
> >>>>>             similar task, but it has some deployment overhead.
> >>>>>             MFIs within one instance can avoid such cumbersome work,
> and
> >>>>>             doesn’t affect the basic routing calculation process.
> >>>>>
> >>>>>             Aijun Wang
> >>>>>             China Telecom
> >>>>>
> >>>>>>             On Feb 26, 2021, at 19:00, Robert Raszuk <
> robert@raszuk.net
> >>>>>>             <mailto:robert@raszuk.net>> wrote:
> >>>>>>
> >>>>>>             Hi Yali,
> >>>>>>
> >>>>>>                 If this was precise, then the existing
> multi-instance
> >>>>>>                 mechanism would be sufficient.
> >>>>>>                 [Yali]: MFI is a different solution we recommend to
> solve
> >>>>>>                 this same and valuable issue.
> >>>>>>
> >>>>>>
> >>>>>>             Well the way I understand this proposal MFI is much
> weaker
> >>>>>>             solution in terms of required separation.
> >>>>>>
> >>>>>>             In contrast RFC8202 allows to separate ISIS
> instances at the
> >>>>>>             process level, but here MFIs as defined must be handled
> by the
> >>>>>>             same ISIS process
> >>>>>>
> >>>>>>                 This document defines an extension to
> >>>>>>                 IS-IS to allow*one standard instance*  of
> >>>>>>                 the protocol to support multiple update
> >>>>>>                 process operations.
> >>>>>>
> >>>>>>             Thx,
> >>>>>>             R.
> >>>>>>
> >>>>>>             _______________________________________________
> >>>>>>             Lsr mailing list
> >>>>>>             Lsr@ietf.org <mailto:Lsr@ietf.org>
> >>>>>>             https://www.ietf.org/mailman/listinfo/lsr
> >>>>>
> >>>>>         _______________________________________________
> >>>>>         Lsr mailing list
> >>>>>         Lsr@ietf.org <mailto:Lsr@ietf.org>
> >>>>>         https://www.ietf.org/mailman/listinfo/lsr
> >>>>>
> >>>>> --
> >>>>>
> >>>>> <http://www.verizon.com/>
> >>>>>
> >>>>> *Gyan Mishra*
> >>>>>
> >>>>> /Network Solutions A//rchitect /
> >>>>>
> >>>>> /M 301 502-1347
> >>>>> 13101 Columbia Pike
> >>>>> /Silver Spring, MD
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >
> >
> >
>
> --

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD