Re: [Rfced-future] Moving forward: Please state your preference

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 19 September 2020 21:35 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 98B043A0A70 for <rfced-future@ietfa.amsl.com>; Sat, 19 Sep 2020 14:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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.001, 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 TOx16KEoeTdH for <rfced-future@ietfa.amsl.com>; Sat, 19 Sep 2020 14:35:03 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 3C3CF3A0A6E for <rfced-future@iab.org>; Sat, 19 Sep 2020 14:35:03 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id x123so5782956pfc.7 for <rfced-future@iab.org>; Sat, 19 Sep 2020 14:35:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=Zgtzab/SpvsUSfKvYh0/FWd04o8G6ZKAss6wH0+lvWw=; b=LC+EbLPTwckTNFk2TowighG1fG2itYZ7H+iG7Zd1HyUr86Fwt5noH/DJTsKyKxhD31 /02gjBKIiISlLoxBI8GYQ85a8bg8hC+kCCzUJidsdaArd8yENqdGubN1Q++jj5nq53S4 0/CqSJEZ/JKd9xiJP2tUjHIENWGdz+jSWsDKc600T7L9EdP7tbarDnckyVInd5rf3ron 7+V7pMQGjQNjxC4LLcIU6yuED/sl56Q+hDT4xBMnOx5LLHET4WTJ9sctpCWo+znrRyA3 jpTwEkT6TfnT5vVoRHzdnRHjyBeZfent6Yz+E8gFeyuTjAIpI7RS7+ehHtjvkwI/B7zy WctA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; 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=Zgtzab/SpvsUSfKvYh0/FWd04o8G6ZKAss6wH0+lvWw=; b=U4nk0oUMwXGjKNwDf9HSJ7D/xXoxUKuz20NInDd2NPUOtwhYGwQZN9rqSvqiqmkzx1 dKjwTAE1eDGVZbpIWJI4ljGzgDg/DYdg87xbvZyRuGJMrmkzwRt24VkFIeKAhkPLR11Z G//gf3gfil3SABrbHgp88MZSsbznPzPWfQpmdXODtJQHF2f+1FElpPbpj5ZT1QiNxY6B VgztJRM2nLiF0/fFqjPn8tv7iNPZHBcb1rea7IJ4MuoHFQ+tlE8a++MEYAiZJ79CXVC5 RuBrjcu9TC8vvHplpzzONYFPZv92cR+JKRq78CzGpoZX36EkdXZ0ukQfx49mtaFtQu4C j9MA==
X-Gm-Message-State: AOAM532zlqo/EnU7O9GZDjwgtvNcPLpSXZxTZYLMsbdYqMsNt8szNBmy kirgqGleY2KhKZxxj+EMd+kAHxEnQR0=
X-Google-Smtp-Source: ABdhPJzk9oD7qyCKgImoA/ZeMLR5aNfQ7TQLQ+I1RCXP8Qg2DP5yVl6UeAVPm3Uy1xNFpzGoVHXfgQ==
X-Received: by 2002:a63:c74e:: with SMTP id v14mr9532710pgg.186.1600551302104; Sat, 19 Sep 2020 14:35:02 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.138.136]) by smtp.gmail.com with ESMTPSA id s8sm6559704pjn.10.2020.09.19.14.35.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 19 Sep 2020 14:35:01 -0700 (PDT)
To: Michael StJohns <msj@nthpermutation.com>, rfced-future@iab.org
References: <1FCE39CC-BE2D-4731-A74F-7763D9A9E8A6@cisco.com> <7399a374-7561-3b9e-2d04-07ade1a9174c@nthpermutation.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7ca155d7-ad8a-921c-6853-ce210a2f1a7d@gmail.com>
Date: Sun, 20 Sep 2020 09:34:56 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <7399a374-7561-3b9e-2d04-07ade1a9174c@nthpermutation.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/9ycE3fNrRlUNye8jssEwChw9A4Y>
Subject: Re: [Rfced-future] Moving forward: Please state your preference
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: Sat, 19 Sep 2020 21:35:05 -0000

> I've been trying to do a topological sort

That's exactly why I drew my Venn diagram...

Regards
   Brian Carpenter

On 20-Sep-20 05:13, Michael StJohns wrote:
> For the same reasons we discussed on the call, I choose option C - we're not ready to pick a path.   That looks closer to Option B than it does option A but probably actually isn't the same.  We've talked about common solution elements, but we're still having major discussions (cf John and and Adam's back and forth) about the implications of various choices such that picking solution elements are still quite difficult.  Among other things, many of the elements are entwined - e.g., choosing choice A of Group 1 may restrict your choices in Group 2 to choices C and F.
> 
> 
> As I read it we've agreed mostly on one thing:
> 
>   * That the stream managers will take a major role in the evolution process of the RFC Series.  
> 
> We seem to have also agreed that (I think this is what I got an agreement on from Martin and Brian when I asked the question on the call):
> 
>   * The LLC will be responsible for any contractual items including hiring/firing/renewals/day-to-day and that any delegation of that role will be only to a "fiduciary" of the LLC (e.g. employee or a contracted role) to specifically exclude the IAB/RSOC personnel management model.
> 
> We haven't agreed on:
> 
>   * Whether there will be a professional involved in the steering, or the model of engagement for that professional.  (e.g. employee or retained contractor with primary responsibility vs employee or retained contractor with advisory only responsibility or a professional contractor engaged only for task-specific short term items).
> 
>   * The model for publication of documents that drive the publication process.
> 
> And lots more.
> 
> I've been trying to do a topological sort and figure out which of the problems is the core one that we need to come to a conclusion on, and I'm at a loss.
> 
> Mike
> 
> 
> 
> On 9/18/2020 11:55 AM, Eliot Lear wrote:
>> Hello everyone,
>>
>>
>> “When you come to a fork in the road, take it.”
>> — Yogi Bera
>>
>> The chairs have had an opportunity to discuss the last interim.  We note that some people liked the comparison chart, as a means to highlight both similarities and differences.   We know that some people would very much like to have seen a draft adopted, while others were not ready to move forward.  Several people would instead like to go issue by issue and resolve those issues before adopting a draft.  The chairs will leave this choice to the group as to which way to proceed at the moment.
>>
>> You are invited to specify your preference *on list* *by September 25th, 2:00pm GMT.  Option A or Option B.  Please be explicit.*
>>
>> We can pursue one of two approaches:
>>
>> *Option A:  Pursue adopting a draft*
>>
>> The approach would be that we *would* adopt a draft by IETF 109 – *as a starting point*.  To avoid further deadlocks, there would be *no* “I’m not ready” option in the hum.  Authors are invited to merge and indicate open issues in drafts.  Others are invited, if they really feel the need, to create new drafts within 2-3 weeks.  If there are more than two options, the chairs will find ways to wheedle things down to get to a draft to adopt, while being sensitive to the concerns EKR and others raised about inertia of what is in a draft.  If the group would like an interim to facilitate this option, the chairs will accommodate.
>>
>> *Option B: Pursue open issues one by one*
>>
>> Pursue issues one by one to resolve on list, starting with “Do people believe that the RSE position should continue in some form?”  We would pursue from the nature of the role if we get an affirmative answer.  Other questions would follow, such as aspects of oversight and relationship to RPC.
>>
>> If after the poll the group is evenly divided between these choices, in order to take the fork, the chairs will spin a spinner and make a decision.  You are encouraged to discuss these options, and may change your minds right up to the deadline.
>>
>> *A Plea*
>>
>> This program consists nearly exclusively of senior members of the community-  you are all past or current leaders of this organization with deep experience and knowledge.  We therefore hope that you will seek to find common ground with one another when you see a deadlock in view.
>>
>> Brian and Eliot
>>
>>
> 
>