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

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 31 March 2020 12:57 UTC

Return-Path: <jmh@joelhalpern.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 BB39F3A20AD; Tue, 31 Mar 2020 05:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level:
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 Sf50ua9wQ6Gd; Tue, 31 Mar 2020 05:57:01 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 9FF433A20AA; Tue, 31 Mar 2020 05:57:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 48s8VP43GRz6GB0Q; Tue, 31 Mar 2020 05:57:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1585659421; bh=rjtDg6kG36rBDvVNDo9a1/KweKrMCWH12ZeNBtbgTns=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=p4/DhLrcRW/Kof1/PJdvE+fWTM7QDLUlRdTAVBf/ohpKhr8Np+S7+JMQ11xbzGjyk YYmo8Dbm+5Qi+v2yzBoj4KWPQu75phx1p2lru0h3kEaaoIBcqIHy0QMVRCWAIJzkMe MGxm7bqppg8sUCmCuj+cSm8bu3ir1aBS8/drnk9Y=
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 48s8VN5TP2z6G81v; Tue, 31 Mar 2020 05:57:00 -0700 (PDT)
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
Cc: 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> <097a60d7-2229-b849-1ca3-1f6d298cceed@nthpermutation.com> <yblpncthb1n.fsf@w7.hardakers.net> <ad40f5c1-5551-3e3e-9bc3-164ec3368b68@gmail.com> <16726C73-09AB-4F61-8C00-8224E3EF6F1B@mnot.net> <E9B2BFA7-4EFE-4608-AB00-42B46C4503E7@cisco.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <326aa371-82ad-da59-d873-f4e08cd6c3bb@joelhalpern.com>
Date: Tue, 31 Mar 2020 08:57:01 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <E9B2BFA7-4EFE-4608-AB00-42B46C4503E7@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/x1OMhYw7Rm0fag_LGfCTdKUNpus>
Subject: Re: [Rfced-future] [IAB] 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: Tue, 31 Mar 2020 12:57:03 -0000

My take is that we can not focus as much as I would like.

We need to deal with the questions of the authority, responsibility, and 
role of the person we call the RFC Editor.  Differences in understanding 
of those aspects seem to have made a significant contribution to getting 
us into this mess.

To the degree possible, I would prefer that we not get into "what we 
want the RFC Series to be".  We probably do at least need to discuss the 
relationship of the RFC Editor to that discussion.  My preference is 
that we define the job such that it is clearly the RFC Editor's job to 
lead that discussion / process.

Yours,
Joel

On 3/31/2020 2:43 AM, Eliot Lear wrote:
> Hi again,
> 
> With apologies to Mark, he pointed out to me that I misinterpreted his 
> message.  Taking another swing.
> 
>> On 30 Mar 2020, at 23:03, Mark Nottingham <mnot@mnot.net 
>> <mailto:mnot@mnot.net>> wrote:
>>
>>> On 31 Mar 2020, at 7:37 am, Brian E Carpenter 
>>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
>>>
>>> what are the basic principles
>>> of the RFC series and its Editor's role? I'm not sure that has really 
>>> ever been
>>> properly written down as a separate "mission statement" or whatever.
>>
>>
>> One thing that occurred to me recently is that, while this program is 
>> defined with the following scope:
>>
>>> Discussion of changes to how the RFC Editor function is managed, 
>>> staffed, and overseen are all within scope.
>>
>> It isn't said whether discussion of the RFC Series itself (and 
>> potential changes to it) are in scope. Defining the principles of the 
>> series seems like it's more the latter than the former.
>>
>> Could we (Eliot?) come to some determination about whether the latter 
>> is in scope or not for this program? I suspect having that well 
>> understood -- either way it goes -- will help considerably.
> 
> To state the question in a slightly different way:
> 
>   * Should the program worry about the structure of the series or should
>     the program worry about putting in place someone who could lead the
>     community in worrying about the structure of the series (among other
>     things)? 
> 
> 
> A related question:
> 
>   * Should we establish a process that addresses series evolution over
>     time or should we leave that for later?
> 
> 
> I think these sorts of questions are good to sort out in advance so that 
> we know best how to direct our energies.
> 
> Eliot
> 
>>
>> Cheers,
>>
>> --
>> Mark Nottingham https://www.mnot.net/
>>
>> -- 
>> Rfced-future mailing list
>> Rfced-future@iab.org <mailto:Rfced-future@iab.org>
>> https://www.iab.org/mailman/listinfo/rfced-future
> 
>