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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 06 January 2022 20:03 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 99A763A15A1 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 12:03:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.813
X-Spam-Level:
X-Spam-Status: No, score=-2.813 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9cGPuB5XrGQW for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 12:03:48 -0800 (PST)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 900833A15A0 for <rfced-future@iab.org>; Thu, 6 Jan 2022 12:03:48 -0800 (PST)
Received: by mail-pf1-x436.google.com with SMTP id m1so3403530pfk.8 for <rfced-future@iab.org>; Thu, 06 Jan 2022 12:03:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=EFKxsJiN1HLPY7uk1jSmTv/aFlxDn1Gqrweu+OnaTU0=; b=NlOFPy/Lp5sYmjBW7wnV5EdCglzB9ihpx5siIp/kMEuTeQTD0QqEfrN2Q0sGBzLyit rNPhcfSR6gXsabWj+svryA4M8t28UImh3JBp2ltids+p4UtUvmydmozm/1U3ihjRxaNJ oGly8jIcmvT2xrVX6G9Mq7/IRn+I8WZoo9ueIYoO6xM9F9mSKl6dCIlupALhsjA2v3YD hJ7kVJKkmDprURMLCyIJMlAFMGnHsHfbTZhMamzT1pLh/2UZjOF6yDqUl8MK4DMNcb4B 4kCL9aOA4UTp7tVDGBE4M2vUcmGYvq3NARkUcGXT7OLIoRZNPqEiyppW5V42bQIDxk+2 xJEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=EFKxsJiN1HLPY7uk1jSmTv/aFlxDn1Gqrweu+OnaTU0=; b=KjHEhd/QDHDCSoZMw3TtU0XaBPn+eOqBKtCxruOPfw2HZynB286tyKguCnPYjtt0lJ XLVntZB4Il5zrmxarVKuhB3sIhHTewGbbIkujxhLV97yL88idmnQHp/7stCKpNMOTe8g 9477xpRk9UvzQj/FgabL6ZATpGiDmug5lQ3TwW1gTlnJYEHWg003GSfXxn1qCYzYAxn1 BjwHZ+s1iTmENow+GUBLtSc9ceBnB4jgdZCFW0fpo8X5jFEqM2d3gzFOE87RoMqX+SWv 0kJh+yipG4ByXOlQFN1pTvLyMre8aCKHf0y2UNdfiECwm8aixyzE/WOyLK5zwshtI86f PUxA==
X-Gm-Message-State: AOAM533xoJr4OycVgq4yPvhCJWdWdenUkudA3dkGZVQnOq/UW3JRwSVD YblXfA8FUWSXVlqG0E6Se7tFHA/hN8y2jw==
X-Google-Smtp-Source: ABdhPJx8OvJvkmuvTbXSQ7p86zVYHwXwLrgq1MMQRV4nqfZE815qdrWwZiDFZhjZZyhoJJM+0qG8Aw==
X-Received: by 2002:a05:6a00:198e:b0:4bb:2522:56b9 with SMTP id d14-20020a056a00198e00b004bb252256b9mr61788156pfl.22.1641499426389; Thu, 06 Jan 2022 12:03:46 -0800 (PST)
Received: from ?IPv6:2406:e003:1071:1701:db7:d041:a2d:ce65? ([2406:e003:1071:1701:db7:d041:a2d:ce65]) by smtp.gmail.com with ESMTPSA id 17sm2657679pgt.6.2022.01.06.12.03.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 Jan 2022 12:03:45 -0800 (PST)
To: Eliot Lear <lear@lear.ch>, Michael StJohns <msj@nthpermutation.com>, 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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <6680efce-880a-1c58-518b-3b4e78a30360@gmail.com>
Date: Fri, 07 Jan 2022 09:03:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <9c12a079-5b4a-5b1a-6fd0-f01c6ed05b94@lear.ch>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ePKsJGcAMxY3NI2vnFEiVvcGZHg>
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: Thu, 06 Jan 2022 20:03:53 -0000

Comment below...


On 07-Jan-22 01:30, Eliot Lear wrote:
> We didn't quite close on this issue.  There are three candidates:
> 
> Mark's text:
> 
>> Updates, amendments and refinements of this document can be produced
>> using the process documented here, but are only operative upon
>> agreement of the IAB, the IESG, and the IETF LLC. Note that this does
>> not preclude such changes from being defined outside this process, so
>> long as the same agreement is found.
> 
> Mark's 2nd sentence provides a backstop to address any process failures
> that could happen either in the RSWG or RSAB.  This specifically
> addresses an issue that Mike raised at one point.
> 
> Mirja's text:
> 
>> "Updates, amendments and refinements of this document require
>> agreement of the IAB, the IESG, and the IETF LLC."
> 
> And Brian's text:
> 
>> Updates, amendments and refinements of this document can be produced
>> using the process documented here, but are only operative upon
>> agreement of the IAB, the IESG, and the IETF LLC
>> with regard to matters falling under their respective remits.
> 
> Brian's text came about as part of a discussion as to whether the LLC
> should have an approval role here.
> 
> I am a little unsure as to how that would be implemented.   How would
> you as an IAB/IESG/LLC member interpret that sentence? Could a NO vote
> be appealable as to whether something is outside a remit of an org?  
How
> about a YES vote?  Could that be appealable?  And how would one know why
> someone is voting as they do?
> 
> 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.

    Brian


> 
> The analogy here might be that of an IANA considerations section, where
> IANA reviews and clears a document.
> 
> ?
> 
> Eliot
>