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

John C Klensin <john-ietf@jck.com> Mon, 30 March 2020 22:06 UTC

Return-Path: <john-ietf@jck.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 C69F53A143C; Mon, 30 Mar 2020 15:06:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 D-M5E9J905vt; Mon, 30 Mar 2020 15:06:01 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2655F3A1437; Mon, 30 Mar 2020 15:06:00 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jJ2Xc-000LKH-FQ; Mon, 30 Mar 2020 18:05:56 -0400
Date: Mon, 30 Mar 2020 18:05:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mark Nottingham <mnot@mnot.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: rfced-future@iab.org, Michael StJohns <msj@nthpermutation.com>, IAB <iab@iab.org>, Wes Hardaker <wjhns1@hardakers.net>
Message-ID: <F66FC1992F257AEC7843DC77@PSB>
In-Reply-To: <16726C73-09AB-4F61-8C00-8224E3EF6F1B@mnot.net>
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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/81O5uc9R9LFGF3gtuK7bDrAlhbY>
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: Mon, 30 Mar 2020 22:06:03 -0000


--On Tuesday, March 31, 2020 08:03 +1100 Mark Nottingham
<mnot@mnot.net> wrote:

>> On 31 Mar 2020, at 7:37 am, Brian E Carpenter
>> <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.

Mark, I can't parse "latter and former" in the above.
 
> 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.

Definitely.  

As two tests of the scope question, I may not have correctly
understood the proposals but, if I have, various people
including yourself have suggested that IETF Standards Track
documents (presumably including both technical and procedural
BCP) and possibly all IETF Stream documents either become living
documents or be restructured so that each one is complete onto
itself rather than, as is typical, normatively referencing a
collection of others.   Independent of the merits of those ideas
(and other issues with them), such a change might call for a
radically different structure of the RFC Editor Function and
probably a different role and set of qualifications for the RSE.


I have also heard it suggested that, in the absence of an
incumbent RSE, this would be the right time to split the Series
up into separately-numbered series for each stream or for the
IETF stream separate from the others.  That, too, might require
a different structure and/or a different set of qualifications
for the RSE.

So, would those two examples be in scope or not?

thanks,
   john