[mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)

Tianran Zhou <zhoutianran@huawei.com> Mon, 30 September 2024 00:38 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 B696AC14F5FC for <mpls@ietfa.amsl.com>; Sun, 29 Sep 2024 17:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 IqaB2l6HTVEy for <mpls@ietfa.amsl.com>; Sun, 29 Sep 2024 17:38:07 -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 44DC4C14F604 for <mpls@ietf.org>; Sun, 29 Sep 2024 17:38:07 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4XH2BJ3fV9z6L6sP for <mpls@ietf.org>; Mon, 30 Sep 2024 08:34:00 +0800 (CST)
Received: from lhrpeml100006.china.huawei.com (unknown [7.191.160.224]) by mail.maildlp.com (Postfix) with ESMTPS id B55FA140155 for <mpls@ietf.org>; Mon, 30 Sep 2024 08:38:05 +0800 (CST)
Received: from dggpemf100009.china.huawei.com (7.185.36.128) by lhrpeml100006.china.huawei.com (7.191.160.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Mon, 30 Sep 2024 01:38:04 +0100
Received: from kwepemf100007.china.huawei.com (7.202.181.221) by dggpemf100009.china.huawei.com (7.185.36.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Mon, 30 Sep 2024 08:38:02 +0800
Received: from kwepemf100007.china.huawei.com ([7.202.181.221]) by kwepemf100007.china.huawei.com ([7.202.181.221]) with mapi id 15.02.1544.011; Mon, 30 Sep 2024 08:38:02 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Joel Halpern <jmh@joelhalpern.com>, "Zafar Ali (zali)" <zali=40cisco.com@dmarc.ietf.org>, Tony Li <tony.li@tony.li>
Thread-Topic: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)
Thread-Index: AQHbDoUwKFW6ojt28kyIJnukrZbcFLJpvwyAgAD84/CAAwAlgIAACnkAgACEz4CAAAS0gIABM6+A
Date: Mon, 30 Sep 2024 00:38:02 +0000
Message-ID: <17a93a68d5ce4571b0ad19a342e8d684@huawei.com>
References: <DS0PR19MB65014515D511B396E79BA36FFCF82@DS0PR19MB6501.namprd19.prod.outlook.com> <LV8P220MB1914BBB4896362040615CAB2FC6F2@LV8P220MB1914.NAMP220.PROD.OUTLOOK.COM> <5f5db9a20d8e4b47b5515b686e834227@huawei.com> <4819c3baa7bd4bff81babbd913db2227@huawei.com> <DM6PR11MB46922AC760C358D172A6A4B7DE752@DM6PR11MB4692.namprd11.prod.outlook.com> <452FDD29-F8A9-417A-8BC6-B16721385AEC@tony.li> <DM6PR11MB46923BEAA8216EFBE0545290DE752@DM6PR11MB4692.namprd11.prod.outlook.com> <6b90419c-bcfc-4684-b183-ff0c89b7a3c1@joelhalpern.com>
In-Reply-To: <6b90419c-bcfc-4684-b183-ff0c89b7a3c1@joelhalpern.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.118]
Content-Type: multipart/alternative; boundary="_000_17a93a68d5ce4571b0ad19a342e8d684huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: PQRG6N5UOE6YQYH2737WPYYVIUBR5HLU
X-Message-ID-Hash: PQRG6N5UOE6YQYH2737WPYYVIUBR5HLU
X-MailFrom: zhoutianran@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mpls <mpls@ietf.org>, "Zhukeyi(Kaiyin,Datacom Standard&Patent)" <zhukeyi@huawei.com>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/qImiAzPgJpchnRH5XUhWx8a310I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>

My interpretation of your point shows draft-ietf-mpls-mna-hdr is premature.
It does not well consider how to adapt and support PSD.
In addition, ISD still need to resolve many challenges in SR case.

Tianran

From: Joel Halpern [mailto:jmh@joelhalpern.com]
Sent: Sunday, September 29, 2024 10:12 PM
To: Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org>; Tony Li <tony.li@tony.li>
Cc: mpls <mpls@ietf.org>
Subject: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)


I fail to see the coupling you are asserting.  We can happily define the reserved bit in the ISD RFC.  And then, if the WG adopts a PSD draft, it can define that bit to have specific meaning, if the solution needs that.  We do this all the time in lots of our protocols.  That is in fact why we define reserved bits.  Any solution implementing PSD will know about that bit and its meaning.  The fact that some ISD solutions that do not support PSD do not know aobut the bit does not cause any difficulty.  The PSD solution already needs to deal with requiring that the node addressed by the bottom of the stack understands PSD and will properly remove the PSD.

I also disagree with a number of the other objections.  I am trying to think through the clearest way to explain my disagreement.  I hope to post that within a few days.

Yours,

Joel
On 9/29/2024 9:55 AM, Zafar Ali (zali) wrote:
Hi Tony

I am aware of the thread but all we hear is that chairs are discussing the responses and will share further update, “interest” vs. “consensus” debate, the chairs are discussing how to initiate the PSD debate, etc. There were 65 emails on the original PSD poll. I am not sure why we need another round of debate and what will be the nature of that debate. Why not just start WG adoption call and gauge the WG “consensus”.

For the reason many others and I mentioned, I also fail to see the rush to progress draft-ietf-mpls-mna-hdr, prematurely.
Let’s first have the working group complete the work on PSD and all the pieces and gain implementation maturity.

Thanks

Regards … Zafar

From: Tony Li <tony1athome@gmail.com><mailto:tony1athome@gmail.com> on behalf of Tony Li <tony.li@tony.li><mailto:tony.li@tony.li>
Date: Sunday, September 29, 2024 at 2:00 AM
To: Zafar Ali (zali) <zali@cisco.com><mailto:zali@cisco.com>
Cc: Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org><mailto:zhoutianran=40huawei.com@dmarc.ietf.org>, Dongjie (Jimmy) <jie.dong=40huawei.com@dmarc.ietf.org><mailto:jie.dong=40huawei.com@dmarc.ietf.org>, Tarek Saad <tsaad.net@gmail.com><mailto:tsaad.net@gmail.com>, mpls <mpls@ietf.org><mailto:mpls@ietf.org>, mpls-chairs <mpls-chairs@ietf.org><mailto:mpls-chairs@ietf.org>, draft-ietf-mpls-mna-hdr@ietf.org<mailto:draft-ietf-mpls-mna-hdr@ietf.org> <draft-ietf-mpls-mna-hdr@ietf.org><mailto:draft-ietf-mpls-mna-hdr@ietf.org>
Subject: Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)
[WG chair hat: on]

Hi Zafar,



On Sep 28, 2024, at 10:22 PM, Zafar Ali (zali) - zali at cisco.com <mailforwards@cloudmails.net><mailto:mailforwards@cloudmails.net> wrote:

There was a rather encrypted WG poll on PSD interest which shows clear support from vendors and operators to work on the PSD option.
However, the working group has not heard any outcome of the poll.

Tarek posted the outcome of the poll on August 14th: https://mailarchive.ietf.org/arch/msg/mpls/qHBCt-X17u_VLIbuJuuS22C-ru8/

There were several subsequent comments on that thread that were also relevant.

T




_______________________________________________

mpls mailing list -- mpls@ietf.org<mailto:mpls@ietf.org>

To unsubscribe send an email to mpls-leave@ietf.org<mailto:mpls-leave@ietf.org>