IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Mon, 30 March 2020 21:40 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 794663A1388; Mon, 30 Mar 2020 14:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.701
X-Spam-Level:
X-Spam-Status: No, score=-7.701 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, 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 mDAgfcwJEztU; Mon, 30 Mar 2020 14:40:20 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC64C3A137E; Mon, 30 Mar 2020 14:40:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1419; q=dns/txt; s=iport; t=1585604420; x=1586814020; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=dAwZ8NUqwu3t40ILu0hxkbtyWRguOBVnfthn+v2kHqo=; b=XPT6OF1KVp1V/nY1bThe9sNgC42a+7L0kOCj1XH3GpzYhOkHA7BoTrQv CZ2xxiywpbNN4oDXQbk+wXaQbfa8WeR87RvekD2B0bDrKXnaxFBN8LDxQ mBRKXohtELp6txVCm5nd/RhhmxDlN7vzt7dwpWfbou3fdaEcgKDEch38N g=;
X-IPAS-Result: A0BbAACAZoJe/xbLJq1mGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF7hAoSKoQaiQKIDoltkVsKAQEBDAEBLwQBAYREAoJWOBMCAwEBAQMCAwEBAQEFAQEBAgEFBG2FYoVwAQEBAQIBI1YFCwsOCgICJgICITYGE4MmgkwDDiCtHXWBMoVLgkkNgiCBDiqMS4IAgTgggh8uPoIegjCDEjKCLASwIEWCRoJWkAGEPh2PLow+mmeNAYM0AgQGBQIVgWkigVgzGggbFWUBgkE+EhgNjikXjic/AzACj0UBAQ
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.72,325,1580774400"; d="scan'208";a="22582955"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Mar 2020 21:40:17 +0000
Received: from [10.61.237.69] ([10.61.237.69]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 02ULeGxe020307 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 30 Mar 2020 21:40:17 GMT
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <16726C73-09AB-4F61-8C00-8224E3EF6F1B@mnot.net>
Date: Mon, 30 Mar 2020 23:40:16 +0200
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, rfced-future@iab.org, IAB <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <645A58A0-1E68-4CEC-B4AE-4ABBA838BC0B@cisco.com>
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>
To: Mark Nottingham <mnot@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-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/u7KbigsUzAfWrgbDZZUhs4ph8yo>
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 21:40:22 -0000

Hi Mark,

> 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.
> 

That’s a good point, but perhaps it also depends on just how much influence the RFC Editor is meant to have on the series versus other bodies.


> 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.


Do people agree with Mark?

What is important to me is that we have an agreed basis for how to proceed with the discussion.  That’s something that I would like to nail down Real Soon Now.

Eliot

v2.23.0 | Report a Bug | By Email