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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 31 March 2020 20:10 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 CA1713A02BD; Tue, 31 Mar 2020 13:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 jO5OG6sIHTiW; Tue, 31 Mar 2020 13:10:05 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 983BB3A060D; Tue, 31 Mar 2020 13:10:01 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id k191so10861349pgc.13; Tue, 31 Mar 2020 13:10:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=XLa54h+UB6X7BxfPXvceW85cDKQPaAL4te2mbzaHJDY=; b=QmThyFXSSXUUKb8MAAv/4Na4z0LWIgj8s8nJaS4LY+qJKUj5KVilXG7cQNcJLcOWrA SEvcsS4KFBOfQkSwota4hpXoezkaL7HSqSQB/M3d6N9F/UnQlnkwVCW06i9kswQpqbnd m5NJz5Lx3ZSlZonJHJfs3CsARCpfbdl7V9Q5zpa3DE0zWGwbIUIoCCQOrksHSzsBBxCB 7I8aOLemgF/1VVhg/Gx89u9+hfQIGPpHYYBeP5zyHwU5lLEihRzdDX1QBr1cf2V47TXP JBR9CfWpfKqba7Q8j/+Kq/Bxg8TaOoq/PnpB9X9MYPMvm26ut2zM56XOgHYYwe29PtyG klYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=XLa54h+UB6X7BxfPXvceW85cDKQPaAL4te2mbzaHJDY=; b=BYRyTMCjOgNC8acLfTFeZkuhblzEGGpHbdmOmDaNbn/JVBO9G8HE0ftk3J9R50ugQt kx0LBl1kzRew51apRS0lwaz8gi4zd6P8c9DMK/fHkDN6mIy42tDOv6cDeI/b4+w4sB4F NakWe8aLD/rGHck6MfdDY0nRJD1Tu8gpqNDAMCnX1fA45KgvnJNFkrQlQu0OWvh+KsVy 7NYCKNkwXZVKDwHDM0iv63VQEtxhCTM3RjxB5e/Dbj3bkJgi35qTNHY+zET6slswS273 tlB+qdWufIoMUExdEPIwjuvLLlE5yj4M3XlKWf3bm6H51UqJ9fAg9EizscFuWpmwSD3U nGnA==
X-Gm-Message-State: AGi0PuYQdAaz70GJoAOwyo0T+j1+6NPlaNrEp7k71CUkmbwnsyEfSHfF oYVDhrMRGpkw+PXMjivD0PYLrdY1
X-Google-Smtp-Source: APiQypJIR5FxHytT2cihs7zvbkC3ZSWsDChtSWs2aoE8yeXDse2Iox32tBw5LeL4jpaZV4Iy7l7VJQ==
X-Received: by 2002:a62:2b06:: with SMTP id r6mr8498313pfr.249.1585685400357; Tue, 31 Mar 2020 13:10:00 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id l18sm8832671pgc.26.2020.03.31.13.09.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Mar 2020 13:09:59 -0700 (PDT)
To: "Joel M. Halpern" <jmh@joelhalpern.com>, 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> <326aa371-82ad-da59-d873-f4e08cd6c3bb@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0934cdca-7ff4-f43e-2e5f-66ed2939232f@gmail.com>
Date: Wed, 01 Apr 2020 09:09:55 +1300
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: <326aa371-82ad-da59-d873-f4e08cd6c3bb@joelhalpern.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/-IKxEKbv1k_ujWYGk950DicYem0>
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 20:10:12 -0000

Joel,

>  My preference is 
> that we define the job such that it is clearly the RFC Editor's job to 
> lead that discussion / process.

I very strongly agree with that, but to my mind that requires that we agree
on the principle that the RFC Editor is autonomous and the series is not
controlled by the IETF or, except at a very abstract level, by the IAB.

Regards
   Brian Carpenter

On 01-Apr-20 01:57, Joel M. Halpern wrote:
> 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
>>
>>
>