Re: [Rfced-future] Welcome to the RFC Editor Future Development Program

Michael StJohns <msj@nthpermutation.com> Mon, 30 March 2020 17:28 UTC

Return-Path: <msj@nthpermutation.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 2E8843A08EB for <rfced-future@ietfa.amsl.com>; Mon, 30 Mar 2020 10:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level:
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=nthpermutation-com.20150623.gappssmtp.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 LSjU9nir53LD for <rfced-future@ietfa.amsl.com>; Mon, 30 Mar 2020 10:28:48 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 25C853A08C3 for <rfced-future@iab.org>; Mon, 30 Mar 2020 10:28:48 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id q188so19878806qke.8 for <rfced-future@iab.org>; Mon, 30 Mar 2020 10:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=msRwlnYrYVU3w5fqGVx54fQU03VCDygkB4CRohSxl+w=; b=WY7nAyZVL0wmGo+bT9oS3wmCQfdddayGayA1mk8sR5f34w6/M2rSt09QH2GKqpzSxZ BtmOpuF4XGYLZAKboEsOrtJpIo2e7KM+Uzf4MrnEtLxsuapxqCV6cROQB8FweeKd6G1J hB/+0UrNY9HCi4s5d9zdK6it+ZsKNlVKosB6r8KeUhvr2iEAv27nNoWrdYMnSpiL6k/T BEds5nYOmoSa1P/B+eJY8XHq80s4qE0MROQq5xWPEt7nHa7iFMkKx/06x5D1pUa2cis8 APDsNJKzNxxGSz151ongmq9Tnq9Kqz5KJEuVsfytYStws0DdsU0gEBZhUBMLoOzKfRKZ lyXQ==
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=msRwlnYrYVU3w5fqGVx54fQU03VCDygkB4CRohSxl+w=; b=pxVeMUpIC73pKRgBHntGkDbzawDYeUa/x4sEsOAsDksfL0rgHY7LmJVmDzQG9y6jBF tOjmKEBbZv4CL4RrAxCyBNPIwMFNKTBQh2GN32a54l5Ma1JbmA9td99rxg6tWrKpM65J Ki62WpWZRPwP4Fip7CLTm6u1+kS2koDubMZzi6z7ucUnHmq1p0EBEQOqQ4tHisNB+jnK 30BBatMl9KuyvgGFbdalR/C4eNv6IrtLVptyqDiKVgwyvPcgQHdJeXazshr2naJFXN+g LefPHKh1x1ufJq5Zk/dHzuh97OaCsrxHw+vmH2wqksaMU/XvRKqpKRSwj1WuQuWFmf8Q lMYA==
X-Gm-Message-State: ANhLgQ1e7vhVT6T+BTAh1696RkEPpFdMJTuHBOZ/zw/8IY0ttUaQz9Ml Otnpwkru3EkVz92u7oPykRS2SA==
X-Google-Smtp-Source: ADFU+vs030lD3nYEuYFco+Cy/zGwfC1BwXGueelmz4kTO2Vt9OqhduBGe7eZX2EWnTTToKZMXEFrdg==
X-Received: by 2002:a37:453:: with SMTP id 80mr1051984qke.325.1585589326849; Mon, 30 Mar 2020 10:28:46 -0700 (PDT)
Received: from [192.168.1.115] (pool-71-163-188-115.washdc.fios.verizon.net. [71.163.188.115]) by smtp.gmail.com with ESMTPSA id r207sm10805961qke.136.2020.03.30.10.28.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 30 Mar 2020 10:28:46 -0700 (PDT)
To: rfced-future@iab.org, IAB <iab@iab.org>
References: <97B63B78-0D49-4007-B8A2-101FB7849C0F@cisco.com> <CAA=duU0_pr_56HTR5vZg+AK981rkvGrMGFFi-UHgW4L=6=6mwg@mail.gmail.com> <D6A290EE-72E5-46A7-BA25-085CC2AAE35C@cisco.com> <0E6D83F8D11D8C1B9B7237B7@PSB> <73C27FFD-BD81-4CF3-9D9D-845DE9544A36@cisco.com>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <097a60d7-2229-b849-1ca3-1f6d298cceed@nthpermutation.com>
Date: Mon, 30 Mar 2020 13:28:45 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <73C27FFD-BD81-4CF3-9D9D-845DE9544A36@cisco.com>
Content-Type: multipart/alternative; boundary="------------F5F63A56A5F20D72F13C5755"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/a7BXqmsZoEGuuPHqy70iciFO_RI>
Subject: Re: [Rfced-future] Welcome to the RFC Editor Future Development Program
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: Mon, 30 Mar 2020 17:28:58 -0000

I agree with John that we should delay this, but not for the same 
reasons.  My reason is that the IAB has not completed its work.   The 
announcement (and the community agreement on which that announcement was 
made) indicated the requirement for at least two chairs to represent 
multiple points of view, as well as the appointment of a Liaison from 
the IAB. The appointment of a single chair does not satisfy the agreement.

If the IAB declines to appoint a second chair from the current 
volunteers, it should re-open the call for volunteers and arm twist 
until it gets sufficient volunteers. Until then, this program has not 
been formed.  Or at least that's my opinion, and I think an appeal 
indicating the IAB was not following its own rules would be successful.

On another point: In a different note Eliot indicated that he wanted a 
co-chair so that the IAB could replace him if he went off the rails.  
Again, working back to the community discussion hosted by Heather, this 
program is meant to be as independent as is feasible from the IAB.  Once 
appointed, the chairs should not fear replacement by the IAB unless 
there is sufficient public community urging to do so.

So I await eagerly the appointment of the second chair and I believe 
that Nevil would be an acceptable choice to most of us who are 
interested in that topic.  I also await the designation of the Liaison.

Later, Mike



On 3/30/2020 1:07 PM, Eliot Lear wrote:
> Hi John,
>
> Thanks for your comments.  Please see below.
>
>> On 30 Mar 2020, at 18:07, John C Klensin <john-ietf@jck.com 
>> <mailto:john-ietf@jck.com>> wrote:
>>
>> On a slightly different topic, the issues associated with the
>> 2020-2021 Nomcom and what, if any, changes are needed to the
>> eligibility requirements for the future are still very active on
>> the IETF and eligibility-discuss lists (in addition to many
>> other issues, of course).  For those of us who can only put in a
>> limited number of hours a week on IETF-related work, paying
>> careful attention to both sets of threads might be nearly
>> impossible.  Much as I hate to see this process delayed, would
>> it be sensible to postpone active discussions here for a week or
>> two in the hope that the other ones will settle down?
>
>
> I appreciate your desire to take the time necessary to understand 
> others’ views, and to contribute in a meaningful way, and that you 
> have time pressures, as I am sure we all do.  Thank you for having 
> chimed in with your views; it is now for others to do so.  If this 
> list volume really becomes a problem, please do let me know.
>
> Eliot
>
>