[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:48 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 279FFC1519A2; Thu, 3 Oct 2024 02:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_NONE=-0.0001, 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=unavailable 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 d2bOSXtBr7rI; Thu, 3 Oct 2024 02:47:54 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 A5EDFC1519A7; Thu, 3 Oct 2024 02:47:54 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-a8d56155f51so82222966b.2; Thu, 03 Oct 2024 02:47:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727948873; x=1728553673; 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=rIJmTkjwSY0qRXYMoHUJPaKMO3EaDdIJT6D76e9jhq8=; b=hEb5WzJbvG2DQjDXjEXgwA/wIwsvD+EB/YfImsTVfCyKdaMutkfvGmVbYmdWwTjr7K sb23U/IXharwQ4YM/tBtrz8vYPSuEQJvRIkRnxAPf3kfga5lWzQ7avfyZL8NmsiAhgmI tHwOWsJEHTXmNq2v+e5mYgua6i2ZoHimOSo5sbylGF//g3c+ExL4F4z0rlqgitVe2gAB o28lhuyt9i/P7UAMbScc+tV7+wct1CgF9oQ8qXKPGat9zkgnc0AOanJcdnrG5w1WtAe+ sFcHFFcRu5A6dUO1DH21SGut6WhENEZ6J50T1BbShpvaiYB0ko/+Q8c3NKycthEC4MaD oQhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727948873; x=1728553673; 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=rIJmTkjwSY0qRXYMoHUJPaKMO3EaDdIJT6D76e9jhq8=; b=vsIUrQTO9Q+Wa+y5Vi6rp+V5TLBAwOXz4JXYZ7MB5MrZhsprDRTL8vk/YisHUS6Mkx WZLUGrvM5J6ERuMr22ezJbhiY0gGgnKurn5lJTxPYunBLGEX1pSBebBpNa4rMdkUmJuh /qHtj9scGy4KE1bj7W7XIZWbeX9kv84Ys7oj84Lb9IAVfW24n8M8T20vqoA/XV2uoehg 0FBecBA5HJ/5zmwe1AUSriiQkMsT6c9uHx84v5oTkXnQ9/JJKexoET+II2XVK415k9Z8 jzbYPyRdPHf2k3YPOtLXKXo5Sar/GIbyk2DD4jlSuU1KoG2sRug2yMUektGhaUkFWgms wILQ==
X-Forwarded-Encrypted: i=1; AJvYcCUAU08E7AlHbPnlE03Nagl9uEDQFPvo2qeAkS3iyjt0w6YSGMTKaVIsFUtxDkNvdLT3tmtDvMnCXnUVhEWziG238hBB7gPI+g==@ietf.org, AJvYcCUxvmj0NjcAkXD/jCKbOeUO46EJ+a7kK9fp24UYGlA3pZH/covJpiTxPHwx8EKfya3pjYOMzswtcyBnN8M=@ietf.org, AJvYcCWFT3NjAiblBV9NeBTwi3s3AYXqQ9ZcTK9ztWpaRAvagWjVCw9HehZ9vLBRzsNGw3xKfyRc0w==@ietf.org
X-Gm-Message-State: AOJu0YwbU+K+aviy1qLd/L55O5jKT21FS/Zhr5plXKWdWH2rvjUbzCpE lMS+5b3hkyrG4FtPk5D2MmaE8FpB7HE7v4BxMdrylMnNPw+zTw/v
X-Google-Smtp-Source: AGHT+IFqyAUDlQsPFa7NZiSdFyLiP21FNkMR8bnmQVFOCpXeZLHBLvkyKgTE/NJERb+u0Y+s8emelw==
X-Received: by 2002:a17:907:97c4:b0:a8d:4db8:9edf with SMTP id a640c23a62f3a-a98f8362d79mr494971966b.42.1727948872887; Thu, 03 Oct 2024 02:47:52 -0700 (PDT)
Received: from smtpclient.apple ([148.252.132.241]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a991047a9acsm60860566b.185.2024.10.03.02.47.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Oct 2024 02:47:52 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <998C98F5-3F9F-47C9-A61E-7111140D7F08@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_753CC052-710D-4E12-8073-BE5B4E6124F9"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
Date: Thu, 03 Oct 2024 10:47:40 +0100
In-Reply-To: <78118251-C577-4079-82D9-C688B0AEB088@tony.li>
To: Tony Li <tony.li@tony.li>, James Guichard <james.n.guichard@futurewei.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> <CABNhwV1w3UU+CCbw7JUQ_B4q8MbrO0W-r8vTtY_AZb6q5SQ3hQ@mail.gmail.com> <CABNhwV3=wLZ7+JAJqDwTkb6hbEzb4ZshZ5h=22g6DpGq0OR4xg@mail.gmail.com> <293634235.11486342.1727703337762@mail.yahoo.com> <1967059291.1285279.1727707657938@mail.yahoo.com> <78118251-C577-4079-82D9-C688B0AEB088@tony.li>
X-Mailer: Apple Mail (2.3776.700.51)
Message-ID-Hash: MRLSVB64ET7FF7YC3XN4QTHH25OQXY7K
X-Message-ID-Hash: MRLSVB64ET7FF7YC3XN4QTHH25OQXY7K
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>, mpls-chairs <mpls-chairs@ietf.org>, "draft-ietf-mpls-mna-hdr@ietf.org" <draft-ietf-mpls-mna-hdr@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/AxKYTgx6jKoOQESb1WIE8RovM2M>
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>

The WG leadership position may or may not align with the consensus of the WG.

If the WG disagrees, with the chairs, the AD may express an opinion, but it would be unusual for the WG consensus to take priority on a matter such as this.

In the event of a disagreement the WG or indeed any member of the WG  can appeal, or and in any case they can elevate their concerns to the IESG at IETF LC, or even post approval through the appeal process.

The normal approach in cases such as this would be to resolve the PSD situation by WG consensus rather than WGC direction, and I would hope that is the path that we follow.

Best regards

Stewart


> On 30 Sep 2024, at 17:56, Tony Li <tony.li@tony.li> wrote:
> 
> 
> [WG chair hat: on]
> 
> As has been pointed out, we have not conducted a discussion and a consensus check on whether PSD is required. After discussions, WG leadership has decided not to take that path and that we will simply continue to progress documents and let discussions happen within that context.
> 
> Regards,
> Tony
> 
> 
>> On Sep 30, 2024, at 7:47 AM, John Drake <je_drake@yahoo.com> wrote:
>> 
>> Hi,
>> 
>> I will defer to the chairs who are responsible for judging consensus. 
>> 
>> Thanks,
>> 
>> John
>> 
>> On Monday, September 30, 2024 at 07:44:17 AM PDT, Tianran Zhou <zhoutianran=40huawei.com@dmarc.ietf.org> wrote:
>> 
>> 
>> > There is no consensus that PSD is required and as Joel points out
>> 
>> Could you please point out how you get this?
>> 
>> Tianran 
>> 
>> 
>> 
>> Sent from WeLink
>> 发件人: John Drake<je_drake=40yahoo.com@dmarc.ietf.org <mailto:je_drake=40yahoo.com@dmarc.ietf.org>>
>> 收件人: Zafar Ali (zali)<zali@cisco.com <mailto:zali@cisco.com>>;Gyan Mishra<hayabusagsm@gmail.com <mailto:hayabusagsm@gmail.com>>
>> 抄送: Tianran Zhou<zhoutianran@huawei.com <mailto:zhoutianran@huawei.com>>;Dongjie (Jimmy)<jie.dong@huawei.com <mailto:jie.dong@huawei.com>>;mpls@ietf.org <mailto:mpls@ietf.org>;MPLS Working 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>
>> 主题: Re: [mpls] Re: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)
>> 时间: 2024-09-30 21:36:02
>> 
>> Gyan,
>> 
>> There is no consensus that PSD is required and as Joel points out, the only PSD proposal on the table works just fine with draft-ietf-mpls-mna-hdr.
>> 
>> John 
>> 
>> 
>> On Sunday, September 29, 2024 at 08:23:20 PM PDT, Gyan Mishra <hayabusagsm@gmail.com> wrote:
>> 
>> 
>> 
>> Dear Chairs & WG 
>> 
>> To clarify my position on PSD work is that the work should be completed meaning at a minimum implemented by two vendors for interoperability and at WGLC state.  The MNA header draft now in WGLC could then be progressed including PSD solution.
>> 
>> Thank you 
>> 
>> Gyan
>> 
>> 
>> 
>> 
>> 
>> On Sun, Sep 29, 2024 at 3:33 AM Gyan Mishra <hayabusagsm@gmail.com <mailto:hayabusagsm@gmail.com>> wrote:
>> 
>> Dear Chairs & WG
>> 
>> I agree with points raised by  Zafar, Jimmy, Tianran, Loe and other WG members that this is a hardware implementation that is standards track and that said must have a minimum two interoperable implementations.
>> 
>> I support both ISD and PSD.
>> 
>> There has been a lot of discussions on ML about both and I think both should be included in this draft as they are in the MNA framework architecture draft section 3.6.
>> 
>> https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-fwk-10#name-encoding-of-post-stack-data
>> 
>> I agree the PSD work should be completed before we move forward with progressing this document.
>> 
>> This was from “IOAM and PSD” discussion this past summer:
>> 
>> From Michel Menth 8/3/23 below 
>> - presented some results at an interim meeting before:
>> https://datatracker.ietf.org/meeting/interim-2024-mpls-01/session/mpls
>> 
>> IOAM requires mutable data. In combination with multiple labels, e.g., for SR, these mutable data need to be near the bottom of the stack, otherwise they get popped along the way. Moving them to PSD makes encoding more efficient without increasing the effective header length that needs  to be parsed. Therefore, we think PSD is the better option for applications like IOAM.
>> 
>> This draft is not ready for progression at this time.
>> 
>> Kind Regards 
>>  <http://www.verizon.com/>
>> Gyan Mishra
>> Network Solutions Architect 
>> Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com>
>> M 301 502-1347
>> 
>> 
>> 
>> 
>> On Sun, Sep 29, 2024 at 1:24 AM Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org <mailto:40cisco.com@dmarc.ietf.org>> wrote:
>> Dear chairs and the WG,
>> 
>>  
>> 
>> I agree with points raised by Jimmy, Tianran, Loe and others.
>> 
>>  
>> 
>> This is hardware implementation.
>> 
>> The ask is to progress the document as a standards track RFC.
>> 
>> Having at least two interoperable implementations by vendors should be a bare minimum bar.
>> 
>>  
>> 
>> Support for PSD is part of the MNA architecture
>> 
> 
> _______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org