Re: https://chairs.ietf.org/documents/i-d-adoption

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Tue, 14 October 2025 17:10 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: wgchairs@mail2.ietf.org
Delivered-To: wgchairs@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 349A17360D96 for <wgchairs@mail2.ietf.org>; Tue, 14 Oct 2025 10:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 jeNadDr7WMDQ for <wgchairs@mail2.ietf.org>; Tue, 14 Oct 2025 10:10:50 -0700 (PDT)
Received: from outbound.st.icloud.com (p-east2-cluster1-host8-snip4-10.eps.apple.com [57.103.76.83]) (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 70A757360C4A for <wgchairs@ietf.org>; Tue, 14 Oct 2025 10:09:53 -0700 (PDT)
Received: from outbound.st.icloud.com (unknown [127.0.0.2]) by p00-icloudmta-asmtp-us-east-1a-10-percent-1 (Postfix) with ESMTPS id 42915180071B; Tue, 14 Oct 2025 17:09:45 +0000 (UTC)
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kuehlewind.net; s=sig1; bh=tALa8kjoJnrna7S+JGJzXWaiYf/s8WYHXrZKSPQY+rU=; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To:x-icloud-hme; b=z3fTnOyLrDssMaI8FOa+FDm+lck6NbuQRj5mDenm6O727FSejbtNKZqv79NckHmOO6ZQltle+4NrUsytgX1pYndQZdLVmtkxGoXcA5QGcZWPUvaNs2RN8rGthCLAl8FesnjWFKSL+k/RXHOtanabFT6ojYSFZHknmEq0T7+P1VeEuWNA4XNcmzPOdOESSpXqYQqfBM0T+83r2MmiLaCLbC1VCa8a/nnjT5/CCnggDOpz4Jfzmhk5jQjD/m0flkrgrQcuYc+MRfSFF4OpQnlQxExA812d/ogsh5IZsRzA/hPYpoMAdzv+8J7gpDXsJT8plfve7sSksP/prujU3t1QYg==
mail-alias-created-date: 1725731591227
Received: from smtpclient.apple (unknown [17.42.251.67]) by p00-icloudmta-asmtp-us-east-1a-10-percent-1 (Postfix) with ESMTPSA id 77A211800208; Tue, 14 Oct 2025 17:09:32 +0000 (UTC)
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Message-Id: <34D6756F-4694-4B80-A708-53EA205F8223@kuehlewind.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_091BC7A4-CE81-4932-9786-B05C0D04FD48"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
Subject: Re: https://chairs.ietf.org/documents/i-d-adoption
Date: Tue, 14 Oct 2025 19:09:20 +0200
In-Reply-To: <37c0efe5-396d-4243-a610-5fbf15ac83ed@app.fastmail.com>
To: Bron Gondwana <brong=40fastmailteam.com@dmarc.ietf.org>
References: <c716beb9-cfa8-4364-8f73-2256ff7f9c6c@sidn.nl> <FA24E274-9C74-4DD3-812F-DFA660AC178C@staff.ietf.org> <086D6187-23E6-472C-9085-54336FC62A2B@episteme.net> <CAA=duU3B9OY2Mt+dnZ33RD3oFV8Brc8JVmoEQpyPx19gja0HJw@mail.gmail.com> <MN2PR17MB4031C871EC497A2AE1CEAA17CDEAA@MN2PR17MB4031.namprd17.prod.outlook.com> <CAA=duU25BsPMBiR7Mr9hyN9QRf2YNQ4O7ErgrSjHuMO10yED-w@mail.gmail.com> <2A28DBBF-8736-497F-B5A0-D0802F99B64C@episteme.net> <8bcec90a-8fba-46ab-8133-a659ec37e041@cs.tcd.ie> <207d8536-d708-417b-8ada-b03bcfca2028@riseup.net> <17782.1760455018@obiwan.sandelman.ca> <MN2PR17MB4031364FDA766103543E3358CDEBA@MN2PR17MB4031.namprd17.prod.outlook.com> <37c0efe5-396d-4243-a610-5fbf15ac83ed@app.fastmail.com>
X-Mailer: Apple Mail (2.3776.700.51.11.1)
X-Proofpoint-GUID: beQAtVwMGVEPkwjlVHkPMRNwXgVdDc9R
X-Proofpoint-ORIG-GUID: beQAtVwMGVEPkwjlVHkPMRNwXgVdDc9R
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUxMDE0MDEzMSBTYWx0ZWRfXwkfm4bUNXVZh lyFkQx8+d4HX2QmQo0+YhpNAczhtRv4hPJKf5ydasBR6vs/dwFjz+UfS3mFt9LAjBAHeL+jHKWw uSO7wbDvpIBWmz/TDKdf61usnXYHXzt3vn9fMLKXEeaE4MY/vqjOe1D/Xradc/CTBSD0AEiYZCA ylbbFVqT59XnYrIUKYqWCs0ZOlHf98YWNqWeBbRAULr7b8CbeWo14ricbno67sna77s3chnEVpy ecne4L35sljDY3l2byYZInOfYXjl1NSIbUsrEM2Y5/uKHszxDxgkQt6A4Ewa0zsGXO9aH6CwM=
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.80.40 definitions=2025-10-14_03,2025-10-13_01,2025-03-28_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 malwarescore=0 adultscore=0 spamscore=0 clxscore=1030 suspectscore=0 mlxscore=0 mlxlogscore=958 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.22.0-2506270000 definitions=main-2510140131
X-JNJ: AAAAAAABxL5oO8lRhZwsL+G1QLzdYIWQG9F52tds8cZaw6DlI65iO4O69bgvJJ7QzlSP6pzcmoJp7aO5lG9l1wUtTOzvtc1U9uhv1htO5i7/cDXUe4ZrCGtirefIXhPrl+H2/Iak+zxRNMofmAomj3fM0DVFu+qRUGzxITpdxmfZ0CMDpSU4sZU0fTtPlN9v6Zh2bEe0zFMRhdPhVZw6T5AvTfx+TjW7qnmu0zqDbjkFLj5FDcBj0TBmbDmtpQy1f9rBlzwgzWi8b7nHE5Io2HUYqF4bjHXMWxWyan4JtP6eCVxJNjBfV+CG9tiuphSxryrc2+zkyodeeSiYKC2tv078FGX1tg9KuUA0UDUbpnGEHBcCRYd+1D+zfaUYJJt9B5iStvJiTRslklQrcmKFWaOVmXRuQoWm4FQOn3tkpRgRWuROpmjSxYOzSv41/Eonj7+1mJpT0xLAe8GqUdfrPMxhZ1Yt7ozyHNpfRQplPcQ/cBwMKgoPfFHu/P4WXj9r1m7peS4vXru5HUx+mStaIS2/2Z4vUf6bUqx/+JpDBFIM+AnnYltkP0b3vWNhqAhLsUnq2OZtXXhWnLc+02mFcGZXS59iK89XdUsxi5eJOgGZEe6Aw+iQZPyfFrYPal56eMqaEUFXlQ/JMuEvBFfFlxgy7bU/nRZrlC+SZP2Qulq8fiMfRaijypTiblhM5WvyRM7qmkEcZzsTpktDsSgxxi8c7UfKWjNi
Message-ID-Hash: FT5JYUV7IGH56SQ67L7V2UN4QAY7MOFT
X-Message-ID-Hash: FT5JYUV7IGH56SQ67L7V2UN4QAY7MOFT
X-MailFrom: ietf@kuehlewind.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-wgchairs.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Michael Richardson <mcr@sandelman.ca>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/bpQjv7JjwQc4kGXIOtcnVBWNZro>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Owner: <mailto:wgchairs-owner@ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Subscribe: <mailto:wgchairs-join@ietf.org>
List-Unsubscribe: <mailto:wgchairs-leave@ietf.org>

I strongly recommend to do a publicly recorded adoption call if you want to adopt a document, mainly for transparency reasons. The reason why this is not codified as required in rfc2026 is because adoption itself is optional and effectively has no real meaning in the standards process.

For the standards process the only things that counts is that there is consensus to publish at the end (and that needs to be well documented). However, the status of being adopted doesn’t really have any special standing. I would say it's more an orientation for the working group to understand how far a document is in the process and where the focus should be concentrated to.

However, if a chair/wg wants to adopt a document, I think it is on the safe side to run a public call (which I don’t find a lot of overhead). The chairs (only) job is to judge consensus for any wg decision. And if you handle adoption as a wg decision, I think you are better of if you can ensure and “proof" that there is consensus and that everybody had a chance to speak up which is what the call is for.

My 2c
Mirja


> On 14. Oct 2025, at 17:50, Bron Gondwana <brong=40fastmailteam.com@dmarc.ietf.org> wrote:
> 
> I have had an almost zero rate of "adoption call failed" in my working groups - the only time I've proposed something and it hasn't been adopted was when the authors changed their mind and retracted the adoption request!
> 
> But I've always done a 2 week call because that's how I cargo-cult learned to do it.
> 
> I'd be happy to discuss a more flexible adoption process where for working groups which don't have any issues with too many drafts being proposed or contentious topics coming up.  I'd probably have used that in the past if I'd known it was OK to say "yeah, we all agreed in the in-person call and this seems unlikely to be contentious, let's just adopt it and we can kill it if we discover it's a bad idea during later discussion".  High trust groups would manage that just balance fine.
> 
> Bron.
> 
> On Tue, Oct 14, 2025, at 11:24, Salz, Rich wrote:
>> I strongly recommend that WG chairs do adoption calls like:
>>   "Chairs see support for working on foo-bar.03.  We plan to adopt it.
>>   Please post objections by YYYY-MM-DD"
>> 
>> It seems to me that you should only do that if you’re really sure about consensus because otherwise you’ll have to repeat the process.
>> 
>> Attachments:
>> smime.p7s
> 
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC
>   brong@fastmailteam.com
> 
>