[Gendispatch] Re: [procon] could the Updates question be within the charter for procon?
"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Tue, 15 July 2025 16:56 UTC
Return-Path: <ietf@kuehlewind.net>
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 EF947446C0E3 for <gendispatch@mail2.ietf.org>; Tue, 15 Jul 2025 09:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_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=kuehlewind.net
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 PGXEUZ1cebcK for <gendispatch@mail2.ietf.org>; Tue, 15 Jul 2025 09:56:44 -0700 (PDT)
Received: from outbound.st.icloud.com (p-east2-cluster6-host2-snip4-10.eps.apple.com [57.103.76.191]) (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 52F23446C0D1 for <gendispatch@ietf.org>; Tue, 15 Jul 2025 09:56:44 -0700 (PDT)
Received: from outbound.st.icloud.com (unknown [127.0.0.2]) by outbound.st.icloud.com (Postfix) with ESMTPS id 24D331801015; Tue, 15 Jul 2025 16:56:41 +0000 (UTC)
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kuehlewind.net; s=sig1; bh=vwB4pPx2nYwWaVuBSbTcTT6wHT5MTGTkXozzpZrRKDE=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To:x-icloud-hme; b=Mr+LSD0n4W2vxdMz/IMKQFSJb85YiJF9540x8XXfrLJB7D8zlyw/MyBftCbaeXFNAcpt05uLzcvlZmiTvRplRfq57fIl5RIRxDOlj3LTWkFbWX97wp7Jx0y3ahabvSVB2WJPNQ10GAzXS4iVlZEpiQYgX7YUfFeR3FsouS9gvvojCOrKfO7pu36g5FqJeQ/vAIRBXe0ztFYhz2MF5mRhJsjEDfkIAtXPa7thdPRK6bxoFuh6y9qUqvVi/eUwoR+us0F+jPFXzqkB0LGborG8vVa1GzS6kq/eAK+6MYs3eisgc2CM/3pfdbnlFtyxWueD8EzuXKRiMvey8bTk/5oUyQ==
Received: from smtpclient.apple (st-asmtp-me-k8s.p00.prod.me.com [17.42.251.67]) by outbound.st.icloud.com (Postfix) with ESMTPSA id 153871800C8F; Tue, 15 Jul 2025 16:56:40 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <551275.1752595806@dyas>
Date: Tue, 15 Jul 2025 18:56:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2378A3E-2518-48CA-8336-DA7DFB134C2C@kuehlewind.net>
References: <2027567.1749411385@obiwan.sandelman.ca> <49aa3e0a-71de-4f3d-a9c9-0fe7c0342c24@gmail.com> <BN2P110MB11070B3A4F8A4EEAA4549E97DC7AA@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM> <23797.1750953043@obiwan.sandelman.ca> <88C7EF29-C583-4DC0-97DD-A77599364202@kuehlewind.net> <551275.1752595806@dyas>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3776.700.51.11.1)
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUwNzE1MDE1NSBTYWx0ZWRfX4/t24WEerv9O Pn/mEH1bHixM+1bSCNpeKvhAfSe4OowL6ejrMSfEmmI3Ewu2cqDJleOEhnwkmLHuZFe74IawJ6/ hPKPijK5I5Aw/ZMHEzGuB5u8vdTRNtJpyjyjx/UVc+5JvK0HgIp/PUTt1iAhVCj7g2cQgK+NLLx EyNKY2MrJX5LdTg0YoJLn8WUploH0XXvlPdcmvneWXW+t6/GWZTDQ0shcNfhlxS4KqcAnvQwYLV HjWWqEQRa27SiWU19Qlk/ZVl/kmwDym7U2NHtqCuQOr3XJ5VYy97lHSGHjSkmf6HHQFmbg5ww=
X-Proofpoint-GUID: XzUChB-P57EnRt8JMfo_gggMvtE0FccQ
X-Proofpoint-ORIG-GUID: XzUChB-P57EnRt8JMfo_gggMvtE0FccQ
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1099,Hydra:6.1.9,FMLib:17.12.80.40 definitions=2025-07-15_04,2025-07-15_02,2025-03-28_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 mlxlogscore=999 clxscore=1030 suspectscore=0 bulkscore=0 mlxscore=0 malwarescore=0 adultscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.22.0-2506270000 definitions=main-2507150155
Message-ID-Hash: UQDACNE6TWALEZOLM4YJHZOE6IX4EQFA
X-Message-ID-Hash: UQDACNE6TWALEZOLM4YJHZOE6IX4EQFA
X-MailFrom: ietf@kuehlewind.net
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" <procon@ietf.org>, "gendispatch@ietf.org" <gendispatch@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] Re: [procon] could the Updates question be within the charter for procon?
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/spFeS0G07CpUc7FxdYVkWYPjX58>
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>
The draft provides a definition of the tags which are meta data of an RFC which I think should be uniformly defined for the whole series. If each stream uses these tags then, is a question for each stream separately. > On 15. Jul 2025, at 18:10, Michael Richardson <mcr+ietf@sandelman.ca> wrote: > > > Mirja Kuehlewind (IETF) <ietf@kuehlewind.net> wrote: >> I thought the updates tag draft should go into RSWG, that also why we >> resubmitted at some point with -rswg- in the name. However, that group >> seems to be too much focused on other things :-( > > hi, I can see some mechanical questions that the RSWG should ask the RPC to > figure out. Particularly around Amends that effectively are complicated errata. > It might be the RPC might want to subdivide some of Amends/Extends/See-Also > into more categories. > > But, I think that the semantics of when/how/why to use these needs to remain > with the stream itself. > >>> On 26. Jun 2025, at 17:50, Michael Richardson <mcr+ietf@sandelman.ca> wrote: >>> >>> >>> Roman Danyliw <rdd@cert.org> wrote: >>>> [Roman] Procedurally, I am trying to find the right balance between >>>> accomplishing the original goal of PROCON to simply producing a 2026bis >>>> and 2048bis which consolidates all updates into a single draft while >>>> simultaneously opening up these documents for procedural revisions. I >>>> am open to recharters at a measured pace. My current opinion is that >>>> having stable 2026bis/2048bis I-Ds or even RFCs will position us best >>>> to them make subsequent changes. ==[ snip ]== >>> >>> This works for me. >>> While I agree that it does not fit into the current procon charter, I think >>> it's the same group of people in the end. >>> So let's get to stable 2026bis first. >>> >>> >>> -- >>> Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) >>> Sandelman Software Works Inc, Ottawa and Worldwide >>> >>> >>> >>> >>> _______________________________________________ >>> procon mailing list -- procon@ietf.org >>> To unsubscribe send an email to procon-leave@ietf.org > > > > > -- > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works > -= IPv6 IoT consulting =- *I*LIKE*TRAINS* > > > > -- > Gendispatch mailing list -- gendispatch@ietf.org > To unsubscribe send an email to gendispatch-leave@ietf.org
- [Gendispatch] could the Updates question be withi… Michael Richardson
- [Gendispatch] Re: [procon] could the Updates ques… Brian E Carpenter
- [Gendispatch] Re: [procon] Re: could the Updates … Roman Danyliw
- [Gendispatch] Re: [procon] Re: could the Updates … Michael Richardson
- [Gendispatch] Re: [procon] could the Updates ques… Mirja Kuehlewind (IETF)
- [Gendispatch] Re: [procon] could the Updates ques… Michael Richardson
- [Gendispatch] Re: [procon] could the Updates ques… Mirja Kuehlewind (IETF)
- [Gendispatch] Re: [procon] could the Updates ques… Michael Richardson
- [Gendispatch] Re: [procon] could the Updates ques… Pete Resnick