IETF Logo Mail Archive

[Ecrit] Re: I-D Action: draft-ietf-ecrit-lost-planned-changes-16.txt

Keith Drage <drageke@ntlworld.com> Mon, 11 May 2026 09:19 UTC

Return-Path: <drageke@ntlworld.com>
X-Original-To: ecrit@mail2.ietf.org
Delivered-To: ecrit@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 53E9AEC6623A for <ecrit@mail2.ietf.org>; Mon, 11 May 2026 02:19:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778491160; bh=jT/R1EYu8Bo8SDCZSeMTbjktLUFbjErxGEJhQ6ZiSCQ=; h=Date:Subject:To:References:From:In-Reply-To; b=J6nESzlu4tg6+IpnLGv+VmvnjQnALB8F0UdA/NSHY6WMIULKRIhLRDuySnwseIz4v O5ATCjH4FjXtOLPkwI7TNCZEXGQtbqqfgTkkP3fU+CmeE+/h7jKlhlfPw2qGKtPVg1 d2Nb1odOxkIyZCqkydIDbVl9muGOzl8Rco8sxRNk=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_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=vmo-authrelay.edge.unified.services header.b="PXnTFLyS"; dkim=pass (2048-bit key) header.d=ntlworld.com header.b="IbwQOTkx"
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 b2nUpN2Zx61x for <ecrit@mail2.ietf.org>; Mon, 11 May 2026 02:19:15 -0700 (PDT)
Received: from csmtpq1-prd-nl1-vmo.edge.unified.services (csmtpq1-prd-nl1-vmo.edge.unified.services [84.116.50.35]) (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 9AA6AEC66229 for <ecrit@ietf.org>; Mon, 11 May 2026 02:19:15 -0700 (PDT)
Received: from csmtp4-prd-nl1-vmo.nl1.unified.services ([100.107.82.47] helo=csmtp4-prd-nl1-vmo.edge.unified.services) by csmtpq1-prd-nl1-vmo.edge.unified.services with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <drageke@ntlworld.com>) id 1wMMn5-000TFu-TO for ecrit@ietf.org; Mon, 11 May 2026 11:19:08 +0200
Received: from [10.19.88.169] ([194.61.207.70]) by csmtp4-prd-nl1-vmo.edge.unified.services with ESMTPA id MMn5wfb9pc8Z4MMn5wk0VO; Mon, 11 May 2026 11:19:07 +0200
X-SourceIP: 194.61.207.70
X-Authenticated-Sender: drageke@ntlworld.com
X-Spam: 0
X-Authority: v=2.4 cv=UehhjqSN c=1 sm=1 tr=0 ts=6a019f0b cx=a_exe a=goH2sV3TZ1eYELxYs5Jgqg==:117 a=goH2sV3TZ1eYELxYs5Jgqg==:17 a=NGcC8JguVDcA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=48vgC7mUAAAA:8 a=m8ZsFaG_OoaNLzL04JwA:9 a=3ZKOabzyN94A:10 a=QEXdDO2ut3YA:10 a=c5iR93XZ12R1gomFFIcA:9 a=_W_S_7VecoQA:10 a=lqcHg5cX4UMA:10
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=vmo-authrelay.edge.unified.services; s=dkim1; t=1778491147; bh=jT/R1EYu8Bo8SDCZSeMTbjktLUFbjErxGEJhQ6ZiSCQ=; h=Date:Subject:To:References:From:In-Reply-To; b=PXnTFLySMBnoYnsQP5WiNaC2QsP/ayqYn457kZHCyp8Im8TRFUiXB3ghfwsIVr52N uAONFdnQGthwV6IXvtB+Nk/aRfWO7dtyMztAmuGNIb1abWqeuEMrNPirhXZLDbwi1v laRMp5doPhVFZfVYhcvqXjehx3W/iNu9Xjj4KObSKoOGG0rDCtkflSE+ZhYYwq/kCt 0qY5PlY7GCSsudi+xU6UIybDQgSCXPKUSLFlMOv7Irq3VydLUj8i2neoiNOIEGZKE3 gjgSWgmS56kOHNQJa+9hOZR74znYPjl3tERYtXfqJ15imGAE1wSfV8t+jSEsWHLSM3 qr4E7DCmM62uQ==
Feedback-ID: 20260511-??:csmtp-prd-nl-vmo:Authrelay:??
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1778491147; bh=En73cMZUEDnqvrU3uYdEAxtnsvNbdoGErx1FObnxDoA=; h=Date:Subject:To:References:From:In-Reply-To; b=IbwQOTkx8mHrzm+6CS6f5EN6XApz/4wKsc1XV1M0t3cFlmV9umk8HOhK+a5nhvfER D0M6jeMj4ENjljuDUaTUSNMOq9U87enjH9VDA8hdfwdt2d0ynS+K0XWXbAquNFVcNo JuwFtHbL2pH05UnDrAuka4uaemZouC7ybAjRr5VoGOWdFsrqKPEbcZ89ixCKHMHcaL NVMD83pS24YiWpBtka/f8w7IJlJtT4EuUh6/wHuu+OuJxf59taJdvdSsosqtkDog2F y3B7FHFNF6CSyzbxCdssL8ISn2HP8ts6iuv8wGTeNK4fnDS8UYswZSND40IEbweDSB ifQEGmfmxGmxg==
Content-Type: multipart/alternative; boundary="------------kLOv7xQjB0Qi9FEk0srJfSs0"
Message-ID: <2995d0c7-2ca9-4ca8-aefc-a8cd2473b182@ntlworld.com>
Date: Mon, 11 May 2026 10:19:08 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: ecrit@ietf.org
References: <177825263978.107467.13390934289023798105@dt-datatracker-54557f87b8-lnrkh> <CAKB0ssHiLn_xeCd1X5fWGi4spU5-A3yopcoFkFh3cs7iZJXH-g@mail.gmail.com> <99A9212E-ED10-466E-8371-C92E48FACFC8@brianrosen.net> <3385280D-69D6-4F26-B731-C20A0E7EF8C1@randy.pensive.org>
From: Keith Drage <drageke@ntlworld.com>
In-Reply-To: <3385280D-69D6-4F26-B731-C20A0E7EF8C1@randy.pensive.org>
X-CMAE-Envelope: MS4xfAjZnOI3nrHbVDOZAjZx05K3A0dGVq1iYmJ/bBBJ4+njC+q9me5E1F9I1IcWkb7IZcv5pyefMc0d/wPSJbE11F+tBgCrArhPdML20PYivOxe940KY/Nl ZG24G3EWCE1q/fXZd9JzQuqks8+QQIj5XkbIfsAjBF6Qh/oOOtHhoBnMqsfxJtMhLOicSf2iYMRAvw==
Message-ID-Hash: RTDHWZME5K52S35AKBKJ22PAZXAUHO7E
X-Message-ID-Hash: RTDHWZME5K52S35AKBKJ22PAZXAUHO7E
X-MailFrom: drageke@ntlworld.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ecrit.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Ecrit] Re: I-D Action: draft-ietf-ecrit-lost-planned-changes-16.txt
List-Id: Emergency Context Resolution with Internet Technologies <ecrit.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/zDkqa9VctGdznNsQVpZZRGgifys>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ecrit>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Owner: <mailto:ecrit-owner@ietf.org>
List-Post: <mailto:ecrit@ietf.org>
List-Subscribe: <mailto:ecrit-join@ietf.org>
List-Unsubscribe: <mailto:ecrit-leave@ietf.org>

If you follow that argument, the ECRIT work updates an awful lot more 
than one document. I prefer to follow Brian's argument, in that UPDATES 
should only occur if it makes a technical change. Otherwise we are 
changing the whole definition of UPDATES for the whole of IETF.

Keith


On 10/05/2026 21:52, Randall Gellens wrote:
> On 8 May 2026, at 10:24, Brian Rosen wrote: > >> It doesn’t update it = no text in 5222 is affected in any way 
when >> it’s published. It adds stuff, but doesn’t change anything. > > 
I think it makes sense for an extension RFC to have an "updates" > tag, 
so anyone looking at the base RFC will see that's there's > something 
else to see. > > > --Randall > > 
_______________________________________________ Ecrit mailing list > -- 
ecrit@ietf.org To unsubscribe send an email to ecrit- > leave@ietf.org

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