[Gendispatch] Re: [Tools-discuss] Re: adding new forward references after publication
Michael Richardson <mcr+ietf@sandelman.ca> Thu, 22 January 2026 17:49 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 05BABAB8E317; Thu, 22 Jan 2026 09:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level:
X-Spam-Status: No, score=-2.8 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, 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 mMlTQ87R5d8R; Thu, 22 Jan 2026 09:49:03 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 093BDAB84E54; Thu, 22 Jan 2026 09:16:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id A8B731801B; Thu, 22 Jan 2026 12:16:50 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id ns0ItwRtz8JX; Thu, 22 Jan 2026 12:16:49 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1769102209; bh=Zqhmbd6NZX7XaBqyFKpxg/CmiGokCfb4coMbE/bVrMs=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=FpIDGLrjhyfeSDkSDDieDqcC6g2rfbguZwsfdPfJuLdbJ8iczmcjYuW6o9t7Exinj w0jZlMMhh3lQ8tON7eSn02TVJSSXUIrqRn0+hBiy7NWPIOVar3BvK11HtiV1N+B3Fj Io7HztUN0QOx2xMHHaAuUEEegIrnQA6A52vciJB5JAJSy9yPMtX9BGGqWo8z/aZzR7 sUB95uDGYBBEjeNoFJBA5SKISfCYzdIHfqDCIE6N/1wf8ZkB26NrKtOlh7rvqSh1bq rfyyoqVszA85IAqJcToArP4g5OuTZnoVMqInxiGJSuhiHaoC994jIk8N69CzE1dqNe bqUl3WsrkAbVg==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7A9C618019; Thu, 22 Jan 2026 12:16:49 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 746E01AE; Thu, 22 Jan 2026 12:16:49 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, gendispatch@ietf.org
In-Reply-To: <3f3ab144-4f94-47d2-b0dc-0e76f9241a5b@gmail.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> <8019.1769011073@obiwan.sandelman.ca> <a9373c84-c0ff-4853-a5c5-e49ab106ef60@joelhalpern.com> <3f3ab144-4f94-47d2-b0dc-0e76f9241a5b@gmail.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: Thu, 22 Jan 2026 12:16:49 -0500
Message-ID: <24733.1769102209@obiwan.sandelman.ca>
Message-ID-Hash: RFEYNJLGAABQ4CCMUA5BMQ3S6NXP6KH5
X-Message-ID-Hash: RFEYNJLGAABQ4CCMUA5BMQ3S6NXP6KH5
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: tools-discuss@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] Re: [Tools-discuss] Re: adding new forward references after publication
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/AxIetqxrQHQCTWq0xIjQkbj14r8>
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>
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> On 22-Jan-26 05:01, Joel Halpern wrote:
>> One of the main reasons I see for "improper" inclusion or exclusion of
>> updates items is that different people understand the tag differently.
>> And IESG efforts to fix that have not gotten community support. Adding
>> another tag without clarifying "updates" does not seem effective.
> Yes, and draft-kuehlewind-rswg-updates-tag is still hanging around. It
> proposes to formalize "See Also":
It only works/helps if we remember to include it in the new document.
That's not my question.
--
Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
- [Gendispatch] adding new forward references after… Michael Richardson
- [Gendispatch] Re: adding new forward references a… Joel Halpern
- [Gendispatch] Re: [Tools-discuss] Re: adding new … Michael Richardson