Re: [Rfced-future] Issue 134: Re: How can this process be changed?

Peter Saint-Andre <stpeter@stpeter.im> Fri, 07 January 2022 00:06 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF5A13A0ABD for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 16:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=stpeter.im header.b=c06jKMp4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=l/4QHEV2
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 MTH55GXWetaR for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 16:06:25 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E14E3A0ABC for <rfced-future@iab.org>; Thu, 6 Jan 2022 16:06:25 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 6CA625C019F; Thu, 6 Jan 2022 19:06:24 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 06 Jan 2022 19:06:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= message-id:date:mime-version:subject:from:to:references :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=9 R25xTjaFLO9VmfvPaieyPrD5aWWRupkatfVIHB7iBk=; b=c06jKMp4QhIrhGtGv 9CZHeyMfhg8gwrgsgcuVR8qj64ewzYWMaFScq/Xucav3SuOq7xltIY5lX0ZzHZSL YHTYELaJyXkfKbVjtQTZCclVd1JnLzrcfmbwioRT06gefYpN0k5qbP90gjmsJ7MM iUZB5rbD9BH6zpnm4xp8Ih8ZXnRIX4BdfI33zvr94T6SUzMi0BNThh40xbnvysBl ZwzxdsKtt7oWd1akBl06roPeWz8HV21umZm/K/EKwvGkq1V32DEdieJ3WOmmip8B bnEqNPy+rOtf+6C+ztO2ymORBQEX49jxHgjHTpSqHvG1j9C0Ufd6g71dWkuSG6Lt Yj1Nw==
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=fm1; bh=9R25xTjaFLO9VmfvPaieyPrD5aWWRupkatfVIHB7i Bk=; b=l/4QHEV2jHbqcjVGhq1/nhsZ4bq05GgiShCsbB033DCnZF+VVk60dHn38 cEEjPcfumZCGQlJAk2T8q8MJnfsAMNKm6cWMyc+4YUbygukQQcmXsHLSWTkH4/U2 leh3dz2+WXwokwxKfvoUx08EQSJIab1QMrEoTo6giPpzRXNODKJ0ulbbcHaRg6Cl KkPr/i2ru3pS2iioEHGbhORQaywujT7QPMsZ/OzkjBAaaUiPX+fTrp1C/9QKlC4J Z3lw1V7ENMCTzt+Qdtujw/WBXjTG8vxqIUsVt6cFZIcwLZYay2gDJzR12LKvvlyz prDey9VQzGch+yFE92+cDqt5xDI+A==
X-ME-Sender: <xms:AITXYTB_T_qXzOflfnErrb6BZV2ZUI38PUIMf6ZmuMFaYiXi026jMQ> <xme:AITXYZhjVChAFmBc5LGwMrjd06FoPZb9VLj5RtXiQ5j3MbDMKWHgIq3-akAwUyyZe qTY09kxNf9l1yq5Gg>
X-ME-Received: <xmr:AITXYelP6ZSa20JjjDWiipkYkf6sJx1bJg2oQBi5st6Vw3bsALA9lLfwdwaA0WYDy9J_gVehFQGIoYzZ8jdgGesIgcQ24ABEtnZz2K8>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudegtddgudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffhvfhfjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcuufgrihhnthdqtehnughrvgcuoehsthhpvghtvghrsehsthhpvghtvghrrdhimheqne cuggftrfgrthhtvghrnhepfffgvefgveejieetffeuhfekteeitdduhfevvdehhedtleef udetteegleejgeeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepshhtphgvthgvrhesshhtphgvthgvrhdrihhm
X-ME-Proxy: <xmx:AITXYVzI0QKdKrkWjBVAb4YqJ_m9lnQfzoJBIyJRjQ5Aarwb0_boLQ> <xmx:AITXYYS7aGbB332B9TlpfGx9VYFhUry4nAAnntwbA4LTjaPOGZk00w> <xmx:AITXYYYLp4lEUtP8wI8z9ZP32UeA9i06FEsdxXTQA8WNlynkdz_-5w> <xmx:AITXYTc11hIefbFvgGeFy4sn5swGRnm4946fUnjK40JrgeDcFe9Uug>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 6 Jan 2022 19:06:23 -0500 (EST)
Message-ID: <ec47e794-d67e-d241-e3f2-5d0b34298151@stpeter.im>
Date: Thu, 06 Jan 2022 17:06:19 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
From: Peter Saint-Andre <stpeter@stpeter.im>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Eliot Lear <lear@lear.ch>, rfced-future@iab.org
References: <f718d5a6-0b88-42f1-95b6-81c46db18b00@www.fastmail.com> <61B6976D-14FA-4CD5-A49F-432FABE40533@ietf.org> <DC00B6B2-FFE6-4FDE-AEA3-D67F5D9B2DF7@kuehlewind.net> <a765d5dc-f434-f71a-aaf7-b3ea7a238ede@lear.ch> <0586FE1B-18F1-41C1-9F8E-D4BD42D3814B@mnot.net> <0ea56594-2a74-4dc2-ff42-bf73acca00be@lear.ch> <f54a8145-6871-75bc-504e-cf925d7fbf66@gmail.com> <be9fb84f-9a01-20a9-918e-e8a72b7d1407@nthpermutation.com> <adf77671-dcb7-ab22-a5f1-f15edbd03eeb@gmail.com> <650d784a-a7e8-e27b-e8ea-1f4cf610cd8a@nthpermutation.com> <18340aca-5c46-477c-d6da-f764a9033a6a@gmail.com> <9c12a079-5b4a-5b1a-6fd0-f01c6ed05b94@lear.ch> <6680efce-880a-1c58-518b-3b4e78a30360@gmail.com> <a37561d5-eddf-ee32-2c4d-c5f144235761@stpeter.im>
In-Reply-To: <a37561d5-eddf-ee32-2c4d-c5f144235761@stpeter.im>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/qL8VitV_1ajlP9CTb2nvk0zuvfg>
Subject: Re: [Rfced-future] Issue 134: Re: How can this process be changed?
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2022 00:06:30 -0000

On 1/6/22 4:48 PM, Peter Saint-Andre wrote:
> On 1/6/22 1:03 PM, Brian E Carpenter wrote:
> 
>> On 07-Jan-22 01:30, Eliot Lear wrote:
>>
>>> It may be helpful to restate Brian's text as follows:
>>>
>>>> Updates, amendments and refinements of this document can be produced
>>>> using the process documented here, but are only operative upon
>>>> agreement of the IAB and the IESG, and with no objections from the LLC
>>>> with regard to their ability to implement any proposed change.
>>
>> Yes, that scopes it correctly. For example, if a change unintentionally
>> required the LLC or its contractor to break GDPR or any other law, or
>> overspend its budget, this would catch it.
> 
> WFM.

Here's the same concept with some slight editorial tweaks:

Updates, amendments, and refinements to this document can be produced
using the process documented herein, but shall be operative only after
(a) obtaining the agreement of the IAB and the IESG, and (b) ensuring
that the IETF LLC has no objections regarding its ability to implement
any proposed changes.

Peter