IETF Logo Mail Archive

Re: [Gendispatch] New Version Notification - draft-eggert-bcp45bis-04.txt

Martin Thomson <mt@lowentropy.net> Mon, 27 September 2021 00:05 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C0E43A183A for <gendispatch@ietfa.amsl.com>; Sun, 26 Sep 2021 17:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=YTZKvZIw; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=TiYV6gts
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QcApVEo2O-vm for <gendispatch@ietfa.amsl.com>; Sun, 26 Sep 2021 17:05:39 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F0823A1830 for <gendispatch@ietf.org>; Sun, 26 Sep 2021 17:05:38 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 6E2805C007B for <gendispatch@ietf.org>; Sun, 26 Sep 2021 20:05:36 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute5.internal (MEProxy); Sun, 26 Sep 2021 20:05:36 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm3; bh=sxTC/ 6tIMg4y8I/PmJkWQ5pcs98Go0w/ULzzGGAPIfI=; b=YTZKvZIwTeOAge71ujG73 Gebluhsyw9mih315DfbzBoOfKQBko3hc0KBQdasr4BYzXXhAAlOfWpRqer8GNV19 vLRagDay72TyjpCVGxuf8Y0B2h1m/IwjV+qZzhBZvPaikdeRTFXOT+bgjjhR2o6j ouHmUrGhU7WGGAyViVO7iIos2PUVBEJQshvdMwzzuBeDhI0asicng/JdqfiJe7qt k1sE8BLmCVYJl0o3UDHjvVh78fCZcbSfLuxZPx125h2iyf+cWKSMSTngwHD0mPHS TgM+XVniyalYT6gLFo4s5M7xIyecYvRxUGv8fk10qD6hjMeZslszv0seUtV6LynZ g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=sxTC/6tIMg4y8I/PmJkWQ5pcs98Go0w/ULzzGGAPI fI=; b=TiYV6gts28RjEn+BLvDrVf+FSW3bTaNZvZNW0232x70cfBvO/aiMfqbt+ xIyDNCGospPS5eqYQW737ya4ILjxXO4W1LiFHij+4RiJrhX7SwqmYvVCmMxax+wN z7XawNJ3j/G2T9Ios+zWv2rPyiyMW9gf3i2yDHVQQml5xxUJWuynreERcn4EfQak rqD4m5ISHQeAzOJ4bvXqEZDUg0K8ujHi+D/OCDp1DcvQZl0+fixjOhDZPLdIx722 GBdqHXeWb0YdmS0cSjycxmxxNYu3uR2DSBWOOqauULn9vheNYDS7b7DgeFHELUbK EcX1qNlE1Epwx0qmKD3Ls+c/Lx3jw==
X-ME-Sender: <xms:0ApRYbx0ryY_eWB-TCVHOSTBBViAZNSXJ70LSJnNAMg83ESh1IrB1g> <xme:0ApRYTS42wgq35CoAE4wIKb_hI80QNVzCy0eOhsV96ldcPGZBPrXkV5ja5WnErR2n jhUz8QjssBWnW2sQLQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudejjedgfedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtgfesth hqredtreerjeenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepgfejueduieffledtge elheejvdettdejudduhefggeefgfekgfeuieetgefftddtnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnh gvth
X-ME-Proxy: <xmx:0ApRYVV-XAwU7OE_MFA8NLZPs-c52owwJB_CB-5pp99L1aC4NafurA> <xmx:0ApRYViUIc4lAMQIbbR4kT_b30FXgDa18DOBAfEt3BuDNhTOzUkTAQ> <xmx:0ApRYdD99jzKpNdhj7SI7qxcerpmScMCxybpfVjpJVvblO68E5mi7w> <xmx:0ApRYQM7myUNUZIoRXvEMmXFbj8LajdrkmvzyMFXaztC0bk6ZWpK4Q>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4961E3C0E5F; Sun, 26 Sep 2021 20:05:36 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-1303-gb2406efd75-fm-20210922.002-gb2406efd
Mime-Version: 1.0
Message-Id: <aa5e366b-a1f7-4b5a-a4e3-b6f280494847@www.fastmail.com>
In-Reply-To: <75349e81-e85f-b92d-92da-98497ea2b2f0@network-heretics.com>
References: <DM4PR11MB543899B05B3BD7AD92459B3FB5DB9@DM4PR11MB5438.namprd11.prod.outlook.com> <A1F6409C-97AA-42A9-AAFD-C1AED39559E9@yahoo.co.uk> <F3E0166F-1ABC-445C-A269-54BB523BA5FA@eggert.org> <CABcZeBOu-QMv6e00gOsZivjvzkKr1G3b+pS5R6=UGx2hMAv5Uw@mail.gmail.com> <75349e81-e85f-b92d-92da-98497ea2b2f0@network-heretics.com>
Date: Mon, 27 Sep 2021 10:04:53 +1000
From: Martin Thomson <mt@lowentropy.net>
To: gendispatch@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/RnAexYFSTqW4YTNJSKubVgkfgL4>
Subject: Re: [Gendispatch] New Version Notification - draft-eggert-bcp45bis-04.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Sep 2021 00:05:45 -0000

On Mon, Sep 27, 2021, at 04:29, Keith Moore wrote:
> Asking for a draft, or at least a concrete set of proposed changes to 
> the current document, seems reasonable.  What does not seem reasonable 
> is to publish the current draft before these identified problems are 
> dealt with.

This is a process document.  It describes how things work.  Whether you like current practices, there is still value in having processes documented.  I'm supportive of publishing this documentation of current practices.

As far as changes to the moderation of some of the more contentious IETF lists goes, it is very reasonable to start a discussion about how those processes might be improved.  It is perfectly normal for the update of process documentation to stimulate thinking and conversations about improvements to process.  However, any changes that result belong in the NEXT update.

v2.23.0 | Report a Bug | By Email