[mpls] Re: 答复: Working Group Last Call on draft-ietf-mpls-mna-hdr (2nd WG call)

Tony Li <tony1athome@gmail.com> Mon, 14 October 2024 02:32 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 1165AC15109A; Sun, 13 Oct 2024 19:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 6YTV4yi1-6AX; Sun, 13 Oct 2024 19:32:38 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 A47A7C15107C; Sun, 13 Oct 2024 19:32:38 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id d9443c01a7336-20c805a0753so30461235ad.0; Sun, 13 Oct 2024 19:32:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728873157; x=1729477957; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=pSAg6E/OJKCaHpxsA/j97tZj3q06mIsEDWKNWdn/Uuc=; b=UC1M6AieWHqphhoQe7nLXchRRGv76XQM3sultM/umGDavxuwCp1xlVM2QW2ItOndG3 +6dKIN3oJu9bg9cXpw6Qm1212KPrIWvd1VgdCPqPS+RUS1ywtf+silR17neZQU7KqexQ 2QZ3XGRGclIMwIJ3MtipkfNOHMBslIFdk/mabErNC/LD6Uv+A+m127pUKPMintnkHI+8 krfJQ+Xflh/ia1yiKB+ImqAulWyzYXEh+YdU/wGAXb0IihZB0Oo4hiIfsHF6qYj54Dl0 i/2KBqsgIxC9c81VBlOeMwfHQgeEYw8SJlokkcAGkL1EyPEYNEBtaODCUYmgVh8jcip0 ivGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728873157; x=1729477957; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=pSAg6E/OJKCaHpxsA/j97tZj3q06mIsEDWKNWdn/Uuc=; b=TOxDz30qsazG1FQGMBZFydXCNtzqHtnNS9CJuOt81HDCmEFr9WB+kP09ADclmr3Q7q RbVeHSdymxua7YoFiZiIzoPrpMQubcAZkax61k6f/WmUhQhwvY2BXjbGt5p6PiE/Iq3p JCqhkaBv0AK/082n7a+RVbvudSxIGyeSH8WdnA3w8XBM5OUda+RqjS6ycrrJLaw2+ao2 xP+Q+DegX6Bw8s2xN7b/ZQ86BVXcJ0iieufEELl4PoifB7TrjJ4uLP0TtKzNpjo6Co/L 584BtvuKdON4+3xNHf6Ol5z8I74WTCPHdff2pX2dvQfGIcXglNrb/iaGZG2ts2eSvRHx VQqA==
X-Forwarded-Encrypted: i=1; AJvYcCW2Heeoiy/3D/gv/z18ncoiKIuQoqMin6g4MpoIlKPT6mm2D/6L2+UMsGImkKrat3BPThPrpIAJTyWUI3g=@ietf.org, AJvYcCWKWt8hJEyT0ygxJuYg8u0BRP2HtzvF3UlsWjem1G5sxos0GK5BC0vaHuz6+pk+OfAhNXaMnQ==@ietf.org, AJvYcCWwuMtZoGahW7FccsOHRlZAOeLxICeVZPGRQE9dTXPdUDp3IXP43fT/Zh3kpWNxJn6/5Va7nMu73OrxakPP+DatQHl81ixb1w==@ietf.org
X-Gm-Message-State: AOJu0YwpuwZMWfatS89WIlDKlHb8fZwcW2HnEMr9RGjTZzfgr1hp2XJ7 h1R6qN64V7YBJT5keR1/raKhM2PE2X/mFbk/NFzvgoURSunZbp2w5QxsCw==
X-Google-Smtp-Source: AGHT+IEancKP9yeeJd5dC/gRh3/SWU6Yq/OY/c2+dVwZFRR4pNpBQ69IDtZqAs2dpWdc1fuO2UIQWA==
X-Received: by 2002:a17:90b:3757:b0:2c9:9658:d704 with SMTP id 98e67ed59e1d1-2e2f0df9cb7mr10407227a91.40.1728873157502; Sun, 13 Oct 2024 19:32:37 -0700 (PDT)
Received: from smtpclient.apple (192-184-144-109.fiber.dynamic.sonic.net. [192.184.144.109]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2e304095794sm5146070a91.15.2024.10.13.19.32.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 13 Oct 2024 19:32:37 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Tony Li <tony1athome@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 13 Oct 2024 19:32:26 -0700
Message-Id: <AE651102-E37A-44B4-BF06-A14DEC915C6C@gmail.com>
References: <1de712e7-1408-4ec1-bc55-dffaa6558182@pi.nu>
In-Reply-To: <1de712e7-1408-4ec1-bc55-dffaa6558182@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: iPad Mail (20H350)
Message-ID-Hash: AC2CLQVEDU743455A7KIFOSIJ65EN5K6
X-Message-ID-Hash: AC2CLQVEDU743455A7KIFOSIJ65EN5K6
X-MailFrom: tony1athome@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: mpls@ietf.org, MPLS Working Chairs <mpls-chairs@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/5SnJJ2A5PpXcZt2dK-WTD6bErk0>
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>

[WG chair hat: off]

Hi Loa,

> I agree that it is important to take the input we can get from implementations. I'm quite surprised by the perceived resistance for the WG chair that has spoken up on this. Taking the lessons we can from existing implementations has been there for MPLS Standard Track RFCs, since the start.

I think it’s a poor idea because I’ve sat through many hardware design meetings where someone raises the question of whether something is ready to consider for implementation. The hardware folks inevitably feel that something has not reached RFC status, then it is still in flux and not ready for hardware implementation.

Thus, an implementation mandate would create an unsolvable chicken-and-egg problem whereby we could not go to RFC without hardware and we could not get hardware without an RFC.

Thus, my concern is that requiring implementation experience is effectively ensuring that no progress can be made.

> There is one more thing, I've said several times. The P-flag and the PSD Present Op Code and the indicating the offset are by definition ISD, and should go in the ISD draft.
> 
> On the people supporting progressing the draft-ietf-mpls-mna-hdr, say that already today we know how the presence of PSD should be specified, so based on their arguments I see no  reason to wait.

Again, we have no justification for implementing PSD.  Until that’s presented, adding PSD indications to the ISD header is premature.

If there is truly justification for PSD, then members of the WG should simply put it on the table. The fact that they have not done so strongly suggests that it simply does not exist.

Regards,
Tony