[mpls] Re: Gunter Van de Velde's No Objection on draft-ietf-mpls-mna-hdr-18: (with COMMENT)
Adrian Farrel <adrian@olddog.co.uk> Fri, 30 January 2026 12:29 UTC
Return-Path: <adrian@olddog.co.uk>
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 685A9AF6C49C; Fri, 30 Jan 2026 04:29:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=olddog.co.uk
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 B3wnTG2zCNNe; Fri, 30 Jan 2026 04:29:48 -0800 (PST)
Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id C755BAF6C496; Fri, 30 Jan 2026 04:29:44 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.7/8.14.7) with ESMTP id 60UCTe61006902; Fri, 30 Jan 2026 12:29:40 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 854814604B; Fri, 30 Jan 2026 12:29:40 +0000 (GMT)
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 782384603D; Fri, 30 Jan 2026 12:29:40 +0000 (GMT)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS; Fri, 30 Jan 2026 12:29:40 +0000 (GMT)
Received: from LAPTOPK7AS653V (82-69-109-75.dsl.in-addr.zen.co.uk [82.69.109.75]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.7/8.14.7) with ESMTP id 60UCTd7t014695 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 30 Jan 2026 12:29:39 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Gunter Van de Velde' <gunter.van_de_velde@nokia.com>, 'The IESG' <iesg@ietf.org>
References: <176977442126.1914444.1280667825254290156@dt-datatracker-77f8b84995-z4hzn>
In-Reply-To: <176977442126.1914444.1280667825254290156@dt-datatracker-77f8b84995-z4hzn>
Date: Fri, 30 Jan 2026 12:29:38 -0000
Organization: Old Dog Consulting
Message-ID: <00ef01dc91e4$1a750580$4f5f1080$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKLm4BMTJXOHqu098c9xyWuPT8YmbQMjWtw
Content-Language: en-gb
X-Originating-IP: 82.69.109.75
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding; s= 20221128; bh=4qWxq1aNHBL9oJFNI8v6AGm1t/Y1f1kBmE1rZNWtlbM=; b=Bia +BEfhZpEIc9f1ftyCYO5rC5PYA2N5w7bHk3dts254wn/7MeWiPzDHdmO5QqSiQQz Jqm2Ze6HVF20I5gQ5MSIieEtanrveEL7nYWMgWGP1Rj9F5tJ01q7slCXCi0+oD6C lb8JD0M3idWvUBVn+mai5MP1JVqrSiU4+13A26Zy1ivxEPsfpCCjILqOL5fZAeTF 3aAbpc5TOCyAavhom3bPNzkSh9rbeJjSwwaPOrLRmU4/0+cOILnTN+jkLEHUQmjv OrNcq6CEQV2riJlRxWBGCyTQQphQ87WB2LJQ/EQgieVkANQMpoputEOAYiGzgJC9 apqsaAkbdkb+NQUaq6w==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1006-29464.005
X-TM-AS-Result: No--6.668-10.0-31-10
X-imss-scan-details: No--6.668-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1006-29464.005
X-TMASE-Result: 10--6.667800-10.000000
X-TMASE-MatchedRID: HXSqh3WYKfvxIbpQ8BhdbPHkpkyUphL91KDIlODIu+XG6KjwOvvPJF0Q TojKLQVyssXNVaazvgLqHK8Idq2A6cfdkIlEiI2kC8FMH3T6F77J5SXtoJPLyC196sn93sBvvjX dJjrklctanfi7p7YrsULIYTs8DylF1s1YQK1Ht0cqy6shOlK/48WaYx0jCOsOvsuGOPOyHAHpDI mdo+bLZeLNRz6Y86fZHWm5UoWAU14YB2fOueQzj4MbH85DUZXyOTej9KUDj5XH85pIf0QqWxvcx ZgTG+du3QfwsVk0UbtuRXh7bFKB7kOtDWPw/W5JjRz7B5LHmFeljfAyqJLojeOsT1GR0whjS4W/ MRhJ1X4=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Message-ID-Hash: RP6BZ2IQK53HWT7OB3X3FSAMWA7RIFDD
X-Message-ID-Hash: RP6BZ2IQK53HWT7OB3X3FSAMWA7RIFDD
X-MailFrom: adrian@olddog.co.uk
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: draft-ietf-mpls-mna-hdr@ietf.org, mpls-chairs@ietf.org, mpls@ietf.org, tsaad@cisco.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: adrian@olddog.co.uk
Subject: [mpls] Re: Gunter Van de Velde's No Objection on draft-ietf-mpls-mna-hdr-18: (with COMMENT)
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/9vP-KE0cTN5JrxFiz2WQq1UR8JQ>
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>
> # COMMENTS
> # ========
>
> 139 2.1. Requirements Language
> 140
> 141 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> 142 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> 143 document are to be interpreted as described in [RFC2119] [RFC8174]
> 144 when, and only when, they appear in all capitals, as shown here.
>
> GV> is there a reason why BCP 14 is not mentioned in the usual Requirement
> Language template?
Interesting question, Gunter.
Looks like idnits doesn't seem to mind about this.
But 8174 is clear that the form of words should be:
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
"MAY", and "OPTIONAL" in this document are to be interpreted as
described in BCP 14 [RFC2119] [RFC8174] when, and only when, they
appear in all capitals, as shown here.
While I believe the RFC Editor would fix this, I see no reason not to handle it in the updates after IESG review before the document is passed to the Editor.
Cheers,
Adrian
- [mpls] Gunter Van de Velde's No Objection on draf… Gunter Van de Velde via Datatracker
- [mpls] Re: Gunter Van de Velde's No Objection on … Adrian Farrel