Re: [Rfced-future] Issue 144

Eliot Lear <lear@lear.ch> Thu, 06 January 2022 21:09 UTC

Return-Path: <lear@lear.ch>
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 EE0913A1691 for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 13:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level:
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 1SXlSIWMcyMb for <rfced-future@ietfa.amsl.com>; Thu, 6 Jan 2022 13:09:19 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C49773A1690 for <rfced-future@iab.org>; Thu, 6 Jan 2022 13:09:18 -0800 (PST)
Received: from [192.168.0.131] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 206L9DwK036195 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 6 Jan 2022 22:09:14 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1641503354; bh=4D74GqldrVOxS+ypVxIdo9EuahwpQ0oBOTij14LqyV4=; h=Date:Subject:To:References:From:In-Reply-To:From; b=pMfyiTqJD8c6pwCO1gIIY1VHWvU6+sHP17ihjqhjWOJ7GD8ddewjYnefLTse3OVF8 DgYQee92NLRYBo/ynaOTnO5aYP2cfxuj2Ms9nTSJ6wIRB9eZgizbGlcjlB6c1I90qB 6hLUZcCEOYcqzmC/2R5nICGP2Q+OHoEYxT69mL6s=
Message-ID: <68cd6e6f-b0bd-a980-f38d-65dce206d23b@lear.ch>
Date: Thu, 06 Jan 2022 22:09:12 +0100
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
To: John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, rfced-future@iab.org
References: <CABcZeBO3-q+SMTFNZyeC50eghFs1CJNSLojmr1Zip1g_nsGZHQ@mail.gmail.com> <d7ce7879-2324-69d1-0770-e104aff6c68c@stpeter.im> <53497e97-ed65-93c8-5f4c-3f4ee9943501@stpeter.im> <FBE56AF3-8E2A-43D1-920B-F3F1EA6C6CD4@sobco.com> <8F21BC41-404A-4007-8436-AE2506C6A0A2@akamai.com> <CABcZeBNcuywBJfHAbL_5GYgLp6t+-pWWBbuCZKnQzqjp7BYxNg@mail.gmail.com> <DC6F136A-8FC4-4A6F-B42A-ED8BE3544999@akamai.com> <CABcZeBOGPsA7WmBcw_NwjLa60G1_8F0ZW4YzNNeyLy3rLNOhiw@mail.gmail.com> <D4D84AE9-17B2-4961-88B7-EE53FF4489E5@akamai.com> <7dc741bb-728e-c53b-2987-39318df38842@gmail.com> <BDA5471982A04903F9E0B0B9@PSB>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <BDA5471982A04903F9E0B0B9@PSB>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------JK0ubXZHOqVFH0yDlUFx0XVB"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/JNx-imX-E74H9u0qx3HgUH946K0>
Subject: Re: [Rfced-future] Issue 144
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 21:09:22 -0000

I think this issue is more about a starting point.  We've already said 
the group could set its own modalities, b



On 06.01.22 21:52, John C Klensin wrote:
>
> --On Friday, January 7, 2022 09:08 +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
>> On 07-Jan-22 06:12, Salz, Rich wrote:
>>> *>* I suspect others may feel differently in that they don't
>>> want this to be subject to changed IETF policies.
>>>
>>> I'd really like to hear from people who feel this as to
>>> what and why. I was just assuming this is like a WG in its
>>> behavior, and perhaps my assumption is completely wrong.
>   
>> No, but it *isn't* an IETF WG and should be able to opt out of
>> an IETF rule change that isn't appropriate. Analogy: each RFC
>> stream decides its own IPR policy; the fact that streams have
>> so far decided to follow the IETF policy doesn't change that
>> independence.
> Right.  But those streams have each made affirmative decisions
> to do so, more or less on a policy by policy basis.

So have we.  Group modalities have been discussed in great detail over a 
number of issues.  This issue was about whether we overly constrained 
meeting scheduling.  There seems to be consensus on call by value to 
relax the text slightly so that chairs can do meeting scheduling.  
That's pretty much it.

Eliot