IETF Logo Mail Archive

[Gendispatch] adding new forward references after publication

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 21 January 2026 15:57 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: gendispatch@mail2.ietf.org
Delivered-To: gendispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 496ECAAF9ACA; Wed, 21 Jan 2026 07:57:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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_LOW=-0.7, 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=sandelman.ca
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 iqQMtHbYH2Br; Wed, 21 Jan 2026 07:57:56 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 EB44EAAF9AC2; Wed, 21 Jan 2026 07:57:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 7352718012; Wed, 21 Jan 2026 10:57:55 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id 4oKqUqCKuH8k; Wed, 21 Jan 2026 10:57:53 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1769011073; bh=qxg5q0CbkQWTAo3UHdHBMnuOy36oKU74KA/NzxYy6Q4=; h=From:To:CC:Reply-To:Subject:In-Reply-To:References:Date:From; b=Bi0BgAQYW467Ey+S+FOHv2mc20n3uRq1E+fO6NxOASwbvRJqmoygjfP4bn3Q6Tjup myY+iz/iYSRxw5L/8A4tl+wc9ZHe3Fn+WBCxNt6MD+7BsThbWQu8yteLL+5hNS/P+e NO8zAdtWkdzo++dbOixxZMEq+w/igOpl+Ns6fnp34TJrzhqSfmIHV3T9DSpHpU+oMr 5gsuFvMN7/dNnluCkCq8mQESYISPmEOWHxbHDFsVjUuCmErZSMHngHCkknZFVkYz9V whzE4Z2SCL7oq8tHl7AlGDdtU6S6NVynjhnHi6K0B0mr94gOyQqk+hFsV0iR0XZ2ZI CXd6Xu7dBbpMw==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2F40C18011; Wed, 21 Jan 2026 10:57:53 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 266E81AE; Wed, 21 Jan 2026 10:57:53 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: tools-discuss@ietf.org, gendispatch@ietf.org
In-Reply-To: <0100019bdc499bc5-e02406ac-1354-4c68-87d2-0bba5cc0a567-000000@email.amazonses.com>
References: <176881747091.641185.2163432407686031992@dt-datatracker-865585c994-4fgh4> <b0b18fc293fc4461a5a9046f5a75fbf5@huawei.com> <CH3PR11MB851963046DCDCE5F00DCDF6AB589A@CH3PR11MB8519.namprd11.prod.outlook.com> <0100019bdc499bc5-e02406ac-1354-4c68-87d2-0bba5cc0a567-000000@email.amazonses.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 21 Jan 2026 10:57:53 -0500
Message-ID: <8019.1769011073@obiwan.sandelman.ca>
Message-ID-Hash: RTKYMIQACJ3FYX2YNLFV6F5ZZJQK6XUZ
X-Message-ID-Hash: RTKYMIQACJ3FYX2YNLFV6F5ZZJQK6XUZ
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: procon@ietf.org, Kent Watsen <kent+ietf@watsen.net>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: gendispatch@ietf.org
Subject: [Gendispatch] adding new forward references after publication
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/aMzLYZzy6Hc0V-ug4EnikbgaTeU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

Please see reply-to: gendispatch@

Kent Watsen <kent+ietf@watsen.net> wrote:
    > Separately, I think the WG made a mistake when publishing RFC 8808,
    > which should have also *updated* RFC 8342.  It is unfortunate (dare I
    > say tragic), as the <factory-default> datastore remains hidden to many.
    > IDK if there exists a mechanism to change the "update" status of a

It happens more often than I think anyone likes that we realize that readers
of some other document would benefit from reading a future document.  One
that we didn't think about at the time.

Since in the end, the updates information is meta-data, and really lives in
the DT (and RFC editor database), I wonder if we couldn't create some new
category of relationship.  Amendable after publication without an RFC.

This would I think, be akin to when we mark an RFC as Historical or Obsolete
without publication of an RFC... it's an IESG decision subject to an
IETF-wide LC comment.

I'm CC procon, lacking another venue, but it's clearly not about
consolidating existing practice.   I could write an I-D for a future GENDISPATCH.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

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