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

Joel Halpern <jmh@joelhalpern.com> Sun, 29 September 2024 14:12 UTC

Return-Path: <jmh@joelhalpern.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 711B9C14F5F3 for <mpls@ietfa.amsl.com>; Sun, 29 Sep 2024 07:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, 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_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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 nVuf0BXQTz5x for <mpls@ietfa.amsl.com>; Sun, 29 Sep 2024 07:12:31 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12C25C14F5F9 for <mpls@ietf.org>; Sun, 29 Sep 2024 07:12:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4XGmPB5XSqz1q2h3; Sun, 29 Sep 2024 07:12:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1727619150; bh=MNjcYuRweEOHdgTHZ9BIYRR5taJAY2tpTXT/JndzPgU=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=YZnkvmyt57Hd8+NR5tdjjGuYP2NWBkCNoHmSVBqy85FndeNu0FI9StKL1e2Xxt5Cb 3IBnLKpEQN7ZVk8LNoGpbjMvD3GcYp/W4ma5MA17L4SgCC/sxijxup09YPE8cUHpdi 8XfFo4h0Bq14zlpm8u4aEs7+3erXnQibD0/jdefo=
X-Quarantine-ID: <QDeCz3gfh4kz>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.22.13] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4XGmPB10Thz1q2LJ; Sun, 29 Sep 2024 07:12:29 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------Cjd5fomOD3gvmbvJOxVkxSSK"
Message-ID: <6b90419c-bcfc-4684-b183-ff0c89b7a3c1@joelhalpern.com>
Date: Sun, 29 Sep 2024 10:12:25 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "Zafar Ali (zali)" <zali=40cisco.com@dmarc.ietf.org>, Tony Li <tony.li@tony.li>
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>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <DM6PR11MB46923BEAA8216EFBE0545290DE752@DM6PR11MB4692.namprd11.prod.outlook.com>
Message-ID-Hash: BTMNFHNMNZMXQ44FCK5V4LEPVEI2XM5L
X-Message-ID-Hash: BTMNFHNMNZMXQ44FCK5V4LEPVEI2XM5L
X-MailFrom: jmh@joelhalpern.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>
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/0OW5MV7eCaUiBUf6tz1FAE-Rj08>
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 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> on behalf of Tony Li 
> <tony.li@tony.li>
> *Date: *Sunday, September 29, 2024 at 2:00 AM
> *To: *Zafar Ali (zali) <zali@cisco.com>
> *Cc: *Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org>, Dongjie 
> (Jimmy) <jie.dong=40huawei.com@dmarc.ietf.org>, Tarek Saad 
> <tsaad.net@gmail.com>, mpls <mpls@ietf.org>, mpls-chairs 
> <mpls-chairs@ietf.org>, draft-ietf-mpls-mna-hdr@ietf.org 
> <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> 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
> To unsubscribe send an email tompls-leave@ietf.org