[mpls] Re: 答复: Working Group Adoption Poll on draft-li-mpls-mna-entropy

Aijun Wang <wangaijun@tsinghua.org.cn> Fri, 11 October 2024 14:06 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
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 67C93C1840C7 for <mpls@ietfa.amsl.com>; Fri, 11 Oct 2024 07:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.012
X-Spam-Level:
X-Spam-Status: No, score=-1.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, 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_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 azH86s0AsNPQ for <mpls@ietfa.amsl.com>; Fri, 11 Oct 2024 07:06:29 -0700 (PDT)
Received: from mail-m49198.qiye.163.com (mail-m49198.qiye.163.com [45.254.49.198]) (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 1D465C16A128 for <mpls@ietf.org>; Fri, 11 Oct 2024 07:06:27 -0700 (PDT)
Received: from smtpclient.apple (unknown [5.180.77.214]) by smtp.qiye.163.com (Hmail) with ESMTP id 562ebc5; Fri, 11 Oct 2024 22:06:23 +0800 (GMT+08:00)
Content-Type: multipart/alternative; boundary="Apple-Mail-A0A7F857-BAF7-44CC-B1A1-E9A51A6E0F4D"
Content-Transfer-Encoding: 7bit
From: Aijun Wang <wangaijun@tsinghua.org.cn>
Mime-Version: 1.0 (1.0)
Date: Fri, 11 Oct 2024 22:06:11 +0800
Message-Id: <A2338A30-0DD5-4B96-A27E-44F735F5A08D@tsinghua.org.cn>
References: <9bd535c9-0d2f-4d73-8283-6b3a3326aeae@joelhalpern.com>
In-Reply-To: <9bd535c9-0d2f-4d73-8283-6b3a3326aeae@joelhalpern.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: iPhone Mail (21G93)
X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWS1ZQUlXWQ8JGhUIEh9ZQVkaTEodVhhPGhhMTRhNQx9LGlYeHw5VEwETFh oSFyQUDg9ZV1kYEgtZQVlOVUpDS1VMTFVJSk9ZV1kWGg8SFR0UWUFZT0tIVUpLSEpITUpVSktLVU pCS0tZBg++
X-HM-Tid: 0a927be6e8ad09c2kunm562ebc5
X-HM-MType: 10
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Kxg6Lyo6HTItHFYTOVFKEhg2 FC9PCgpVSlVKTElDTU5OTkNPSUNCVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlOVUpDS1VMTFVJSk9ZV1kIAVlBSklISUk3Bg++
Message-ID-Hash: 3PIM2S73G3QLFBP6ANOY6C7DIKU5HLNF
X-Message-ID-Hash: 3PIM2S73G3QLFBP6ANOY6C7DIKU5HLNF
X-MailFrom: wangaijun@tsinghua.org.cn
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
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [mpls] Re: 答复: Working Group Adoption Poll on draft-li-mpls-mna-entropy
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/mVBF-7xVS3wIwRAPDtncthbcL5g>
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>

Hi, Joel:

What’s my main concern is that the entropy function is not the key use case for the MNA based solution, there is also no any mention of such use case in https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-usecases-15" rel="nofollow">https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-usecases-15.

What’s the reason to adopt such MNA -based solution for one non-killer application(also not indispensable) to encourage the industry to implement, deployment of the new MNA based forward plane?


Aijun Wang
China Telecom

On Oct 11, 2024, at 21:38, Joel Halpern <jmh@joelhalpern.com> wrote:



It sounds like you consider that the use cases draft, which the working group approved for publication, is insufficient.  If so, it would have seemed appropriate for you to raise the objection in the WG to that draft.  I don't recall you doing so.  Did I miss it?

Yours,

Joel

On 10/11/2024 4:34 AM, Aijun Wang wrote:

Hi, Nic and WG:

 

Although this draft provide one solution to implement the entropy function, it is not the necessary and killer application for the MNA based solution.

If there is no other prominent function for MNA based architecture, what’s the reason to design the new architecture?

 

I would like the WG to focus firstly other prominent(if exists) functions that can utilize/exploit the flexibility of MNA based architecture.

From the POV of the operator, there is no impetus to put forward such new knob for the existing function(also considering the existing MPLS entropy label can fulfill its task perfectly)

 

I suggest the WG to stop adopt it as the WG document, and devote more energies to others fascinate proposals.

 

Best Regards

 

Aijun Wang

China Telecom

 

发件人: forwardingalgorithm@ietf.org [mailto:forwardingalgorithm@ietf.org] 代表 N.Leymann@telekom.de
发送时间: 2024101 22:04
收件人: mpls@ietf.org
抄送: mpls-chairs@ietf.org; draft-li-mpls-mna-entropy@ietf.org
主题: [mpls] Working Group Adoption Poll on draft-li-mpls-mna-entropy

 

Dear WG,

 

This email starts a two-week poll on adopting draft-li-mpls-mna-entropy as a MPLS working group document.

 

Please send your comments (support/not support) to the MPLS working group mailing list (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.

 

Currently, there are no IPR disclosure against this document. All the authors/contributors have stated on

the MPLS WG mailing list that they are unaware of any undisclosed IPRs that relates to this document.

 

This working group adoption poll ends October 16, 2024.

 

Regards,

 

Nic (as MPLS WG co-chair)


_______________________________________________
mpls mailing list -- mpls@ietf.org
To unsubscribe send an email to mpls-leave@ietf.org