Re: [Rfced-future] [IAB] Welcome to the RFC Editor Future Development Program
Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 30 March 2020 21:24 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 1E7623A135E; Mon, 30 Mar 2020 14:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 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] autolearn=ham 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 T9RIeQ2hFfbf; Mon, 30 Mar 2020 14:24:11 -0700 (PDT)
Received: from mail-pg1-x543.google.com (mail-pg1-x543.google.com [IPv6:2607:f8b0:4864:20::543]) (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 162263A1345; Mon, 30 Mar 2020 14:24:11 -0700 (PDT)
Received: by mail-pg1-x543.google.com with SMTP id 142so9275550pgf.11; Mon, 30 Mar 2020 14:24:11 -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=/dV6icG4fFbX+Gzn5f9Lly94QSqpKY4TyiZTYoVipvg=; b=DSo7zfbUoOl/Z7Ot2P12l6CbX7s59mk37w724VZu6qkxcjsmeCMg0KJfyab/cr82r+ NMF+uHvHsGvxCWPJn4xQLrxD8q9YusOxovlA0imhJOn7iQb+rYKVWpLZIZzXRgOtvdDX hcTC68PQXHGfavW5nyH01oMh54BJctXL5FsscIvCuLKfE2e+BW2LyiLGlx7ixade+B2S Mf6R7VZmI/HmnaZBpaRIVZKWGhy/bod5nLr8pT1GiqvmVpIa0ggRtatzWGSsKVbjDOsM Kkr3NgQxOU8C3x2u0YmwE0z3v6O5hFIOs41tjhXqI5Wh7us96dy1SwmI2L2T/qKSkfYl Cf1w==
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=/dV6icG4fFbX+Gzn5f9Lly94QSqpKY4TyiZTYoVipvg=; b=nmmEuz+GDr1nCvc64rQ4zSrJDBd72/N9l2GBUPyLwyRy3PIrx2x8li2McZDdWAHfhH 9RpU0hjpV9mNv240r4m3OZp8HyTxMLPO9p7lgPh6cH/sRuvaOBM5DzECeBB+uZOUxeZq L3VRnf2C0J92zyGRD+LiGq1wCGUqMiwmBJLUvIqiogqi8Ox8q3KDxlYDy5RDqRPcZlbB RaPsFmiA6JGJNOK4NX1hpiwhIPXEqOzLtoNHXYBAEjhjkc4FDCsuHclejwQp5hag1zp1 GDWoyhdTtLvhJaYQHxBBt+3HFxyJ2TdQWN9l/OsEqzHziS21uGnuxkWDS8CvYsCTlDf1 wOjA==
X-Gm-Message-State: ANhLgQ3TxnBqPvleod+WSrTzW+mziBS+dZ0EfT8NtvpI8mcJbAd+RtgP Oz1UFZwDvWWW56/St1laJ54+tRq1
X-Google-Smtp-Source: ADFU+vt1g1XeYQ1s8ZqeCJshzJtg06M6hReOCYy3xt8O336pO4aJItZ0ZkJ6BBp8u8IRU0a31yED9w==
X-Received: by 2002:a63:ec44:: with SMTP id r4mr14074132pgj.425.1585603450326; Mon, 30 Mar 2020 14:24:10 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id t63sm10153641pgc.85.2020.03.30.14.24.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Mar 2020 14:24:09 -0700 (PDT)
To: Mark Nottingham <mnot@mnot.net>
Cc: Wes Hardaker <wjhns1@hardakers.net>, Michael StJohns <msj@nthpermutation.com>, 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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <86a4a270-6411-a817-6157-3b7932dd1918@gmail.com>
Date: Tue, 31 Mar 2020 10:24:06 +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: <16726C73-09AB-4F61-8C00-8224E3EF6F1B@mnot.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/_YQemF5ELA_vtJOM7mPvpohdQ7Y>
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:24:12 -0000
On 31-Mar-20 10:03, Mark Nottingham 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. Yes. What I should have added is that while it probably isn't our job to define the mission, if we don't have a common understanding of it, we are unlikely to converge on much of anything. Brian
- [Rfced-future] Welcome to the RFC Editor Future D… Eliot Lear
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Andrew G. Malis
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Eliot Lear
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Eliot Lear
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Michael StJohns
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Lucy Lynch
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Wes Hardaker
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Brian E Carpenter
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Wes Hardaker
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Mark Nottingham
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Brian E Carpenter
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Eliot Lear
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… John C Klensin
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Mark Nottingham
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Eliot Lear
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Joel M. Halpern
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Brian E Carpenter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Stephen Farrell
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Jari Arkko
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Adrian Farrel
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Stephen Farrell
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Adrian Farrel
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Mark Nottingham
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Brian E Carpenter
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… John C Klensin
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… John Levine
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Stephen Farrell
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Larry Masinter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Christian Huitema
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Joel M. Halpern
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Christian Huitema
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Michael StJohns
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Michael StJohns
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Brian E Carpenter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Larry Masinter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… jmh.direct@joelhalpern.com
- [Rfced-future] AUTH48 and editing before approval… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Larry Masinter
- Re: [Rfced-future] AUTH48 and editing before appr… Russ Housley
- Re: [Rfced-future] AUTH48 and editing before appr… Ted Lemon
- Re: [Rfced-future] AUTH48 and editing before appr… Russ Housley
- Re: [Rfced-future] AUTH48 and editing before appr… Ted Lemon
- Re: [Rfced-future] AUTH48 and editing before appr… Carsten Bormann
- Re: [Rfced-future] AUTH48 and editing before appr… Michael StJohns
- Re: [Rfced-future] AUTH48 and editing before appr… Eliot Lear
- Re: [Rfced-future] AUTH48 and editing before appr… Ted Lemon
- Re: [Rfced-future] AUTH48 and editing before appr… John C Klensin
- Re: [Rfced-future] AUTH48 and editing before appr… John Levine
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John Levine
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Andrew G. Malis
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John R. Levine
- [Rfced-future] Up level [Re: AUTH48 and editing b… Brian E Carpenter
- Re: [Rfced-future] AUTH48 and editing before appr… Russ Housley
- Re: [Rfced-future] AUTH48 and editing before appr… Christian Huitema
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Larry Masinter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John R. Levine
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Julian Reschke
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Carsten Bormann
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Joel M. Halpern
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Julian Reschke
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Julian Reschke
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John R. Levine
- Re: [Rfced-future] AUTH48 and editing before appr… John C Klensin
- Re: [Rfced-future] AUTH48 and editing before appr… Russ Housley
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Brian E Carpenter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Carsten Bormann
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John R. Levine
- Re: [Rfced-future] AUTH48 and editing before appr… John C Klensin
- Re: [Rfced-future] AUTH48 and editing before appr… Christian Huitema
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John Levine
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Mark Nottingham