IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Tue, 31 March 2020 06:44 UTC

Return-Path: <lear@cisco.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 C23113A0DF9; Mon, 30 Mar 2020 23:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.7
X-Spam-Level:
X-Spam-Status: No, score=-7.7 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 u43_zpWvLlfU; Mon, 30 Mar 2020 23:44:04 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF2563A0DF6; Mon, 30 Mar 2020 23:44:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5794; q=dns/txt; s=iport; t=1585637044; x=1586846644; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=EZ4+DS3EXMuTzfNHdu+ZXvWuBuXoyJsSlQAtncmVpDw=; b=MiHMG/jSRNUPiCwrQvxJR1VUYHeg/9n4d5gpMM5dxArG4nmCFZjtCZTg olnrLuJuZEbDVCm1HojjVcBu/m4DQZ1m/e+fWZrWHbB/FjqKRGSXtpjX7 OxhSeN7KMaLJ4yl9suFVoBhkEprcxaDkgNf3+qvUfHmwC3fPbamL6fv6v Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BkAABI5oJe/xbLJq1mGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF7gXgFgRhUASASKo0ch2oliWyJUIgKCgEBAQwBARgBCgwEAQGERAKCVzgTAgMBAQsBAQUBAQECAQUEbYVWDIVwAQEBAQIBAQFsCwULCw4KLiEGMAYTFIMSAYJLAw4gD6xEgieFS4JUDYIaBoE4jEuCAIE4DBSCHy4+gh5JAYUqgiwEsChFgkeCVpADhD4WB48vjD+aa40BgzQCBAYFAhWBaSKBWDMaCBsVOyoBgkE+EhgNjikXgQQBDocWO4VDPwMwAo8LAQE
X-IronPort-AV: E=Sophos; i="5.72,327,1580774400"; d="scan'208,217"; a="24912389"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Mar 2020 06:44:01 +0000
Received: from [10.61.237.69] ([10.61.237.69]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 02V6hxfK021362 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 31 Mar 2020 06:44:01 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <E9B2BFA7-4EFE-4608-AB00-42B46C4503E7@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9BA02B10-B3BF-4529-8A44-517E293AF06E"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Tue, 31 Mar 2020 08:43:59 +0200
In-Reply-To: <16726C73-09AB-4F61-8C00-8224E3EF6F1B@mnot.net>
Cc: rfced-future@iab.org, Michael StJohns <msj@nthpermutation.com>, IAB <iab@iab.org>
To: Mark Nottingham <mnot@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: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.237.69, [10.61.237.69]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/b513ZNKlc-ZojMqXbqlgkYg9lfA>
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 06:44:07 -0000

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> 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.
> 
> 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
> https://www.iab.org/mailman/listinfo/rfced-future

v2.23.0 | Report a Bug | By Email