Re: [mpls] A question about the benefit of not using ISD MNA

Stewart Bryant <stewart.bryant@gmail.com> Tue, 27 February 2024 07:14 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 1CA8BC165518; Mon, 26 Feb 2024 23:14:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.201
X-Spam-Level:
X-Spam-Status: No, score=-6.201 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, 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 Twr1vshvifO2; Mon, 26 Feb 2024 23:13:58 -0800 (PST)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 05BD7C157930; Mon, 26 Feb 2024 23:13:57 -0800 (PST)
Received: by mail-wm1-x334.google.com with SMTP id 5b1f17b1804b1-412a9e9c776so4077005e9.0; Mon, 26 Feb 2024 23:13:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709018035; x=1709622835; darn=ietf.org; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc:subject:date :message-id:reply-to; bh=LRfQcTe0M5XvvEQT/LSla6n2X403Ev5DfxpFqfbV+UU=; b=fe5IgB941G2BqW1eBoMuD8eBQgu16ppDrxMtMV7mbw0M4bzb+akLrY57EGDvNoqSt0 YML6KS/76TRFU3JIIWQX6Qq8qQ0Kq6eAt98zky7XSYlTdFL0K0s02vfzMTPL/DJkggid lhr6m2J0Yseb8jCTMkZKBLdDi2u9AALKcAzwI4DTE63qNAtLJ7PPXmOeedAZGmBFyOls SsMxnNz7xkj1A7nSy3WxXMYOxVSPRPXCoRQfbiDLIGk1oO3196HXKotblVLBfYTnK1zQ ZhR8esv554U9fo5NzlasG1QS8RpyLKp7HhFj+r1xwAkFXCI1OZhcqHNk7B0huBnBq/PV t9lA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709018035; x=1709622835; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=LRfQcTe0M5XvvEQT/LSla6n2X403Ev5DfxpFqfbV+UU=; b=Uu/Sn2Tuv8uEiOGfUIT8YirF8sZYy5j2z1N62bXC60tAdMYTime/r99RPRgR9Wu4B0 TpRSeYegTUFjqJ9AmdFWa+Ba7a5PoEs6ccb0AKbLqp+OGyr7u/nMRn4bBlPbKI5GW4gK voHaBUO/vcqya1TWHGfzHOBQd5eIjPRN0yWs7Z4DzL8s3qlzPh2eE1b2391Ej33EYzMe bfAKXTEpzpPjzkptgC8rxjXl1VfjT7bZGMV4zjm0tuMjQcb7gEOyJTb8rYRwyoITgtD/ aMzqvyCkUY3dWmGkexAp9VBDkuz/7UXdfuP7uqX57CekRgaCn/uHrxG+AwtEZL3Hm2n2 EgTg==
X-Forwarded-Encrypted: i=1; AJvYcCUnqXodMTeYddvUB6I+KaiLVN0A65BREU+OEwiJQKzsLBIhWWs73XZNiaaE6ga08pUGAXXuAVMBswZjUBif3BpYUw8girv1S5SKQ66IINrAlcZEyXW7G6dHGm2NpPDCszUzqwdG5PgTFnbxAtfnkTv1qwRdMfdmqI9Mt4N6dWgJ8AMCfiRe
X-Gm-Message-State: AOJu0Yx5qlhfVtyYxBqPJ+zIq/7rkhEKl5DypUSdrtB/fs5qNMmVHUJn GsjT2OmNFpbhmJrTnHimCQ2iCOgDP/XIkNLTmAKmM7ReUaNbaeIm7BkVrJii
X-Google-Smtp-Source: AGHT+IGXSJW2MLTUGXa8gohSuht8ZF0jwL3Il2ZEZsiQM2+AJRLWCQCRofF20AU85lw8q0EWynsnWg==
X-Received: by 2002:a05:600c:3503:b0:412:ae2f:e9fe with SMTP id h3-20020a05600c350300b00412ae2fe9femr436453wmq.4.1709018035164; Mon, 26 Feb 2024 23:13:55 -0800 (PST)
Received: from smtpclient.apple ([2a02:8012:7161:0:cd5a:a1be:1f3a:17cb]) by smtp.gmail.com with ESMTPSA id jn11-20020a05600c6b0b00b00412ae4b45b3sm551145wmb.30.2024.02.26.23.13.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 26 Feb 2024 23:13:54 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-D5A04B5B-1461-49ED-9326-1A753A49E55F"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <CA+RyBmXSRycFYNMPCQfAH0JvUrefsKzy3aB13qMSRy0T_jMRrw@mail.gmail.com>
Date: Tue, 27 Feb 2024 07:13:43 +0000
Cc: xiao.min2@zte.com.cn, draft-ietf-mpls-inband-pm-encapsulation@ietf.org, mpls-chairs@ietf.org, mpls@ietf.org
Message-Id: <F2FCE635-4B5C-467E-859F-FBA56221BF13@gmail.com>
References: <CA+RyBmXSRycFYNMPCQfAH0JvUrefsKzy3aB13qMSRy0T_jMRrw@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
X-Mailer: iPad Mail (21D61)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/c6SwWavX-CmNujnSkMKEOSyecYg>
Subject: Re: [mpls] A question about the benefit of not using ISD MNA
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: Tue, 27 Feb 2024 07:14:03 -0000

Q

On 26 Feb 2024, at 17:39, Greg Mirsky <gregimirsky@gmail.com> wrote:


Hi Xiao Min,
thank you for remaining about the history of this work, but my question was a bit more about the technical merits of two solutions. AFAICS, the MPLS Network Action is the mechanism for enhancing MPLS capabilities (including the signaling of entropy information). I don't see any benefit of having two ways of realizing the same functionality, especially when a better solution is already in a quite advanced state of being finalized. If the WG decides to recognize an earlier experimental work that led to a better technical solution, then it can consider document track other than Standard.

Regards,

I am not sure about MNA, or for that matter this draft when it comes down to simple universal deployment.

The thing that took us down the SFL path so many years ago was that pretty much any router can count the number of times it received a particular label value as part of its existing forwarding functionality.

That does not apply to MNA and I am not it applies to this proposal.

The downside of SFL is that you need to do control plane work to expect the label, but in all PM applications you need to coordinate the endpoints to make the measurement, and that means a control plane type of action.

Stewart


Sent from my iPad




On Mon, Feb 26, 2024 at 12:35 AM <xiao.min2@zte.com.cn> wrote:

Many thanks Adrian!


Dear Greg,

Please also note that Weiqiang's email [1] reflects the authors' view.


Best Regards,

Xiao Min


[1] https://mailarchive.ietf.org/arch/msg/mpls/S4a5kbmBsDmHEcKhF0lsVO_0kSo/" target="_blank" rel="nofollow">https://mailarchive.ietf.org/arch/msg/mpls/S4a5kbmBsDmHEcKhF0lsVO_0kSo/" target="_blank" rel="nofollow">https://mailarchive.ietf.org/arch/msg/mpls/S4a5kbmBsDmHEcKhF0lsVO_0kSo/

Original
From: AdrianFarrel <adrian@olddog.co.uk>
To: 'Greg Mirsky' <gregimirsky@gmail.com>;'mpls' <mpls@ietf.org>;
Date: 2024年02月25日 01:22
Subject: RE: [mpls] A question about the benefit of not using ISD MNA

For clarity for those following this thread, it applies to draft-ietf-mpls-inband-pm-encapsulation

 

The chairs discussed this point with the authors. There are several points to consider…

 

  1. Per section 8, there are some existing and interoperable implementations.

  2. If MNA was available today, it seems that it would be easier to direct the authors to use it.

  3. Two of the lead authors are aware of MNA and working with you on a draft to use MNA for exactly this function (draft-cx-mpls-mna-inband-pm).

  4. At some time in the future, the MNA approach could possibly supersede the approach in this draft.

 

So usual questions for the work group to think about at or around working group last call would be:

  • Are there implementations?

  • Is there are body of support?

  • Is there anything broken in the current solution?

  • Does the current solutions predicate against developing an alternative solution?

  • Is this a case where the market could decide?

  • Does anyone find the patents disclosed and their license terms such that an alternative solution should be developed? (Possibly worth checking whether that IPR would also apply to draft-cx-mpls-mna-inband-pm.)

 

The authors, of course, will want to respond to your question themselves.

 

Cheers,

Adrian

 

 

From: mpls <mpls-bounces@ietf.org> On Behalf Of Greg Mirsky
Sent: 24 February 2024 01:11
To: draft-ietf-mpls-inband-pm-encapsulation@ietf.org; mpls <mpls@ietf.org>; MPLS Working Group <mpls-chairs@ietf.org>
Subject: [mpls] A question about the benefit of not using ISD MNA

 

Dear Authors,

I've read the draft and I have a question:

What benefits do you see to use the proposed in your draft solution instead of using MPLS Network Action In-Stack Data approach?

I thought about it and, frankly, I don't have an answer. Thank you for your consideration.

 

Regards,

Greg


_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls