IETF Logo Mail Archive

Re: Question about BCP 14 / RFC 8174

Simon Josefsson <simon@josefsson.org> Tue, 26 August 2025 14:47 UTC

Return-Path: <simon@josefsson.org>
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 832E1592AFD7; Tue, 26 Aug 2025 07:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.401
X-Spam-Level:
X-Spam-Status: No, score=-4.401 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=josefsson.org header.b="5mU3Nk4r"; dkim=pass (2736-bit key) header.d=josefsson.org header.b="aN3MQ9G1"
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 8mCrGiMtoSWu; Tue, 26 Aug 2025 07:47:38 -0700 (PDT)
Received: from uggla.sjd.se (uggla.sjd.se [IPv6:2001:9b1:8633::107]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 65059592ACA7; Tue, 26 Aug 2025 07:47:08 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; q=dns/txt; c=relaxed/relaxed; d=josefsson.org; s=ed2303; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=cX5CeWpMuP1TaYSuYqfvFqO7QKw+GIK8I5tnHH0//Z4=; t=1756219624; x=1757429224; b=5mU3Nk4rIysnvvNcBm0yepBVsGXELs5Gp1cYoirKEDv1jcMAPPK7xIJrWL/aP6gekTroJlgdRPH YqzutaTEFDg==;
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=josefsson.org; s=rsa2303; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=cX5CeWpMuP1TaYSuYqfvFqO7QKw+GIK8I5tnHH0//Z4=; t=1756219624; x=1757429224; b=aN3MQ9G1uwXxSV3eR+YXkBiLduPaO2Yjk/o+STSNW/F04CsTHtq+NoAGR5PAOP3GcXYSIaJLPPX fCSGqBJvR3S6jXthL/srcbjaLZYg6wlnEeKvdvKXEsaobaSVA1ehwBKNxK8KlCLVdwTvfj2sNCeOf XOZDG3RS4WcpEqR251pXzs7sZW2BA7SKvNCUpVGru7Vhbl1VIWSD27J7Y0jzg0TkpkPOvvaBFoImz zwFJVyZAh1xDDIxoseN6mxNhkzrQbml2IiD22dkUFPZhzCQvrMq3yJHuvBmi+QX3ex1G0Dodf7vBh VCz65P2E2CgPKEpd4kSWhkpduEN3yqmqi8hH/ZaNKrTGACxkxg9YdCUR0L0dzzkAnxZY5jFJKJ0FT y5Oh9paKZzNayodCH1Q5bN5Hn1AQV6jv66e6RXfkYNDlBSHUhrZzBDmj2iDcNUjnG2ac4j9xj;
Received: from h-178-174-130-130.a498.priv.bahnhof.se ([178.174.130.130]:40104 helo=kaka) by uggla.sjd.se with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <simon@josefsson.org>) id 1uquwx-002E0G-7Q; Tue, 26 Aug 2025 14:47:03 +0000
From: Simon Josefsson <simon@josefsson.org>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Subject: Re: Question about BCP 14 / RFC 8174
In-Reply-To: <MN2PR17MB4031F73336C43683553B84B9CD39A@MN2PR17MB4031.namprd17.prod.outlook.com> (Rich Salz's message of "Tue, 26 Aug 2025 13:08:00 +0000")
References: <aKzK5qdwLUHSa3JL@ubby> <878qj67dcq.fsf@josefsson.org> <MN2PR17MB4031F73336C43683553B84B9CD39A@MN2PR17MB4031.namprd17.prod.outlook.com>
OpenPGP: id=B1D2BD1375BECB784CF4F8C4D73CF638C53C06BE; url=https://josefsson.org/key-20190320.txt
X-Hashcash: 1:23:250826:rsalz=40akamai.com@dmarc.ietf.org::XHMNfVcX+uoOYvho:4R+7
X-Hashcash: 1:23:250826:simon=40josefsson.org@dmarc.ietf.org::DJgECh3eyuZGNHqA:7Fly
X-Hashcash: 1:23:250826:ietf@ietf.org::RwProeWlfQtflS9y:B5WK
X-Hashcash: 1:23:250826:nico@cryptonector.com::57b3FKIdV7O0KNf8:0Vxv/
Date: Tue, 26 Aug 2025 16:42:44 +0200
Message-ID: <87y0r6i1p7.fsf@josefsson.org>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Message-ID-Hash: FWFMQ5MLBBNB25PUT7DUPJ6NGA34BKWH
X-Message-ID-Hash: FWFMQ5MLBBNB25PUT7DUPJ6NGA34BKWH
X-MailFrom: simon@josefsson.org
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: Nico Williams <nico@cryptonector.com>, "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/hkJHaxj-KvVVD9KYs8N1gOUeH6o>
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>

"Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org> writes:

> 
> * 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.

Including IAB, IRTF and other non-IETF bodies which also publish RFCs?
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.

/Simon

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