Re: [mpls] Regarding adopting draft-song-mpls-extension-header - do we need post stack data?

Tony Li <tony.li@tony.li> Thu, 23 February 2023 06:38 UTC

Return-Path: <tony1athome@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 DF145C15257C for <mpls@ietfa.amsl.com>; Wed, 22 Feb 2023 22:38:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.096, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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] autolearn=no 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 WlBYRmP--bqx for <mpls@ietfa.amsl.com>; Wed, 22 Feb 2023 22:38:33 -0800 (PST)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 2EDB4C14F737 for <mpls@ietf.org>; Wed, 22 Feb 2023 22:38:33 -0800 (PST)
Received: by mail-pg1-x533.google.com with SMTP id w36so15103pgl.10 for <mpls@ietf.org>; Wed, 22 Feb 2023 22:38:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:sender:from:to:cc:subject:date:message-id:reply-to; bh=fNwz+dw/ICVyrJq4KwCWIG+KiEk/pggWI3tbsz3paIc=; b=jvQ+tn9NVJnZJC3jxmkqaydnDwGJ4oAmVQoMxuKfDQXVWdHccmvnboBSl85T8LyDoR 62NHUIUOZ7LJlJvc09FQpiu8Hy14Wx0RYVmoqBTUxK40o16JTLra5NK9zgvQz6GcnE1I pKS9E+OenfYNo7dgR1rP/fJmGNRSMoufdJqu3XDPPPYSTyCs+q6vabTpNr0koJQOHsTD 5xMAKT0HKI6ghn7r1ki4Ep9VhtWVQhum8NMXzDMkFslPYzk6mSRMKZWHtTbbIC+7Ajnt 4W+x8BQtFF1NlGPqEW2YValY4nvZsPd+wZ20w5qY3Qsg5HmanluWG462vHNiyT145PNr pmGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fNwz+dw/ICVyrJq4KwCWIG+KiEk/pggWI3tbsz3paIc=; b=woB/FtPLfxq3fWxmakEqqGXrYuQg43R4UO6xSP9FGS4S657JrHuFOZvL2LlPLeSQk4 tcDeUcWNWfyzdLjw1uHdHn/V/C44ztrolXOn+HTXDzecK0vDmzPcDGYsA0IKp9EoJEDK NJulf3WN+cm0zgivPn02sqXoB16xl3MdBo3sAVKQpeT9K5c77ByZppajXM03YuuhAz/R 0J1NHrn2dFsE9PNn2iichpyz5PSZ5/DvK8fhT6TfrgJMU/ZGI84AynG+CmcOta2u8tNQ MzhPpE6HySsiZ972gFiN4f3/pZGVSXasz1jr0cHU4zZ+kziM0FmY6rLBlRPbd1afcKwA Rftw==
X-Gm-Message-State: AO0yUKUUrLc7mRxjDIZPl0eKKD6yBVBe3wyGhxsvj4GbORAsNgWeoE2L rHA+61FuWkBHcAUcrxYROTg=
X-Google-Smtp-Source: AK7set/KVFmoeBn/OR3vxdzz2g3XKGbvcN3XHv8sCEJmHQ0ayakXyHI5E81oT9SsfAxFMw6Pz/uR9A==
X-Received: by 2002:a62:19d3:0:b0:5aa:2d65:4733 with SMTP id 202-20020a6219d3000000b005aa2d654733mr10650957pfz.10.1677134312112; Wed, 22 Feb 2023 22:38:32 -0800 (PST)
Received: from smtpclient.apple (c-73-231-1-11.hsd1.ca.comcast.net. [73.231.1.11]) by smtp.gmail.com with ESMTPSA id a20-20020aa78654000000b005a8bfe3b241sm2842775pfo.167.2023.02.22.22.38.31 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Feb 2023 22:38:31 -0800 (PST)
Sender: Tony Li <tony1athome@gmail.com>
From: Tony Li <tony.li@tony.li>
Message-Id: <3A6E13BC-085A-450C-9527-D7BFBCA8F492@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_ED0D1754-03D2-4CDE-B570-68F8DACB8F16"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\))
Date: Wed, 22 Feb 2023 22:38:20 -0800
In-Reply-To: <2d587c97adc54256b1024dc5cfdda725@huawei.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Joel Halpern <jmh@joelhalpern.com>, mpls <mpls@ietf.org>
To: "Dongjie (Jimmy)" <jie.dong=40huawei.com@dmarc.ietf.org>
References: <27b7ff60-4ce1-c053-5c87-42cb4919d79e@joelhalpern.com> <BY3PR13MB4787D662D08331C19F7FB4679AA59@BY3PR13MB4787.namprd13.prod.outlook.com> <97F4AD9B-E131-4BDB-A713-33DD3B0D1D16@tony.li> <BY3PR13MB4787643941C35EACB322010F9AA59@BY3PR13MB4787.namprd13.prod.outlook.com> <CA+RyBmWQPZ8Yu2Xitw1JbEc_v7ZPPHkcj1L-5+fPTkZ36b-X1Q@mail.gmail.com> <BY3PR13MB4787D59355E94935CDEC21359AA59@BY3PR13MB4787.namprd13.prod.outlook.com> <CA+RyBmVxm21a=1istKUcnzFHsabYTNqYk9oPpP98i8P9xMvN1Q@mail.gmail.com> <BY3PR13MB47878D42A5F93813F0863A6E9AA59@BY3PR13MB4787.namprd13.prod.outlook.com> <CA+RyBmVD=apZX2UCT=cYEUg61qcEz8myeP2aNbzERkhK1d50eA@mail.gmail.com> <BY3PR13MB47879B845928B62F600CF47B9AAA9@BY3PR13MB4787.namprd13.prod.outlook.com> <979aa1f2-016d-5a5f-15ce-35893e66a4e0@joelhalpern.com> <79242C42-DF57-44F0-AD57-5B4E2222624D@gmail.com> <2d587c97adc54256b1024dc5cfdda725@huawei.com>
X-Mailer: Apple Mail (2.3731.300.101.1.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/1tKAMDXGBxmyjDhDWGj3nbDDiHE>
Subject: Re: [mpls] Regarding adopting draft-song-mpls-extension-header - do we need post stack data?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2023 06:38:35 -0000

Hi Jimmy,

> However it is not the case for MNA.  As I reminded Joel in one mail yesterday, there was a WG poll on “ISD and PSD in the MNA framework”, and the WG consensus is to have both ISD and PSD as part of the MNA framework. This is also reflected in the current MNA framework document.
>  
> Procedurally any change to that consensus requires another round of discussion, WG poll, and potential update of the MNA framework first, and in that case both of the solution documents would need to wait.


Well, I for one, would be happy to wait. I’d much rather take the time and get it right than rush and produce a mess.

Tony