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

Tianran Zhou <zhoutianran@huawei.com> Mon, 30 September 2024 01:36 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 1B536C14F702 for <mpls@ietfa.amsl.com>; Sun, 29 Sep 2024 18:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 hv6mB4PKO8eb for <mpls@ietfa.amsl.com>; Sun, 29 Sep 2024 18:36:34 -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 DD22CC14F694 for <mpls@ietf.org>; Sun, 29 Sep 2024 18:36:33 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4XH3Tk1ymJz6LDcR for <mpls@ietf.org>; Mon, 30 Sep 2024 09:32:26 +0800 (CST)
Received: from lhrpeml100006.china.huawei.com (unknown [7.191.160.224]) by mail.maildlp.com (Postfix) with ESMTPS id 8675D1401DC for <mpls@ietf.org>; Mon, 30 Sep 2024 09:36:31 +0800 (CST)
Received: from dggpemf200008.china.huawei.com (7.185.36.39) 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 02:36:30 +0100
Received: from kwepemf100007.china.huawei.com (7.202.181.221) by dggpemf200008.china.huawei.com (7.185.36.39) 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 09:36:28 +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 09:36:28 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Joel Halpern <jmh@joelhalpern.com>
Thread-Topic: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)
Thread-Index: AQHbDoUwKFW6ojt28kyIJnukrZbcFLJpvwyAgAD84/CAAwAlgIAACnkAgACEz4CAACZagIABAzlA//+F8wCAAIsZoP//gLeAgACMrKA=
Date: Mon, 30 Sep 2024 01:36:28 +0000
Message-ID: <aa8154bfa19d494b8e75b9523c8d508c@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> <2AEEDFE6-230A-4A19-BF5E-3B9AC34B5603@tony.li> <7390a29e261f4728a31e6984240efdab@huawei.com> <CA+RyBmXLYTybEGsSK6Wx0+g-TnPStWGN-zosfRutsJ1Eo2kDzA@mail.gmail.com> <17428b303a3540ba8266b78128f27938@huawei.com> <940c9751-0731-4d6f-9087-dc6efe610b32@joelhalpern.com>
In-Reply-To: <940c9751-0731-4d6f-9087-dc6efe610b32@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_aa8154bfa19d494b8e75b9523c8d508chuaweicom_"
MIME-Version: 1.0
Message-ID-Hash: MUCCZGSGLWLJXWR5FAH7PXAOLXD7S3JS
X-Message-ID-Hash: MUCCZGSGLWLJXWR5FAH7PXAOLXD7S3JS
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/XCE0a5WFsUPATvBNhHT17aKVYq4>
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>

So the next step for the WG is to work out the PSD and see how ISD and PSD can complement and be compatible.
It’s not the time to finalize draft-ietf-mpls-mna-hdr in hurry.
Especially when there is no hands on implementation.

Tianran

From: Joel Halpern [mailto:jmh@joelhalpern.com]
Sent: Monday, September 30, 2024 9:06 AM
To: Tianran Zhou <zhoutianran@huawei.com>
Cc: mpls <mpls@ietf.org>
Subject: Re: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)


If someone wants to put a proposal on the table for PSD that does not require ISD, they can do so.  And the WG can, if the process moves that far, consider that solution.  But, by definition, if the solution does not use ISD then it has no impact on advancing the mna-hdr draft solution for those cases which use ISD.  I still do not see the coupling you are asserting.

In particular, while the requirements permit such a solution, they do not mandate it.  Since we do not even have a proposal for how to do PSD without ISD, it seems really confusing to be objecting to advancing the mna-hdr draft on such a basis.

Yours,

Joel
On 9/29/2024 8:43 PM, Tianran Zhou wrote:
Hi Greg,

Please see below:

   5.   Subject to the constraints in these requirements, a Network
        Action solution MAY carry MNA information in-stack, post-stack,
        or both in-stack and post-stack.

   6.   Solution specifications MUST NOT require an implementation to
        support in-stack ancillary data, unless the implementation
        chooses to support an NA that uses in-stack ancillary data.

Tianran
From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: Monday, September 30, 2024 8:24 AM
To: Tianran Zhou <zhoutianran@huawei.com><mailto:zhoutianran@huawei.com>
Cc: Tony Li <tony.li@tony.li><mailto:tony.li@tony.li>; Zafar Ali (zali) <zali@cisco.com><mailto:zali@cisco.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>
Subject: Re: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)

Hi Tianran,
Please point me to the part of RFC 9613<https://datatracker.ietf.org/doc/rfc9613/> that supports your request.

Regards,
Greg

On Sun, Sep 29, 2024 at 4:44 PM Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org<mailto:40huawei.com@dmarc.ietf.org>> wrote:
The IPR poll for the two document did not hit the point.
The point is how can the MNA mechanism disable the ISD and use PSD only.
The draft-ietf-mpls-mna-hdr need to resolve this.

Tianran

From: Tony Li [mailto:tony1athome@gmail.com<mailto:tony1athome@gmail.com>] On Behalf Of Tony Li
Sent: Monday, September 30, 2024 12:13 AM
To: Zafar Ali (zali) <zali@cisco.com<mailto:zali@cisco.com>>
Cc: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>; 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>
Subject: Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)


Hi Zafar,

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”.


That’s exactly what we’re doing. The process for doing this begins with an IPR poll.

Nic started the IPR poll on draft-mb-mpls-ioam-dex and draft-gandhi-mpls-ioam-dex on Sept 3.
https://mailarchive.ietf.org/arch/msg/mpls/XU3Ycij6Oq2kGWi14k3eXmpdQvM/
https://mailarchive.ietf.org/arch/msg/mpls/7NmJqyMHDairPxEn7PGxz99KNiI/

Tony


_______________________________________________
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>


_______________________________________________

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>