IETF Logo Mail Archive

Re: Internet-Draft draft-rsalz-2026bis-00.txt is now available.

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 29 August 2024 21:33 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9212AC16940B; Thu, 29 Aug 2024 14:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Zc5MoqdDgpC; Thu, 29 Aug 2024 14:33:22 -0700 (PDT)
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 ietfa.amsl.com (Postfix) with ESMTPS id D0092C169402; Thu, 29 Aug 2024 14:33:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 5A0713898D; Thu, 29 Aug 2024 17:33:19 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id l_W_SHgXjO6b; Thu, 29 Aug 2024 17:33:18 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1724967198; bh=szuJ4VAP5/J0QGlXsE3e7zVbX2XHXS6yc0QIqT3UQCY=; h=From:To:Subject:In-Reply-To:References:Date:From; b=NxvQQtRWE0s9YCTIz8k7jKG+GpuVnxsIFQqT9HjICp+TY1n5WvSBT5AR6YrUR36NN pgyL0cJ45YcyhpAfB98UJaVQOJRC5aNn+MRTA+eDtBsGSiOP+a7XwOTj9twTvhLe0y pUoP2aEa0VTaprlKCvepUvgDNFb/ZaCh357/AjeV1ywoHWykNzu+Ylw/P5Y6fbVHg8 +57RoB3u2MK0FA4VtBT9tXBWm4Y26+jbCn0ILhZkKSw51mkQ8TmgF4qBlUx9ZA3Xia M/h/Ox5H9FgIHa6yknSjTSo0zw33Wcr2i1b7zvD6HafYwebpsiYDZLGdC8bu62kvu3 6vtOolyw+59Rg==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 890D13898C; Thu, 29 Aug 2024 17:33:18 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 84894109E; Thu, 29 Aug 2024 17:33:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "chair@ietf.org" <chair@ietf.org>
Subject: Re: Internet-Draft draft-rsalz-2026bis-00.txt is now available.
In-Reply-To: <LV8PR11MB85369B446C582BF1352049FDB5942@LV8PR11MB8536.namprd11.prod.outlook.com>
References: <9253BAA6-2278-496E-8832-EEB802B54242@sobco.com> <63c4e784-f949-4d5c-97c6-889d2d5bca3a@gmail.com> <7FA8E1ACC4330226FD4A5EEE@PSB> <9a0d142e-057d-44f3-af6b-db72a603ecfd@gmail.com> <LV8PR11MB85369B446C582BF1352049FDB5942@LV8PR11MB8536.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
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, 29 Aug 2024 17:33:18 -0400
Message-ID: <4724.1724967198@obiwan.sandelman.ca>
Message-ID-Hash: RADGDVYM3HWHU772YVR7I3KVZXUEWLJK
X-Message-ID-Hash: RADGDVYM3HWHU772YVR7I3KVZXUEWLJK
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_Tc9Ebr6f0L1FFdHOsbl8exuOIg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

Rob Wilton \(rwilton\) <rwilton=40cisco.com@dmarc.ietf.org> wrote:
    > 3.  Split/migrate the existing IETF process into what must be in the
    > RFCs/BCP and what moves to webpages (hopefully also incorporating
    > appropriate IESG statements).  If we want to change core parts of the
    > IETF process, i.e., the parts that are documented in BCPs, then this
    > may be a time to consider this, but this could also be deferred, to
    > reduce risk).  Moving text to webpages may be quite a lot of work, but

What kind of risks are you thinking here?

I think that the biggest risk is a 1000 message long debate over minutia
which pisses off half the community, and we lose the energy to finish :-)

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

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