IESG Statement on Clarifying the Use of BCP 14 Key Words

IESG Secretary <iesg-secretary@ietf.org> Tue, 18 March 2025 03:23 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from [10.244.8.216] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 63554D6BF39; Mon, 17 Mar 2025 20:23:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IESG Statement on Clarifying the Use of BCP 14 Key Words
X-Test-IDTracker: no
X-IETF-IDTracker: 12.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174226820622.403644.10725566415296176967@dt-datatracker-5b9b68c5b6-zxk6z>
Date: Mon, 17 Mar 2025 20:23:26 -0700
Message-ID-Hash: 7MKZSPWLOWHP6FKZ6JZIVNZH2SDYE44G
X-Message-ID-Hash: 7MKZSPWLOWHP6FKZ6JZIVNZH2SDYE44G
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: iesg@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: iesg@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/JhzRWpjAv0zU4MGoe_OZAUEHLW0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

The IESG has issued a Statement on Clarifying the Use of BCP 14 Key Words.

18 March 2025

Since March 1997, the IETF has relied on BCP 14 for definitions and guidelines for the use of certain key words to specify requirement levels for various normative assertions in technical specifications.  Other standards organizations have also adopted the use of BCP 14 in their specifications.

Notably, BCP 14 recommends these key words be used “sparingly” and mandates they not be used unless they are “actually required for interoperation or to limit behavior which has potential for causing harm.”

Over time, the use of these key words has become less crisp, and they are now used in additional ways in Internet-Drafts.  The IESG provides the following clarifying guidance on the interpretation and use of BCP 14.  However, this guidance is not exhaustive, and other questionable uses of BCP 14 may be identified as documents are processed by the IESG.

Read more: https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/