Re: [mpls] Concerns about ISD

Tianran Zhou <zhoutianran@huawei.com> Thu, 28 April 2022 06:50 UTC

Return-Path: <zhoutianran@huawei.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D292BC159491 for <mpls@ietfa.amsl.com>; Wed, 27 Apr 2022 23:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5y9YWWeHFHT for <mpls@ietfa.amsl.com>; Wed, 27 Apr 2022 23:50:55 -0700 (PDT)
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 3CE37C15948A for <mpls@ietf.org>; Wed, 27 Apr 2022 23:50:55 -0700 (PDT)
Received: from fraeml712-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KpmPK5l7Yz67sbK for <mpls@ietf.org>; Thu, 28 Apr 2022 14:46:45 +0800 (CST)
Received: from kwepemi500009.china.huawei.com (7.221.188.199) by fraeml712-chm.china.huawei.com (10.206.15.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 28 Apr 2022 08:50:50 +0200
Received: from kwepemi500009.china.huawei.com (7.221.188.199) by kwepemi500009.china.huawei.com (7.221.188.199) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 28 Apr 2022 14:50:49 +0800
Received: from kwepemi500009.china.huawei.com ([7.221.188.199]) by kwepemi500009.china.huawei.com ([7.221.188.199]) with mapi id 15.01.2375.024; Thu, 28 Apr 2022 14:50:49 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>, John E Drake <jdrake@juniper.net>, Tony Li <tony.li@tony.li>
CC: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] Concerns about ISD
Thread-Index: AdhKc4fdvDv9lzMNTfy5c++8iNI9i///poSA//7GfeCAAt4vgP/7wPiAgAhY2QD//2GkAAAn72wA//7TxPD//eE1gP/7NOOg//aGzID/67yBQP/A47NQ/4IVBQD/AoIJwA==
Date: Thu, 28 Apr 2022 06:50:48 +0000
Message-ID: <eb8d7858982d449e94511f81eb9913c8@huawei.com>
References: <6cc272447d2f4c779e85d5c42d3b3c6c@huawei.com> <8623637D-A32E-47A4-B5FC-4D2CF40BEDD1@tony.li> <6199e0e886f9437c95ef9b70719b00ec@huawei.com> <BCFD3F4A-36D6-47C2-B907-FC40B402F97C@tony.li> <3fb1f261ddff48deb0c2ea083cdbd16f@huawei.com> <6B96F21B-9331-4FA8-AD7B-84A4CA8B6FAB@tony.li> <903c57a48280454091495673ec2fe275@huawei.com> <BD5C1BE7-4633-4B51-BAC1-B2AE1C537F36@tony.li> <ad6b8c42b0aa4880b9dee02516f5e46f@huawei.com> <F5BB2CEB-CC8C-4E71-A2E7-B4212878C3B1@tony.li> <aa9c4b913d844410b2af90c8db78c194@huawei.com> <BY3PR05MB8081937B52E657713E8293BFC7ED9@BY3PR05MB8081.namprd05.prod.outlook.com> <a29c96be774845e582a66700d2264f7b@huawei.com> <e986565c98c24cadb858ca4abf6dbbfb@huawei.com> <BY3PR05MB8081A6A725740415356DB2EBC7FA9@BY3PR05MB8081.namprd05.prod.outlook.com>
In-Reply-To: <BY3PR05MB8081A6A725740415356DB2EBC7FA9@BY3PR05MB8081.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.195]
Content-Type: multipart/alternative; boundary="_000_eb8d7858982d449e94511f81eb9913c8huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/_Hztkkmj9-ZHDRhsw8PFUEqcbfg>
Subject: Re: [mpls] Concerns about ISD
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2022 06:50:56 -0000

Hi John,

1. Do you only consider nrp? If so, there is no need for a generic ISD structure, which is very complex. And the nrp id we used in ipv6 is 32 bits. If we want to reuse this for consistent design (easy for interop), how do you want to encode it to ISD?
2. If we really worry about the MSD of SR, why not use BSID as a direct way to reduce the stack?

Tianran

From: John E Drake [mailto:jdrake=40juniper.net@dmarc.ietf.org]
Sent: Wednesday, April 27, 2022 9:06 PM
To: Tianran Zhou <zhoutianran@huawei.com>; John E Drake <jdrake@juniper.net>; Tony Li <tony.li@tony.li>
Cc: mpls@ietf.org
Subject: RE: [mpls] Concerns about ISD

Tianran,

If a network action is related to forwarding, e.g., its ancillary data indicates a network resource partition, I don't think defining its ancillary data to be post-stack makes sense.

Yours Irrespectively,

John



Juniper Business Use Only
From: mpls <mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org>> On Behalf Of Tianran Zhou
Sent: Wednesday, April 27, 2022 5:47 AM
To: John E Drake <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>; Tony Li <tony.li@tony.li<mailto:tony.li@tony.li>>
Cc: mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] Concerns about ISD

[External Email. Be cautious of content]

Hi Tony,

My native language is not English, I am sorry if I offended you in the following message. I did not mean to do so.
In my previous messages, I have presented my concerns on the ISD. And we discussed.
I think we can then work in the other way. We can demonstrate why the ISD is necessary and good.
That means, we figure out the cases which require ISD, the solution to implement ISD, and how this ISD implementation is better than a PSD implementation.
I acknowledge the motivation of using ISD for low stack exploration. But I do not see how one existing ISD proposal, say draft-kompella-mpls-mspl4fa, can work.

Regards,
Tianran

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Tianran Zhou
Sent: Wednesday, April 13, 2022 9:17 AM
To: John E Drake <jdrake=40juniper.net@dmarc.ietf.org<mailto:jdrake=40juniper.net@dmarc.ietf.org>>; Tony Li <tony.li@tony.li<mailto:tony.li@tony.li>>
Cc: mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] Concerns about ISD

Hi,

Comments in line.

Tianran



Juniper Business Use Only
From: mpls <mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org>> On Behalf Of Tianran Zhou
Sent: Tuesday, April 12, 2022 2:36 AM
To: Tony Li <tony.li@tony.li<mailto:tony.li@tony.li>>
Cc: mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] Concerns about ISD

[External Email. Be cautious of content]

Hi Tony,

>>Pushing data to PSD and beyond the RLSD will cause systems to be excluded from the path or take a significant performance hit.

If I know the RLSD of each node, there are many ways to prevent some nodes from pushing data to PSD.

[JD]  Given that you *only* want to use PSD, what is the above sentence proposing?

ZTR> If you followed the past few emails, Tony misled people that PSD will hinder the interoperability. I just show you how PSD will not. According to your description below on the ISD process, it's the same as PSD somehow. I did not see the ISD advantage.

I would like to know how ISD could survive if the ISD exceed the RLSD?

[JD]  The correct term is Network Actions  Sub-stack (NAS).  To answer your question, a transit node will miss the NAS regardless of whether it contains in-stack data.  This is the point that Tony has been making for the past few email iterations

ZTR> Creating new terms does not help the community. I do not care the fancy term you created. Could you please point me out how many times Tony has clarified the ISD process? And where they are? I may have missed.
In my brain, Tony did not address any of my concerns on ISD, but only kept ignoring the fact I presented. It's not a good way for technique discussion.

Best,
Tianran

From: Tony Li [mailto:tony1athome@gmail.com] On Behalf Of Tony Li
Sent: Tuesday, April 12, 2022 2:03 PM
To: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>
Cc: mpls@ietf.org<mailto:mpls@ietf.org>
Subject: Re: [mpls] Concerns about ISD


Hi Tianran,

ZTR2> PSD can work with RLSD, I cannot see how it will hinder the interoperability.


Pushing data to PSD and beyond the RLSD will cause systems to be excluded from the path or take a significant performance hit.

Tony