Re: Question about BCP 14 / RFC 8174
Nico Williams <nico@cryptonector.com> Tue, 26 August 2025 15:44 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 C09EB5937B14 for <ietf@mail2.ietf.org>; Tue, 26 Aug 2025 08:44:15 -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_H3=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 onXfWm-VbCMF for <ietf@mail2.ietf.org>; Tue, 26 Aug 2025 08:44:15 -0700 (PDT)
Received: from serval.cherry.relay.mailchannels.net (serval.cherry.relay.mailchannels.net [23.83.223.163]) (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 EE2365937822 for <ietf@ietf.org>; Tue, 26 Aug 2025 08:43:49 -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 DB01B83030; Tue, 26 Aug 2025 15:43:48 +0000 (UTC)
Received: from pdx1-sub0-mail-a210.dreamhost.com (100-102-67-208.trex-nlb.outbound.svc.cluster.local [100.102.67.208]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 85B2483625; Tue, 26 Aug 2025 15:43:48 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1756223028; a=rsa-sha256; cv=none; b=3nSj+LVvd1dm7wvClqF2WnzwZhxQyx8aNdYOjJDtVlkrHNoOwu06G/WwonVJwsECxG5Vzc 61w8QBE1U+PtURhK33fOoFzqKp2vLTxnSFINhfr57gzDjGrthIseAYORXmT0rVT5e8qC2e 7VOc61U1MM8g/l+u8zfNjK7Lq5zPLfioQ4861ScSRd5kDCILlhet3BAL/+s3GTd72SRZKj UJBzBD4te4GaALFt6YxPgmGu7pj1ZDgAOQzE1U67zL+k8iylCwac6soNFGoXF4LNMqNklM 2s/ylIqJDMbjWboxydR1odCiW+ppMfFH4MtBMG12bRUPFk9i55Cq2fHR+ECCgg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1756223028; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:dkim-signature; bh=jGfgoAp3wY/zBXhIIUve8fKT3aaI/A0nnzjKTwzkTP4=; b=ZeAHBjhJpKQCmRc9EWEkMmqniqKBtm3ajAIcpqxLH25+78Pi0oWb0XdCMNpgHtmxgoWmou NEgtYQ8CS5s5jZeqRTWJfB5i0XQeXHY0BI8unwUAe19fiVtQ8wR6bFGHT8WGMFwvc0awrg TCCKTldmhwWXZQO9YYTl2t9eYQbMeLjk/psTOXpaddHMVuUSxKaubqP0Sbt5ugoN7tXIZ/ Z5PCa6PhRLDGay2Qkg6iPvPftihRhO+F33Bq2Ewg5pXF+JIQV1V7/HbHp7VkUN/JwCJrYa sn5RM/C1OHRsLoVJjiDO23kXqdVMwEnkEtMhjvkDgmkQugU4VQ/gOGs6DefL2w==
ARC-Authentication-Results: i=1; rspamd-65f47dcb6-ckbz6; 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-Tangy-Shelf: 0bd0559649677f2f_1756223028785_1359178118
X-MC-Loop-Signature: 1756223028785:2016982639
X-MC-Ingress-Time: 1756223028785
Received: from pdx1-sub0-mail-a210.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.102.67.208 (trex/7.1.3); Tue, 26 Aug 2025 15:43:48 +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-a210.dreamhost.com (Postfix) with ESMTPSA id 4cBBlm067Zz52; Tue, 26 Aug 2025 08:43:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1756223028; bh=jGfgoAp3wY/zBXhIIUve8fKT3aaI/A0nnzjKTwzkTP4=; h=Date:From:To:Cc:Subject:Content-Type; b=ohr4Xenyb9SsxvWvEiQnLg56BdikX6I3myV4HYAM/gqSM+i5ToBc8cmJUwddFyJYA 0llp7B1oW5XW0go5DuRvXXLkDmPT6nqvnSnQje/IDBekL/ZMGG9Hjf/Wn2Dc6G1q8j ByqpfVEAniH50UHl6JX6+Y6UNiEIFHjGJs7YU9lPbOUZ2mjvpMj205LYnlPfPdZ+S3 AUF1EWQFzLM8HHgWkxUho1zQVSp3JsnKUUcEuPFVbm20QPTqpUnpCKYFuwLx7d/rNL bnTuWwF7izvubauEC3yBCA46Y+3y1yRo68GowSKr9Bi65sdAz3LNmREDlfuE4C6EPq bp2jOqLtLFIzw==
Date: Tue, 26 Aug 2025 10:43:45 -0500
From: Nico Williams <nico@cryptonector.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Question about BCP 14 / RFC 8174
Message-ID: <aK3WMbyBzFaErK5H@ubby>
References: <aKzK5qdwLUHSa3JL@ubby> <CAC4RtVASn123qUSuFZg50wL4Nrjebz=QMf5AU=jeZLgQd5fsDg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAC4RtVASn123qUSuFZg50wL4Nrjebz=QMf5AU=jeZLgQd5fsDg@mail.gmail.com>
Message-ID-Hash: DKMVPKTFXBPPJHMBC6RDFL5P4EV54LUI
X-Message-ID-Hash: DKMVPKTFXBPPJHMBC6RDFL5P4EV54LUI
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
CC: ietf@ietf.org
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/gS26nxCYE4WM-QfZMQwsHjykZ0E>
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>
On Tue, Aug 26, 2025 at 11:17:55AM -0400, Barry Leiba wrote: > You're not noticing that the OLD text also talks only about IETF > documents by saying "many standards track documents". The NEW text is > intentionally broader, including all IETF documents -- Informational > and Experimental as well. That's because we've realized over time > that it's useful to include BCP 14 key words in those also, not just > in standards. Thanks. But that "many standards track documents" certainly did not imply that others couldn't use BCP 14, and obviously many did. It's bit weird for an FYI to have normative language, but many FYIs document what running code does that its authors or the IETF did not want on the Standards Track, thus using BCP 14 in such FYIs is perfectly natural (e.g., RFC 4559), though one might question why they were FYIs. > It was not intentional to say that *only* IETF documents use these. > But we're only writing, here, about and for the IETF, and BCP 14 only > explicitly applies to the IETF. As Simon asks, what about IAB, IRTF, and other non-IETF RFC streams? Not that I think we need to update BCP 14 again. Of all the things that need attention I think BCP 14 is at the bottom of the list. I'm not even sure how to phrase this better. At any rate, you've satisfied my curiosity. Nico --
- Question about BCP 14 / RFC 8174 Nico Williams
- Re: Question about BCP 14 / RFC 8174 Simon Josefsson
- Re: Question about BCP 14 / RFC 8174 Salz, Rich
- Re: Question about BCP 14 / RFC 8174 Barry Leiba
- Re: Question about BCP 14 / RFC 8174 Brian E Carpenter
- Re: Question about BCP 14 / RFC 8174 Nico Williams
- Re: Question about BCP 14 / RFC 8174 Nico Williams
- Re: Question about BCP 14 / RFC 8174 Simon Josefsson
- Re: Question about BCP 14 / RFC 8174 Salz, Rich
- Re: Question about BCP 14 / RFC 8174 Nico Williams
- Re: Question about BCP 14 / RFC 8174 Salz, Rich
- Re: Question about BCP 14 / RFC 8174 John C Klensin
- Re: Question about BCP 14 / RFC 8174 Toerless Eckert
- Re: Question about BCP 14 / RFC 8174 Brian E Carpenter
- Re: Question about BCP 14 / RFC 8174 John C Klensin
- Re: Question about BCP 14 / RFC 8174 Carsten Bormann
- Re: Question about BCP 14 / RFC 8174 Eric Vyncke (evyncke)
- Re: Question about BCP 14 / RFC 8174 Rob Wilton (rwilton)
- Re: Question about BCP 14 / RFC 8174 John C Klensin
- Re: Question about BCP 14 / RFC 8174 Brian E Carpenter
- Re: Question about BCP 14 / RFC 8174 Christian Huitema
- Re: Question about BCP 14 / RFC 8174 Brian E Carpenter
- Re: Question about BCP 14 / RFC 8174 Joseph Potvin
- Re: Question about BCP 14 / RFC 8174 Michael Richardson
- Re: Question about BCP 14 / RFC 8174 Rob Wilton (rwilton)
- Re: Question about BCP 14 / RFC 8174 Christian Huitema
- Re: Question about BCP 14 / RFC 8174 John C Klensin
- Re: Question about BCP 14 / RFC 8174 Michael Richardson
- Re: Question about BCP 14 / RFC 8174 Carsten Bormann
- Towards Automated Discovery of Technical Standard… Joseph Potvin