IETF Logo Mail Archive

[rfc-i] Re: bcp14 highlighting in the wrong place

Carsten Bormann <cabo@tzi.org> Mon, 08 June 2026 22:54 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@mail2.ietf.org
Delivered-To: rfc-interest@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B6A48FDB8696 for <rfc-interest@mail2.ietf.org>; Mon, 8 Jun 2026 15:54:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780959284; bh=9go7uKzSMH/A8tRwos1VqGvo6fvt60qYu0/bYnP/72A=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=MFXbys2TecFOMC73PKVPUtyjj2svOmRsqJObfyW2UN4KXHM00ScfZisSLD4QksZQw OUSe8ez9B8/wBn0b/K5gikmNpcqO7MVUqB0XqAyl5p7yHxyrQAwK6o+EP7K+Q+fbQb LrS3hsB9bero1xnPvRQMM6MtEyQunIVYBJB1d/gA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.389
X-Spam-Level:
X-Spam-Status: No, score=-4.389 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_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=tzi.org
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 PV8NWFGcOB6x for <rfc-interest@mail2.ietf.org>; Mon, 8 Jun 2026 15:54:43 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (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 263F9FDB7F53 for <rfc-interest@rfc-editor.org>; Mon, 8 Jun 2026 15:54:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tzi.org; s=2019; t=1780959249; bh=9go7uKzSMH/A8tRwos1VqGvo6fvt60qYu0/bYnP/72A=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=pRw9NTne5P5LUA/s8MfGxGwewnQZTWtnSzHVSGhTdc1yBHVLjP8V0siW/egxLYjin mB6BqhXN5yxlnyMAZiup1gzp8j8PKnQkUV+iQwqgTR+z11hJHzBCjZ1hTEWTsus5xv khpsyJLoEvr4Ny01iE+ne59IlbBS0FWnFFVJOvqmGM++ePMIl8B3DPSBylDgyP592B xwszdBOis31JytajYGT53+6cMdfVp0EO679QLJN2nVwVliO7NrvtRPgcz2Mwj9i7bG F8UADvp0eokODaR2oo9riSeuRXuymOdEUNYrQu1bexI2jU6IS0vydfyZl7k+siozdq GKLfQ3vIZ6W5A==
Received: from smtpclient.apple (p5089ab3c.dip0.t-ipconnect.de [80.137.171.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: cabo) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4gZ6mK1Sd4zDCbH; Tue, 9 Jun 2026 00:54:09 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <a5a8f477-5cbc-4931-ad52-57b3e115fb9f@staff.rfc-editor.org>
Date: Tue, 09 Jun 2026 00:53:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AA59048-8025-4702-BE1B-199B6D601F2C@tzi.org>
References: <6ed8eda2-367c-4b03-9c82-d3a1df327cde@gmx.de> <14F860B9-A1F7-438D-92E2-2698AC20CF8A@tzi.org> <a5a8f477-5cbc-4931-ad52-57b3e115fb9f@staff.rfc-editor.org>
To: Jean Mahoney <jmahoney@staff.rfc-editor.org>
X-Mailer: Apple Mail (2.3864.600.51.1.1)
X-FromAuthMilter: ok
Message-ID-Hash: 5RT2P4W4KRU4VUZFWY4M33JLYXFAVSRJ
X-Message-ID-Hash: 5RT2P4W4KRU4VUZFWY4M33JLYXFAVSRJ
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rfc-interest.rfc-editor.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Julian Reschke <julian.reschke=40gmx.de@dmarc.ietf.org>, rfc-interest@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [rfc-i] Re: bcp14 highlighting in the wrong place
List-Id: "A general discussion list about the RFC Series and its operational processes." <rfc-interest.rfc-editor.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/K_c-2jJdLOZM71gYV-NiEBvLHRY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Owner: <mailto:rfc-interest-owner@rfc-editor.org>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Subscribe: <mailto:rfc-interest-join@rfc-editor.org>
List-Unsubscribe: <mailto:rfc-interest-leave@rfc-editor.org>

Hi Jean,

> On Jun 9, 2026, at 00:44, Jean Mahoney <jmahoney@staff.rfc-editor.org> wrote:
> 
> Would we need an rfc8174bis document for this update?  Or could we just point to our current guidance on referencing subseries?

When I brought this up the last time Barry Leiba convinced me that we’d need an rfc8147bis to make this change.
(I didn’t think so, but it can be reasonably argued.
Maybe we can bring that question up again?)

Doing a bis would be lots of overhead for a very small adaptation to reality (we can now do things we couldn’t do nine years ago), so I put that on the back burner.
I still would like this to eventually happen — but maybe we have to wait for other changes to become desirable as well to justify the bis effort.

Grüße, Carsten

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