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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 19 September 2020 02:02 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 0E9893A0F51 for <rfced-future@ietfa.amsl.com>; Fri, 18 Sep 2020 19:02:38 -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 jxIoV2Q38vJv for <rfced-future@ietfa.amsl.com>; Fri, 18 Sep 2020 19:02:36 -0700 (PDT)
Received: from mail-pl1-x643.google.com (mail-pl1-x643.google.com [IPv6:2607:f8b0:4864:20::643]) (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 76C963A0F14 for <rfced-future@iab.org>; Fri, 18 Sep 2020 19:02:36 -0700 (PDT)
Received: by mail-pl1-x643.google.com with SMTP id u9so3925644plk.4 for <rfced-future@iab.org>; Fri, 18 Sep 2020 19:02:36 -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; bh=v3uz9Wyn8ESKJGdp7NE8GTFcWm0O0vPjrC2R9sOqhS4=; b=fivZg9H/mxNAe1HMwLpIhatZ/Zn8yaCzmGX+z1ow9cpn5H78RJloG3V3VXsPT+j3U/ DByFgqImWrsTl9la4rXL04gpwv1CwptrnT+pEfg2gS4qBd8848t5jsB6/Zqy3qVckws0 07uNy03MDUBbk2R1EfCNx8fzxwnU3rizSypMpl+Qy/f+d0l35xvTiIBaQgB99R5KcWS/ vW4quFj8ecI9h3DwRPn8L3zafzuAmkfhqJJtk8bOgp8uC0wTPzQvEfcz7/Fy7Hznt4Uv NDhWIVDTKpiwG/FE3U+w+j2HAl3IqSSdJkbe2VSHzN6tKOFAlAcLCoyPCZtUyvcgQcV5 wbFw==
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; bh=v3uz9Wyn8ESKJGdp7NE8GTFcWm0O0vPjrC2R9sOqhS4=; b=iSZ7eDmw09suEM7lfneFKq1JaGXe3sMnVZwCCCoBwVMKacOxUuPax9Nx/kBC+rmRsl Dy1INlH/IVidoXVnawxxp29ai+7ezzKh3Od0NEWrkXFBfsEkMOkVTDr51KkEt7pw+Nrp r/raFqwEjXPX5n0fGWTrObh/T+Ev1uL0cu6DsRleUnxBwKPOYg+MwdzUGWd1j5gRefeQ hr1WIMhOnw3z3vX0By5c9G4EHJs2sgZ9PCciy3Z7w61hlLWC2A/bh+dOrsetdAMs4WQ3 iJXz2l4FmruRhFnSCozsvLJ7H9GObmZCkdQfPHgvM/oDHjW4IAZl9CUZEgNfvLWP6S8o xbjA==
X-Gm-Message-State: AOAM532nUrEAn8jIMUgUk6fycjgAXSuKvDIPPuuzQFJY3VV7Sz4f51a7 8d6vKl+/vJgXSzL20fRug7P1YQlCX/Q=
X-Google-Smtp-Source: ABdhPJxzCJo3GV6E1O/h8rG30UqiaLFUiw8ZahzW3d75jIubCiE0zUvioe8wu9semJMrCge1+1d/Bg==
X-Received: by 2002:a17:90b:617:: with SMTP id gb23mr14982656pjb.36.1600480955587; Fri, 18 Sep 2020 19:02:35 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.138.136]) by smtp.gmail.com with ESMTPSA id v21sm4364391pgl.39.2020.09.18.19.02.33 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Sep 2020 19:02:34 -0700 (PDT)
To: Eliot Lear <lear@cisco.com>, rfced-future@iab.org
References: <1FCE39CC-BE2D-4731-A74F-7763D9A9E8A6@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <abfed954-0a43-8cb9-2d3a-de412fca28f2@gmail.com>
Date: Sat, 19 Sep 2020 14:02:30 +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: <1FCE39CC-BE2D-4731-A74F-7763D9A9E8A6@cisco.com>
Content-Type: multipart/mixed; boundary="------------5B217E08980B31291C1A6C1E"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/e-sCH-_L2H9I3F29HY2pc896g7g>
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 02:02:38 -0000

Hi,

Before answering that, I wanted to better understand the discrepancies between the models. Loosely based on Eliot's charts, I built the attached Venn diagram. It's quite subjective, and it skips over many details and subtleties. Comments are very welcome (but space for extra text is very limited).

It's still a bit complex at first sight, but I think we could reduce the strategic questions to 5 or 6. My preference is to tackle that for a few weeks, before attempting to munge the drafts.

fwiw, the SVG file format is almost ready for inclusion in an I-D.

Regards
   Brian Carpenter

On 19-Sep-20 03:55, 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
> 
>