IETF Logo Mail Archive

Re: Question about BCP 14 / RFC 8174

Nico Williams <nico@cryptonector.com> Tue, 26 August 2025 14:46 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 A1291592A5AF for <ietf@mail2.ietf.org>; Tue, 26 Aug 2025 07:46:30 -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 VLki2NrMHp1Y for <ietf@mail2.ietf.org>; Tue, 26 Aug 2025 07:46:30 -0700 (PDT)
Received: from rusty.tulip.relay.mailchannels.net (rusty.tulip.relay.mailchannels.net [23.83.218.252]) (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 F38B4592A5A9 for <ietf@ietf.org>; Tue, 26 Aug 2025 07:46:29 -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 88B0718233C; Tue, 26 Aug 2025 14:46:28 +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 1B4CC182240; Tue, 26 Aug 2025 14:46:28 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1756219588; a=rsa-sha256; cv=none; b=sD/anK5OvPoYQpMO+DSidf7Ibl8u0znEB2BbjW5uR5ePTwucqSzgKriSFxO5ksDcxuWFj+ tqpXBoSbDOHlsQuDV26mfCZrEfu4DaMhLZf75TMHIM47hscBKmlkozlhhVZJp5jNeaHSoF IAT/7C/zaP5S3PMS4snu/ma12mnR+pLHgep/r78BfZX0DHfu9veprMZGPdM7FjhAZXAK62 r8oacbS+/fWqxdRcep0rf3qOqz/sSrwUhoY5F4tljxGkjcAltn7sr4FFBtv4hCkjf84BWM R9r14rR95KwuD5pht7xRm9FWS8irxZBEmOzWe/MXknny9Yp7cDnx74eZhKxm2g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1756219588; 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=7Mcpbh2OOCZ28x7zR9ZbSAC4u8fcxN8VJkvvZaG+zlQ=; b=cYxiMGm4COembFUVEx63hFNg7MPjmCBgeVVdEFKoTLGawrQ9xmy4vOCQUBEvWg76ROUpAk /oHNYqUm23q7i8G/Q5mLZC8gk5R/oOPAZIyILiFiE3VqZxkAp1uSP3/VQH8x3EMsuncRmS PoLweJhbpyXBDHi7Rvc9dCPiyaf/B5Zip7h5GiWMStyVvGjShNu9258pqXw15LU6aCqyNr ofM7jXUspWuRWZnE9BXuuqh1cyCmFT9cjZXq5569STPP2VkL0DzM8mTNbQIpAZG6Pt6Y2v P1steoKm/HM+SqWuMO4fEx1dV/6BG9qMUq1fKr8VQWFXqQxkTMvnv4jNoKUO/w==
ARC-Authentication-Results: i=1; rspamd-b7d944dc4-xdkpg; 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-Daffy-Coil: 095684416ea1eb17_1756219588368_3025237818
X-MC-Loop-Signature: 1756219588368:278856553
X-MC-Ingress-Time: 1756219588368
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 14:46:28 +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 4cB9Tb2qcDz2W; Tue, 26 Aug 2025 07:46:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1756219587; bh=7Mcpbh2OOCZ28x7zR9ZbSAC4u8fcxN8VJkvvZaG+zlQ=; h=Date:From:To:Cc:Subject:Content-Type:Content-Transfer-Encoding; b=RMKJz/JWR5SezZWV5a38EBd8bB+W492RKnusT+ayiUAm0cfZ8dz8rlC3Y7GemIKCL 1/DNJXK2KJuj5TjytRizE4H6OBVLRPPM7A+VhbKtpBbvIMXn9EBzEDxRmvLmI0JnY+ r/jJSw4kL8ui+Kv4FobtfPxzP8GUSzra/pZeEtZpqivgJPQuSG8sTG14RQVn8zwxZ5 rJFKkPXvxS0EdIjl2sJvGKxBB3gTgqidzinqgNM0mUtwqIUPpYRH93F9GYZ3sLz6lR nLJ2/v+V0pRW869XeIIcF+9HffS73PaFaTZFMoNIKCXk5ODb5XYKZJyM2WiQivhJCs RYbNLRcJUNcXg==
Date: Tue, 26 Aug 2025 09:46:25 -0500
From: Nico Williams <nico@cryptonector.com>
To: "Salz, Rich" <rsalz@akamai.com>
Subject: Re: Question about BCP 14 / RFC 8174
Message-ID: <aK3IwX6lPGCtX8gU@ubby>
References: <aKzK5qdwLUHSa3JL@ubby> <878qj67dcq.fsf@josefsson.org> <MN2PR17MB4031F73336C43683553B84B9CD39A@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: <MN2PR17MB4031F73336C43683553B84B9CD39A@MN2PR17MB4031.namprd17.prod.outlook.com>
Message-ID-Hash: PPVDQZI4F5OLNDLDWWMYDRAHDHKFPPJK
X-Message-ID-Hash: PPVDQZI4F5OLNDLDWWMYDRAHDHKFPPJK
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>, barryleiba@computer.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/hFeYji4YAL8aXAJECWPA6EANpag>
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 01:08:00PM +0000, Salz, Rich wrote:
> * Perhaps the restriction to IETF-only was unintentional.
> 
> No, it was almost definitely intentional. If other organizations want
> to pick up BCP 14 that’s for them to decide.

Almost definitely?  I guess we'd better ask the author (cc'ed).  Or dig
through the email archives.

Obviously other orgs/individuals can quote everything they want except
that bit.  But it does seem weirder that we don't acknowledge use
outside IETF than that there is use outside the IETF.  It's not like BCP
14 is terribly controversial and others who want to use it need to
fine-tune it for their needs.

Nico
--

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