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

Stewart Bryant <stewart.bryant@gmail.com> Thu, 03 October 2024 09:50 UTC

Return-Path: <stewart.bryant@gmail.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 6417CC1519B3 for <mpls@ietfa.amsl.com>; Thu, 3 Oct 2024 02:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_DNSWL_BLOCKED=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 PopjTKZQpdjo for <mpls@ietfa.amsl.com>; Thu, 3 Oct 2024 02:50:22 -0700 (PDT)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 473C3C15155F for <mpls@ietf.org>; Thu, 3 Oct 2024 02:50:22 -0700 (PDT)
Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-a8d2b24b7a8so349982466b.1 for <mpls@ietf.org>; Thu, 03 Oct 2024 02:50:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727949021; x=1728553821; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=Alh31yWDfirMH4lNx2/gatfuD7H4+m/ds5Em4cHTB+0=; b=EtmthIqs9K/1q53WTDRk0H3demzMyRXB9NifuE5nyRNp1hRuTntG7cGjhAMzNbk7KW Wmd4pDJVRKsRwXfq/zD4IW6uRDw5d1pfQGYX0D8xEoUmobf1mYABZoF8U15PntVQbKsh a0gBCPaJWkoaPNdTy8XAZkeujmakLMPDOYf/x/SwLJzmd3pfobZVCScsIJIOolH+Mivy IOcDb3WL7hC0MhMl08+lHFZdS8zFPy3+2QwjbyASVX5PfVm7BT4jnhPPAKYwnxyiYmr1 OVC/1vHHcwZ8Aq4tnMxj1V52nx1XnY32OjNvdI7ZU+/V+4ZWX1CT/YAaw2MQs/tnkUjO cdrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727949021; x=1728553821; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Alh31yWDfirMH4lNx2/gatfuD7H4+m/ds5Em4cHTB+0=; b=BgR2JHrOjqOSvW/QmQ5T6Cb8+45JaxwKlPPPa2ll5dpsoKDwVe+wMZtcaSCwOuKKuc BtTeddC3Gb/i6G5+aekQOCgKr1HDtZyGdE2NlAQACWe8+RhpLk667+PbTUxcPHYqjkaK aXuK81DZvAcfL9W+cwGkvOOUQNXbL+zqryL4DkNv4mHZn2uxMU03y0f4b8rcXpA/b5Rv y3Ukp/YC1dhq9To5gMzh+uBf2rpCdojyvOC71XYzPSw47+7qgzPkvVbs6Tda4woa7qHx Hgfj6T2euWLBYsU0doePnRDdh3wUoWzHnyagsU8uzw9dsXhn6JcECq8/6DJ7XP59buGe zgng==
X-Forwarded-Encrypted: i=1; AJvYcCVwHK1nMaMRarN5Psbi7TYwaUvjTKbTvrVbDGw+GB7Es+w40SlGWzc1b2cnOvW76zT+zyP/@ietf.org
X-Gm-Message-State: AOJu0Yw5C42yoYg+1eXuodMkxTOFBqjPUgU44DfrJANthjvmVP7TrLG/ BL9+eAYaZxa7SZ/GXFCGj3PONGiSMDVWQnKKMEN65X3NT988XVHB
X-Google-Smtp-Source: AGHT+IG3BCxvn2LE/esZ8I7eRuf+ITl20suoLR6B3i2T6nGEkW3rJNg6sKHb7KCFDU5w7fE8pIE4dQ==
X-Received: by 2002:a17:906:fd83:b0:a77:ab9e:9202 with SMTP id a640c23a62f3a-a990a03463cmr287601366b.4.1727949020306; Thu, 03 Oct 2024 02:50:20 -0700 (PDT)
Received: from smtpclient.apple ([148.252.132.241]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a99104731a5sm60243066b.180.2024.10.03.02.50.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Oct 2024 02:50:19 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <5BE47B18-8E1C-46B8-B066-E249E59A72FC@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4AB0EE8D-AE0C-4B18-AF9D-5519FE114DB5"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
Date: Thu, 03 Oct 2024 10:50:08 +0100
In-Reply-To: <DM6PR11MB46923AC9A8019DC5AA31EA14DE772@DM6PR11MB4692.namprd11.prod.outlook.com>
To: "Zafar Ali (zali)" <zali=40cisco.com@dmarc.ietf.org>
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> <aa8154bfa19d494b8e75b9523c8d508c@huawei.com> <d4620d84-9e57-4931-a92c-ac36fe9d6c9a@joelhalpern.com> <1d091faa1bb5408fa19a5feee479fb4c@huawei.com> <f404e92c-4618-4245-b5ce-e1ff232296d5@joelhalpern.com> <DM6PR11MB46923AC9A8019DC5AA31EA14DE772@DM6PR11MB4692.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3776.700.51)
Message-ID-Hash: 6AF4GSYDR5NI6Z3FGECXDV77KZKWTIUX
X-Message-ID-Hash: 6AF4GSYDR5NI6Z3FGECXDV77KZKWTIUX
X-MailFrom: stewart.bryant@gmail.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: Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org>, mpls <mpls@ietf.org>
X-Mailman-Version: 3.3.9rc5
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/fScxlJzk_3WXLa3_8PuOAD5-UuI>
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>

I share that concern.

Stewart

> On 1 Oct 2024, at 17:37, Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org> wrote:
> 
> Dear chairs and the WG,
>  
> I agree with Tianran. 
> I am also concerned about lack of implementation experience and interoperability for a data plane change addressing a subset of the MNA architecture.
> These are hardware changes that are not proven or demonstrated in the field, yet.
>  
> Thanks
>  
> Regards … Zafar
>  
> From: Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org <mailto:zhoutianran=40huawei.com@dmarc.ietf.org>>
> Date: Monday, September 30, 2024 at 8:08 PM
> To: Joel Halpern <jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>
> Cc: mpls <mpls@ietf.org <mailto:mpls@ietf.org>>
> Subject: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)
> 
> Looking at the use case draft, PSD can address all use cases and future proof. In this sense, there is no need to implement ISD at all.
> 
> I also started a thread in the working group mailing list to investigate the operators requirements. I only got one requirement on noffrr. There’s rare interest on existing MNA.
> 
> I can’t believe we are going to publish such paper work in a hurry.
> 
> Tianran 
> 
> 
> 
> 
> 
> Sent from WeLink
> 发件人: Joel Halpern<jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>
> 收件人: Tianran Zhou<zhoutianran@huawei.com <mailto:zhoutianran@huawei.com>>
> 抄送: mpls<mpls@ietf.org <mailto:mpls@ietf.org>>
> 主题: Re: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)
> 时间: 2024-09-30 10:40:20
>  
> Given that the PSD proposal on the table requires the ISD draft, and does not require any changes to the ISD draft, I do not understand your comments.  You have said you do not want any ISD solution, and now you are suggesting we adopt a PSD solution that requires ISD?
> 
> And it is not clear that we need a PSD solution at all.
> 
> If we need a PSD solution, I expect with some clarifications and modifications the jags psd draft can serve as a basis for further work.  I would strongly prefer to get the ISD work done.  Then we can have the debate about whethere we need PSD, and then discuss what a solution should look like.
> 
> Yours,
> 
> Joel
> 
> On 9/29/2024 10:16 PM, Tianran Zhou wrote:
> Then why not adopting that PSD proposal as the base for discussion? And find out how it will require the draft-ietf-mpls-mna-hdr.
>  
> Best,
> Tianran
>  
> From: Joel Halpern [mailto:jmh@joelhalpern.com]
> Sent: Monday, September 30, 2024 9:43 AM
> To: Tianran Zhou <zhoutianran@huawei.com> <mailto:zhoutianran@huawei.com>
> Cc: mpls <mpls@ietf.org> <mailto:mpls@ietf.org>
> Subject: Re: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)
>  
> So we should hold up the ISD draft for some proposal to appear?  The one PSD proposal we have on the table does not require any changes to the mna-hdr ISD draft.    That seems to request arbitrary delay from the WG without justification.
> 
> Yours,
> 
> Joel
> 
> On 9/29/2024 9:36 PM, Tianran Zhou wrote:
> 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> <mailto:zhoutianran@huawei.com>
> Cc: mpls <mpls@ietf.org> <mailto: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>_______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org