IETF Logo Mail Archive

Re: Question about BCP 14 / RFC 8174

Nico Williams <nico@cryptonector.com> Tue, 26 August 2025 15:48 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 1BCDF59388D2 for <ietf@mail2.ietf.org>; Tue, 26 Aug 2025 08:48:06 -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 Xyu5jgj2JnFD for <ietf@mail2.ietf.org>; Tue, 26 Aug 2025 08:48:05 -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 7D58759388C8 for <ietf@ietf.org>; Tue, 26 Aug 2025 08:48:05 -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 BB7E62C45F2; Tue, 26 Aug 2025 15:48:04 +0000 (UTC)
Received: from pdx1-sub0-mail-a210.dreamhost.com (trex-blue-3.trex.outbound.svc.cluster.local [100.102.95.165]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 60C052C456A; Tue, 26 Aug 2025 15:48:04 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1756223284; a=rsa-sha256; cv=none; b=3RepyW+O9iCiKrburGAr43uNDErCTOXTkgDX2qobqhnuJk2asHQP7jZGRRkzuAgWRXo7kI vrrCvrpli/r4D2Trl6XLJHaBFeCTr13ZVtBS8ENLZBjk0Qj3S6cw4fqktRJHHdfHvZNKxe 7TCtRyJCC1rlKzVXGGfPwAQrWfU/PqDzmT09XXEmo04xDu+ePWYO5ETRR5CLYfClPI9CFv aLFUC1fRD405b5++Xqubl6RVro//35XrRotYmqhNJiC298NXgugTK8waW24daLvzHWsiof hMPxankIe7FJueqbzvyoxCtfyOwgNCBGFfmH8iwIne1WVpZ/Nr1hKjJqRDgdHA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1756223284; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=89/h5cPlQneNAx/yL06MmW8LGK020g6u7efvlGV98bE=; b=g5WOXCtPHYNeAkoMUtQtEFbA/N8IYo+Bde7Z94P8GvgsSsOCLV5YxTsN5tH/yWDNS6Zy6o UTan6EpPYtAOHTvC7ajAYBwK//M3rw/lCQiLRB0Xwm2aOfIOK9C9XToalV4b4dso1SW5ye Pu9c8lMT9txSDrb1ZNoPN/g4lpy+S9b7KcZyduJzcLRVq20fO0rdqBbcHgvqk1N7ncyg04 l+qN40Fch3a+vBloAM/Qlk09RoMgbUgvJH+wQ6GrWWHLA25FoXIOasIFLvAmJmCIV3goAQ jSNEe/7KRkkPkSsNoElVyFtqUCwJ+NxjEQ/HLwDydviddjPehR6Wa5KjTR9K6w==
ARC-Authentication-Results: i=1; rspamd-65f47dcb6-7tb8d; 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-Abiding-Vacuous: 760245977d341885_1756223284655_1867342737
X-MC-Loop-Signature: 1756223284654:2205097982
X-MC-Ingress-Time: 1756223284654
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.95.165 (trex/7.1.3); Tue, 26 Aug 2025 15:48:04 +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 4cBBrg5S3Nz2W; Tue, 26 Aug 2025 08:48:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1756223284; bh=89/h5cPlQneNAx/yL06MmW8LGK020g6u7efvlGV98bE=; h=Date:From:To:Cc:Subject:Content-Type:Content-Transfer-Encoding; b=aXk1E4ezDF+gTYuoEB2zXHla3XXgYVtJ+QKpPWdJEVOl6OPDn4z6ixdbqBmlhLPUn TVaCi96fuw1n94W6973epvtnXUKL1dKzU+OnCWYVXac8I2EDAfipSe1RenCm4I4DIj 6hg95ukPfCT1PxcTnFWK/PktkBDWygDNZYtA5VbBGjyrF2uddSUGjhzRS8mPLXv3B8 XM41UjDeIN0UMkey/icVmetT+cursvVI7le056aJEC9/FnLGPsyscwu+ERsP7eYwmq gUwuWgMnXwwQeZ1lPzSWEgd5k3AxBGGsGpy6n4PGs7UuCmIqGnFqMJJfASTLgBjqLK K0ICHYg3tlm5g==
Date: Tue, 26 Aug 2025 10:48:01 -0500
From: Nico Williams <nico@cryptonector.com>
To: "Salz, Rich" <rsalz@akamai.com>
Subject: Re: Question about BCP 14 / RFC 8174
Message-ID: <aK3XMWzrnJPFrI4m@ubby>
References: <aKzK5qdwLUHSa3JL@ubby> <878qj67dcq.fsf@josefsson.org> <MN2PR17MB4031F73336C43683553B84B9CD39A@MN2PR17MB4031.namprd17.prod.outlook.com> <87y0r6i1p7.fsf@josefsson.org> <MN2PR17MB4031065DFE92FEBB87A23E15CD39A@MN2PR17MB4031.namprd17.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <MN2PR17MB4031065DFE92FEBB87A23E15CD39A@MN2PR17MB4031.namprd17.prod.outlook.com>
Message-ID-Hash: ORQBJIOEMWBR4KOESCUXP7TMHXEMNUB5
X-Message-ID-Hash: ORQBJIOEMWBR4KOESCUXP7TMHXEMNUB5
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: Simon Josefsson <simon=40josefsson.org@dmarc.ietf.org>, "ietf@ietf.org" <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/DYwHpJQTPopSBMI7PjN3LQLR2q0>
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 02:50:22PM +0000, Salz, Rich wrote:
> > Including IAB, IRTF and other non-IETF bodies which also publish RFCs?
> 
> Only the IETF stream can publish standards-track docs, so maybe those keywords are less important? 

Well, that's.. funny because per Barry the intent was to not imply that
only Standards Track documents could use BCP 14.  We traded the
appearance of implication that BCP 14 is for standards track docs for
the appearance of implication that BCP 14 is for IETF docs only.

> > It wasn't clear which kind of definition of IETF was used in this text.
> > I guess the intent was to include these IETF-related entitites too.
> 
> I don’t think so. The IETF stream doesn’t make policy about other
> streams, it’s up to those streams to pick them up, in this case
> probably on a per-document basis.

Is there a rule somewhere that IETF documents (at least on the standards
track) MUST reference BCP 14?

Nico
--

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