[mpls] Re: 答复: Working Group Adoption Poll for draft-li-mpls-mna-nrp-selector

Joel Halpern <jmh.direct@joelhalpern.com> Sun, 04 May 2025 14:17 UTC

Return-Path: <jmh.direct@joelhalpern.com>
X-Original-To: mpls@mail2.ietf.org
Delivered-To: mpls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id BEB9B248FF35 for <mpls@mail2.ietf.org>; Sun, 4 May 2025 07:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 0.536
X-Spam-Level:
X-Spam-Status: No, score=0.536 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SBL_CSS=3.335, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jgWTNpGiMO5U for <mpls@mail2.ietf.org>; Sun, 4 May 2025 07:17:46 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 mail2.ietf.org (Postfix) with ESMTPS id 8E20D248FF32 for <mpls@ietf.org>; Sun, 4 May 2025 07:17:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1746368262; bh=/seguXBZJVTgmarFYh5TeDz9O7f7ueu2CPUQXilyo6A=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Srg8cn77hDR353d5OzQdzAiuxJST/fXJq/YX5cGWM5HWG+24gSC5ZRqu3YQX0Q7h1 jeKla5lvSpRQoVu+cYYLZ7uCY44TfOx8P1dbKFw67BB4AzNqdJj71D/GmdTyKMZ3aQ 1cilaLB34hTmZpUhzScXKOr/pCriwRSdTiS12fr0=
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4Zr6F23sRxz6KD1Q; Sun, 4 May 2025 07:17:42 -0700 (PDT)
X-Quarantine-ID: <6P3cZxC41yUx>
X-Virus-Scanned: Debian amavis at a2.tigertech.net
Received: from [192.168.21.83] (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4Zr6F201wvz6K9MG; Sun, 4 May 2025 07:17:40 -0700 (PDT)
Message-ID: <8378c9f4-30e6-4794-a59e-308ed4e61d3a@joelhalpern.com>
Date: Sun, 04 May 2025 10:17:37 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Loa Andersson <loa@pi.nu>
References: <aaf2832d7370420e9bbdbd74297cd890@huawei.com> <4cbc99d1-77e3-4216-8c4b-013cb01b32e5@pi.nu> <CA+RyBmXaajqVTLPi540ydR9AH28WDnwU2D4iXY9Hjb2tr8j96Q@mail.gmail.com> <8437fc6e-e458-4e55-8009-088166eafe49@pi.nu> <CA+RyBmWB7BNaM7BVoact4HsgHnvWomQvUZq6QG8-U0YrkN54Fg@mail.gmail.com> <504b8a45-07db-4102-b2e3-d7edc3c7cb87@pi.nu>
Content-Language: en-US
From: Joel Halpern <jmh.direct@joelhalpern.com>
In-Reply-To: <504b8a45-07db-4102-b2e3-d7edc3c7cb87@pi.nu>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: RVNJYHF2ZZL6F7WVFLVT7IXHPQEBU5LY
X-Message-ID-Hash: RVNJYHF2ZZL6F7WVFLVT7IXHPQEBU5LY
X-MailFrom: jmh.direct@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@ietf.org" <mpls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [mpls] Re: 答复: Working Group Adoption Poll for draft-li-mpls-mna-nrp-selector
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/xGm57QcQIQwt26mftaWAUaRNMBA>
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 am not seeing why there is a need to step back.

The Ipv6 draft, the TEAS draft (which really belongs in the MPLS WG) and 
the ISD NROP draft represent three different ways of encoding the 
information for different cases.  The two MPLS approaches represent 
different balances, probably suitable for different situations.

Yours,

Joel

On 5/4/2025 1:32 AM, Loa Andersson wrote:
> --Greg,
>
> I understand that you been working on all these drafts, that does not 
> change the need I see to step back and take  breath, take step back 
> and evaluate the entire set of drafts in this corner of the technology.
>
> /Loa
>
>
> Den 04/05/2025 kl. 03:26, skrev Greg Mirsky:
>> Hi Loa,
>> thank you for the clarification. Please find my notes below tagged 
>> GIM>>.
>>
>> Regards,
>> Greg
>>
>> On Sat, May 3, 2025 at 2:41 AM Loa Andersson <loa@pi.nu 
>> <mailto:loa@pi.nu>> wrote:
>>
>>     Greg,
>>
>>     inline plz.
>>
>>     Den 29/04/2025 kl. 23:21, skrev Greg Mirsky:
>>      > Hi Loa,
>>      > I've reviewed <https://mailarchive.ietf.org/arch/msg/mpls/
>>     <https://mailarchive.ietf.org/arch/msg/mpls/>
>>      > GgY4VnmcE5XkFzZ7l6KqrJWjPLY/>draft-li-mpls-mna-nrp-selector on 
>> the
>>      > request of RtgDir. I am not aware of any other document that
>>     proposes a
>>      > mechanism to signal a dedicated NRP Selector ID in the MPLS
>>     networks.
>>
>>     The two drafts I thought of are:
>>
>>     - draft-li-mpls-enhanced-vpn-vtn-id
>>     - draft-ietf-teas-ns-ip-mpls
>>
>>     The were both mentioned during the WGAP.
>>
>>     When there are draft closely neighbouring over even overlapping 
>> it is a
>>     good practice to have an ideaon where this corner of the 
>> technology is
>>     going and if there are good reasons to hold up a bit to allow 
>> authors
>>     and working groupos look into if we want to merge or continue to
>>     separate documents.
>>
>>
>>     I think we should take the time and consider these draft relative to
>>     each other.
>>
>> GIM>> I actively participated in thework of TEAS WG and commented on 
>> draft-ietf-teas-ns-ip-mpls and onthe topic of NRP Selector ID. Also, 
>> I closely follow draft-ietf-6man-enhanced-vpn-vtn-id <https:// 
>> datatracker.ietf.org/doc/draft-ietf-6man-enhanced-vpn-vtn-id/>that
>>
>> "specifies a new IPv6 Hop-by-Hop option to carry network
>>
>> resource related information (e.g., identifier) in data packets.  The
>>
>> NR Option can also be generalized for other network resource
>>
>> semantics and functions."
>>
>> Thus, in my opinion, the scope of draft-li-mpls-enhanced-vpn-vtn-id 
>> analogous to draft-ietf-6man-enhanced-vpn-vtn-id, and if 6man WG 
>> determined that a dedicated mechanism to carry NRP information 
>> addresses the real problem, so should the MPLS WG. Interestingly, I 
>> find that several opponents of WG adopting 
>> draft-li-mpls-enhanced-vpn-vtn-id are among the authors of 
>> draft-ietf-6man-enhanced-vpn-vtn-id.
>>
>>
>>     /Loa
>>
>>
>>
>>      > AFAIK, it is possible to use existing data plane elements to
>>     express NRP
>>      > ID, but none of that mechanism will be standardized as PS, thus
>>     causing
>>      > a legitimate interoperability concern. Standardizing the 
>> method to
>>      > signal the dedicated NRP Selector ID, in my opinion, is 
>> necessary.
>>      >
>>      > Regards,
>>      > Greg
>>      >
>>      > On Tue, Apr 29, 2025 at 2:16 AM Loa Andersson <loa@pi.nu
>>     <mailto:loa@pi.nu>
>>      > <mailto:loa@pi.nu <mailto:loa@pi.nu>>> wrote:
>>      >
>>      >     Aijun, Tianran, and Joel,
>>      >
>>      >     I'm not fully up to speed on NRP, and might have missed
>>     something.
>>      >
>>      >     But I understand that there are issues with this WGAP
>>      >
>>      >     - there are other drafts about witch it has been claimed that
>>     they
>>      >     addresses the same or similar problems
>>      >
>>      >     - since not all of these draft try fit NRP into MNA, but 
>> specify
>>      >     independent solutions, which makes it an open issue if we
>>     want an MNA
>>      >     approach for this problem.
>>      >
>>      >     Aijun, does not suggest NOT adopting the draft, but point 
>> at some
>>      >     issues
>>      >     that should be cleared up before adoption.
>>      >
>>      >     /Loa
>>      >
>>      >     Den 29/04/2025 kl. 11:20, skrev Tianran Zhou:
>>      >      > Hi Joel,
>>      >      >
>>      >      > I think Aijun’s reply is to the cfa of 
>>  draft-li-mpls-mna-nrp-
>>      >     selector,
>>      >      > not the lc.
>>      >      >
>>      >      > Tianran
>>      >      >
>>      >      > *发件人:*Joel Halpern <jmh@joelhalpern.com
>>     <mailto:jmh@joelhalpern.com>
>>      >     <mailto:jmh@joelhalpern.com <mailto:jmh@joelhalpern.com>>>
>>      >      > *发送时间:*2025年4月29日10:38
>>      >      > *收件人:*Aijun Wang <wangaijun@tsinghua.org.cn
>>     <mailto:wangaijun@tsinghua.org.cn>
>>      >     <mailto:wangaijun@tsinghua.org.cn
>>     <mailto:wangaijun@tsinghua.org.cn>>>; mpls@ietf.org
>>     <mailto:mpls@ietf.org>
>>      >     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>
>>      >      > *主题:*[mpls] Re: 答复: Working Group Adoption Poll for
>>     draft-li-
>>      >     mpls-
>>      >      > mna-nrp-selector
>>      >      >
>>      >      > Aijun, I posted a point-by-point technical rebuttl of the
>>     issues
>>      >     that
>>      >      > were raised.  Of those responses, there was some
>>     discussion that
>>      >     did not
>>      >      > actual prove there were issues for two of the points.  For
>>     the other
>>      >      > rebuttals, there was no response.  As far as I can tell,
>>     there is no
>>      >      > obstacle to the chairs calling for a WG last call.
>>      >      >
>>      >      > Now, having said that, I expect that issues will be raised
>>     if such a
>>      >      > last call takes place.  And those issues will be
>>     discussed.  And the
>>      >      > chairs will decide if the results of that discussion leads
>>     to a
>>      >      > successful or unsuccessful last call. That is in fact the
>>     purpose
>>      >     of a
>>      >      > last call.
>>      >      >
>>      >      > Yours,
>>      >      >
>>      >      > Joel
>>      >      >
>>      >      > On 4/28/2025 10:30 PM, Aijun Wang wrote:
>>      >      >
>>      >      >     Hi,
>>      >      >
>>      >      >     Given the intense discussions of this adoption 
>> call, the
>>      >     dispution
>>      >      >     of ISD/PSD, the ambiguous future of MNA based
>>     application, the
>>      >      >     transition of new MPLS WG etc, , I suggest to 
>> postpone the
>>      >     adoption
>>      >      >     call of this document.
>>      >      >
>>      >      >     The WG should provide the community, the operator the
>>     unified
>>      >      >     solution, not instead of some distinctive, proprietary
>>     solutions.
>>      >      >
>>      >      >     Some comprises should be coordinated.
>>      >      >
>>      >      >     PS.  I don’t like  John E. Drake’s tedious, “argument
>>     by emphatic
>>      >      >     assertion” (quote from his description to other 
>> persons).
>>      >      >
>>      >      >            Please state out your technical argument points
>>     once
>>      >     when you
>>      >      >     want to argue with others, or else, please stay in
>>     quiet and just
>>      >      >     listen to other experts’discussions.
>>      >      >
>>      >      >     Best Regards
>>      >      >
>>      >      >     Aijun Wang
>>      >      >
>>      >      >     China Telecom
>>      >      >
>>      >      >     *发件人:*forwardingalgorithm@ietf.org
>>     <mailto:forwardingalgorithm@ietf.org>
>>      >     <mailto:forwardingalgorithm@ietf.org
>>     <mailto:forwardingalgorithm@ietf.org>>
>>      >      >     <mailto:forwardingalgorithm@ietf.org
>>     <mailto:forwardingalgorithm@ietf.org>
>>      >     <mailto:forwardingalgorithm@ietf.org
>>     <mailto:forwardingalgorithm@ietf.org>>>
>>      >      >     [mailto:forwardingalgorithm@ietf.org
>>     <mailto:forwardingalgorithm@ietf.org>
>>      >     <mailto:forwardingalgorithm@ietf.org
>>     <mailto:forwardingalgorithm@ietf.org>>
>>      >      >     <mailto:forwardingalgorithm@ietf.org
>>     <mailto:forwardingalgorithm@ietf.org>
>>      >     <mailto:forwardingalgorithm@ietf.org
>>     <mailto:forwardingalgorithm@ietf.org>>>] *代表 *N.Leymann@telekom.de
>>     <mailto:N.Leymann@telekom.de>
>>      >     <mailto:N.Leymann@telekom.de <mailto:N.Leymann@telekom.de>>
>>      >      >     <mailto:N.Leymann@telekom.de
>>     <mailto:N.Leymann@telekom.de> <mailto:N.Leymann@telekom.de
>>     <mailto:N.Leymann@telekom.de>>>
>>      >      >     *发送时间:*2025年4月15日16:30
>>      >      >     *收件人:*mpls@ietf.org <mailto:mpls@ietf.org>
>>     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>
>>      >     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>
>>     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>>
>>      >      >     *抄送:*mpls-chairs@ietf.org <mailto:mpls-
>>     chairs@ietf.org> <mailto:mpls-chairs@ietf.org <mailto:mpls-
>>     chairs@ietf.org>>
>>      >     <mailto:mpls-chairs@ietf.org <mailto:mpls-chairs@ietf.org>
>>     <mailto:mpls-chairs@ietf.org <mailto:mpls-chairs@ietf.org>>>; 
>> draft-li-
>>      >      > mpls-mna-nrp-selector@ietf.org <mailto:mpls-mna-nrp-
>>     selector@ietf.org> <mailto:mpls-mna-nrp- <mailto:mpls-mna-nrp->
>>      > selector@ietf.org <mailto:selector@ietf.org>> <mailto:draft-li-
>>     mpls-mna-nrp- <mailto:draft-li-mpls-mna-nrp-> <mailto:draft-li-
>>     <mailto:draft-li->
>>      >     mpls-mna-nrp->
>>      >      > selector@ietf.org <mailto:selector@ietf.org>
>>     <mailto:selector@ietf.org <mailto:selector@ietf.org>>>
>>      >      >     *主题:*[mpls] Working Group Adoption Poll for draft-
>>     li-mpls-
>>      >     mna-nrp-
>>      >      >     selector
>>      >      >
>>      >      >     Dear WG,
>>      >      >
>>      >      >     This email starts a two-week poll on adopting draft-
>>     li-mpls-
>>      >     mna-nrp-
>>      >      >     selector as a MPLS working group document.
>>      >      >
>>      >      >     Please send your comments (support/not support) to the
>>     MPLS
>>      >     working
>>      >      >     group mailing list (mpls@ietf.org
>>     <mailto:mpls@ietf.org> <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>
>>      >     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>
>>     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>>).
>>      >      >
>>      >      >     Please give a technical motivation for your support/
>>     not support,
>>      >      >     especially if you think that the document
>>      >      >
>>      >      >     should not be adopted as a working group document.
>>      >      >
>>      >      >     There are three IPR disclosures against this document.
>>      >      >
>>      >      > https://datatracker.ietf.org/ipr/search/?
>>     submit=draft&id=draft- <https://datatracker.ietf.org/ipr/search/?
>>     submit=draft&id=draft->
>>      >     li- <https://datatracker.ietf.org/ipr/search/?
>>     submit=draft&id=draft-li- <https://datatracker.ietf.org/ipr/search/?
>>     submit=draft&id=draft-li->>
>>      >      >     mpls-mna-nrp-selector <https://datatracker.ietf.org/
>>     ipr/ <https://datatracker.ietf.org/ipr/>
>>      >     search/ <https://datatracker.ietf.org/ipr/search/ <https://
>>     datatracker.ietf.org/ipr/search/>>?
>>      >      >  submit=draft&id=draft-li-mpls-mna-nrp-selector>
>>      >      >
>>      >      >     All the authors/contributors have stated on the 
>> MPLS WG
>>      >     mailing list
>>      >      >     that they are unaware of any
>>      >      >
>>      >      >     undisclosed IPR that relates to this document.
>>      >      >
>>      >      >     This working group adoption poll ends April 29th, 
>> 2025.
>>      >      >
>>      >      >     Regards,
>>      >      >
>>      >      >     Nic (as MPLS WG Co-chair)
>>      >      >
>>      >      >
>>      >      >
>>      >      >  _______________________________________________
>>      >      >
>>      >      >     mpls mailing list -- mpls@ietf.org
>>     <mailto:mpls@ietf.org> <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>
>>      >     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>
>>     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>>
>>      >      >
>>      >      >     To unsubscribe send an email to mpls-leave@ietf.org
>>     <mailto:mpls-leave@ietf.org>
>>      >     <mailto:mpls-leave@ietf.org <mailto:mpls-leave@ietf.org>>
>>     <mailto:mpls- <mailto:mpls-> <mailto:mpls- <mailto:mpls->>
>>      >      > leave@ietf.org <mailto:leave@ietf.org>
>>     <mailto:leave@ietf.org <mailto:leave@ietf.org>>>
>>      >      >
>>      >      >
>>      >      > _______________________________________________
>>      >      > mpls mailing list -- mpls@ietf.org <mailto:mpls@ietf.org>
>>     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>
>>      >      > To unsubscribe send an email to mpls-leave@ietf.org
>>     <mailto:mpls-leave@ietf.org> <mailto:mpls- <mailto:mpls->
>>      > leave@ietf.org <mailto:leave@ietf.org>>
>>      >
>>      >     --
>>      >     Loa Andersson
>>      >     Senior MPLS Expert
>>      >     Bronze Dragon Consulting
>>      > loa@pi.nu <mailto:loa@pi.nu> <mailto:loa@pi.nu 
>> <mailto:loa@pi.nu>>
>>      > loa.pi.nu.@gmail.com <mailto:loa.pi.nu.@gmail.com>
>>     <mailto:loa.pi.nu.@gmail.com <mailto:loa.pi.nu.@gmail.com>>
>>      >
>>      >     _______________________________________________
>>      >     mpls mailing list -- mpls@ietf.org <mailto:mpls@ietf.org>
>>     <mailto:mpls@ietf.org <mailto:mpls@ietf.org>>
>>      >     To unsubscribe send an email to mpls-leave@ietf.org
>>     <mailto:mpls-leave@ietf.org> <mailto:mpls- <mailto:mpls->
>>      > leave@ietf.org <mailto:leave@ietf.org>>
>>      >
>>
>>     --     Loa Andersson
>>     Senior MPLS Expert
>>     Bronze Dragon Consulting
>>     loa@pi.nu <mailto:loa@pi.nu>
>>     loa.pi.nu.@gmail.com <mailto:loa.pi.nu.@gmail.com>
>>
>