IETF Logo Mail Archive

Question about BCP 14 / RFC 8174

Nico Williams <nico@cryptonector.com> Mon, 25 August 2025 20:43 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 9B56F58CE833 for <ietf@mail2.ietf.org>; Mon, 25 Aug 2025 13:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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=cryptonector.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 QReG_c-BKnLl for <ietf@mail2.ietf.org>; Mon, 25 Aug 2025 13:43:23 -0700 (PDT)
Received: from silver.cherry.relay.mailchannels.net (silver.cherry.relay.mailchannels.net [23.83.223.166]) (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 2185D58CE82E for <ietf@ietf.org>; Mon, 25 Aug 2025 13:43:23 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 1B5721C4505; Mon, 25 Aug 2025 20:43:22 +0000 (UTC)
Received: from pdx1-sub0-mail-a315.dreamhost.com (100-102-63-62.trex-nlb.outbound.svc.cluster.local [100.102.63.62]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id B89681C4473; Mon, 25 Aug 2025 20:43:21 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1756154601; a=rsa-sha256; cv=none; b=snWpJA2uaUFxuHGMkZVaPO4uAZbPBFS/lw3Y+p9LfubuCEd1I1kMivIBK6OXDw+WORGh6W UjGZa0mV4/nG03bp1R8irKFadXr1nTEGAwOXNC75o1cGnvklNKVh6To+Sg6XcIVciLK4Qm d/YTD8wHfvSMWOQx/2huvLVGPgeYHaAuR8VqDeb77smysHlV4yXOxy/8OPTPupVMlkq8mf iEansvpJaIVHlM9ZfyE1HtYItUUn+08vsPOD13xpoOECaf+/Ak3JxV9Kd4jlVHQFLeWMKp y3p7FzzojfViMOnKeYMVWipEIL2M7zMIXfIJTnSPJhKPLHAITwj/WoEkazTrLQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1756154601; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: dkim-signature; bh=H1cv44zpiN4f0bmCv3beeHIpsCg5cVJJW1hEGQS9+lw=; b=h88wmLuQRpdd+5V6RAGM6dq42usx7DEZbjIwh4ap8Vr49dzk00hvWNL9yKML4zG8uKRB4j WrZ7eoGnkAdXqfupGdr0jML7sU2s0xvn2h1c0LdBPGPbpaiP+IBx6uLXy6WKCOZk86uhSn yRtrCsUCQzGITsAS+exNCd+82y7PYFPQ1g8LL4HI9R3J6W+htklgTsMnyXHWkrZRwa5Dg6 NWZf8tvaiOgzD42ic94QdICnP7EPu0qJRvXXvgifnfSRgI7QNxQBepPi4RIkl036RoQnnY iasZx68ZW+rOfVyP7h51XUy9Wa2tUMKObX8S5j8dsBsSRnclpkRh1w2BTjiXUQ==
ARC-Authentication-Results: i=1; rspamd-b7d944dc4-zlhm4; auth=pass smtp.auth=dreamhost smtp.mailfrom=nico@cryptonector.com
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Keen-Stop: 02dca1a13d55e8fd_1756154601958_1785709785
X-MC-Loop-Signature: 1756154601958:209368669
X-MC-Ingress-Time: 1756154601958
Received: from pdx1-sub0-mail-a315.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.102.63.62 (trex/7.1.3); Mon, 25 Aug 2025 20:43:21 +0000
Received: from ubby (syn-075-081-095-064.res.spectrum.com [75.81.95.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a315.dreamhost.com (Postfix) with ESMTPSA id 4c9jRs1bPyzY1; Mon, 25 Aug 2025 13:43:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1756154601; bh=H1cv44zpiN4f0bmCv3beeHIpsCg5cVJJW1hEGQS9+lw=; h=Date:From:To:Subject:Content-Type; b=AUCGk2n05U/wljzzOzOG8mRbaVatR8LJ4zD0X8014xWjVmXhopm+PCog/rjoERoId K3P2rLbfytaPuahlT6vM2CxFaSyISxfbARn7axcos0KeqmHDU8vTflY/zjDpMOD74a 93pJgs7+If5jC+yYHluKjA10aMt48+KxOvQj3aA3AX/qiEwhqGcchv/3mzqwT/jAkl OJ2fmPTkrhCNHNPR01dWLBC7SRquSDaif2zZ6Qi7Ok+42xwC33VcLFMEz9vvtMgqMz gS/QoG37S1l7o4qkr3Nzx5zUSe9agTZc7izohjTzIEuWjs90OoaBzWVyzHaSfzZu7K eeFcBWti6E0Cw==
Date: Mon, 25 Aug 2025 15:43:18 -0500
From: Nico Williams <nico@cryptonector.com>
To: ietf@ietf.org
Subject: Question about BCP 14 / RFC 8174
Message-ID: <aKzK5qdwLUHSa3JL@ubby>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Message-ID-Hash: UOWASYCUIYYFTBFEO3TYLLUJVT7QUJ3Z
X-Message-ID-Hash: UOWASYCUIYYFTBFEO3TYLLUJVT7QUJ3Z
X-MailFrom: nico@cryptonector.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jfLnTaEQscJQ4WgHE0KMTdNC2Qo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

I guess I've been hiding under a rock or something and missed RFC 8174.
I was... surprised to see that the NEW text specifically refers to "many
IETF documents" considering that many non-IETF documents also make use
of BCP 14 terminology.

Of course anyone making use of BCP 14 outside IETF documents can just
either not mind or elide the IETF specificity, so maybe "who cares".
But I find this change surprising, and odd.

Nico
--

v2.34.0 | Report a Bug | By Email | System Status