Re: [Rfced-future] Scope and IETF 108 proposals
Nevil Brownlee <nevil.brownlee@gmail.com> Sat, 27 June 2020 03:01 UTC
Return-Path: <nevil.brownlee@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 1DF4F3A097F for <rfced-future@ietfa.amsl.com>; Fri, 26 Jun 2020 20:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 t1J_wFGSde0o for <rfced-future@ietfa.amsl.com>; Fri, 26 Jun 2020 20:01:37 -0700 (PDT)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (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 51AF93A097B for <rfced-future@iab.org>; Fri, 26 Jun 2020 20:01:37 -0700 (PDT)
Received: by mail-vs1-xe2a.google.com with SMTP id s18so6513035vsi.6 for <rfced-future@iab.org>; Fri, 26 Jun 2020 20:01:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=er4kgAjF5Bnvdko8AH8Xqv+9e+IVQs2HN4Bq3BmVRuU=; b=EBWQw0osc/ruVBpIM6I4/UtCWxPkqWUub4qKnuH4KfgLB/PNDSmZCyjVrgh8je6pkA cIs7Efd0oH3nSkr/6zjmNzrsfSWeuUVKL5IwOE18+PMy+057JDchLgFOLm1IxUtNZaDe 2IGUgGuSPdmqO+T5d1w1rMLnvY8e0bWDHDMYkd7XaCXzMD699xYV56LP6xFqrzq9yobl OFj1IB8Y848M+SqmidnrjXYivhalqc1TAHaV3Nn/WRvOm27YNUy7L0UApLMVe9N4QbdS VUyhhmTZxUmH98ohO8PEKJen1I/J88R64o2BqjVKFBQyDSMTBuasFFD3MBOkbJYCzMK7 xyIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=er4kgAjF5Bnvdko8AH8Xqv+9e+IVQs2HN4Bq3BmVRuU=; b=j+a/GM4pi9waq71UEkc6QyzGh0zC+7Y0uphNlXLZ2kqziB9bp+FTcrf5eg3P/oNVDj CCE9i8vcCW7dyngXmsnyrXdiKHp56tjJNUzQljVkLkm8V635lgCziPIK4yRf+yht4D+E mAbt++rPNDe19KAiJD31bYWAEG+AEiBODzG2eGD+pVrkcyquKRi73dg3ui1WceadMOVE lJiHQCssXBJ95KwxGVbUZ67R0ksLBsQMrCY2wJJcjuyfTfKUemb9OwLNEJoRsCdwxxLN rgnAaVV4D56ImYrNAOccMSi5JCQ/YGtA3JuwnWc+daWB6FDFylvaO48cfn8XGyhX+Ib5 c9WQ==
X-Gm-Message-State: AOAM531mQtFdw98bo8Y6VJ/Kt4y+P+xrsQ7TumXru5lRNoWVO1v+g5E4 1m0ohCr6ckUqXCf+gGjrRpmrLoWpvKVREmfEerBcffMF41Y=
X-Google-Smtp-Source: ABdhPJwVdlQi7Abk5p1DIstmIkgPBgW+3/cSsOlwqynItpF3ySUIu/ENOuv12gpojMDAuKfnV3J2lpXgke7ObQY+UaQ=
X-Received: by 2002:a67:6812:: with SMTP id d18mr4876671vsc.227.1593226896341; Fri, 26 Jun 2020 20:01:36 -0700 (PDT)
MIME-Version: 1.0
References: <62A4C70D-419A-4DE3-8A54-60EB2B064EF2@brianrosen.net> <8c626e3e-1700-46fe-90b3-26b9c1296788@www.fastmail.com> <1b6cf5e6-2c16-d839-08dd-d005d4fdbc60@gmail.com> <3678427d-6496-45c7-bd1b-14d7f860c971@www.fastmail.com>
In-Reply-To: <3678427d-6496-45c7-bd1b-14d7f860c971@www.fastmail.com>
From: Nevil Brownlee <nevil.brownlee@gmail.com>
Date: Sat, 27 Jun 2020 15:01:09 +1200
Message-ID: <CACOFP=iAzB+hrtZcu4yaDv9mpmxSybGTc-cugWC2Hv==-zTTdg@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: rfced-future@iab.org
Content-Type: multipart/alternative; boundary="00000000000033fd0205a9080bf1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/BzOJI09f-U_wSwVhPzyWkfImjX0>
Subject: Re: [Rfced-future] Scope and IETF 108 proposals
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: Sat, 27 Jun 2020 03:01:39 -0000
Hi Martin: I've updated my Internet Draft to include a suggestion of what an RSEB (RFC Series Editorial Board) could be structured. Take a look at https://www.ietf.org/id/draft-brownlee-rfc-series-and-rse-changes-01.html Of course, any suggestions for changes/improvements/etc to that draft are welcome :-) Cheers, Nevil On Thu, Jun 25, 2020 at 11:43 AM Martin Thomson <mt@lowentropy.net> wrote: > On Thu, Jun 25, 2020, at 07:09, Brian E Carpenter wrote: > > On 24-Jun-20 19:54, Martin Thomson wrote: > > > We don't need a single person (or contracted entity, if that includes > more than one person) to be given the task of determining strategy. If we > need a strategy to serve our community, then maybe that community should > setting and owning that strategy. Not indirectly, via an appointed > custodian, but directly. > > > > I don't understand how that would work in the absence of a group and a > > group leader to determine what the community is (since it's not the > > IETF) and what the community's rough consensus is. Who would they be? > > In my book, the RSE and the RFC Series Board. > > I don't think that is necessarily the case. > > The process that we're following has the same requirements and > challenges. It has leadership. Two leaders in fact, which is more than > twice as good as relying on a single person. It has open participation. > (I don't know what RFC Series Board is, but it implies a closed group, just > as RSE implies an individual.) > > Speaking strictly about strategy, the structure of what we have here is > just about as good as we will get in all the ways that matter. > > -- > Rfced-future mailing list > Rfced-future@iab.org > https://www.iab.org/mailman/listinfo/rfced-future > -- ----------------------------------- Nevil Brownlee, Taupo, NZ
- [Rfced-future] Scope and IETF 108 proposals Brian Rosen
- Re: [Rfced-future] Scope and IETF 108 proposals Michael StJohns
- Re: [Rfced-future] Scope and IETF 108 proposals Eliot Lear
- Re: [Rfced-future] Scope and IETF 108 proposals Bob Hinden
- Re: [Rfced-future] Scope and IETF 108 proposals Adrian Farrel
- Re: [Rfced-future] Scope and IETF 108 proposals Christian Huitema
- Re: [Rfced-future] Scope and IETF 108 proposals Bron Gondwana
- Re: [Rfced-future] Scope and IETF 108 proposals Bron Gondwana
- Re: [Rfced-future] Scope and IETF 108 proposals Michael StJohns
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Wes Hardaker
- Re: [Rfced-future] Scope and IETF 108 proposals John Levine
- Re: [Rfced-future] Scope and IETF 108 proposals Stephen Farrell
- Re: [Rfced-future] Scope and IETF 108 proposals Jay Daley
- Re: [Rfced-future] Scope and IETF 108 proposals Ted Lemon
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals S Moonesamy
- Re: [Rfced-future] Scope and IETF 108 proposals Martin Thomson
- Re: [Rfced-future] Scope and IETF 108 proposals Brian Rosen
- [Rfced-future] "oversees" [was Scope and IETF 108… Brian E Carpenter
- [Rfced-future] hiring [Scope and IETF 108 proposa… Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] "oversees" [was Scope and IETF… Peter Saint-Andre
- Re: [Rfced-future] Scope and IETF 108 proposals Martin Thomson
- Re: [Rfced-future] "oversees" [was Scope and IETF… Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Colin Perkins
- Re: [Rfced-future] Scope and IETF 108 proposals Eliot Lear
- Re: [Rfced-future] Scope and IETF 108 proposals Colin Perkins
- Re: [Rfced-future] "oversees" [was Scope and IETF… S Moonesamy
- [Rfced-future] Publication vetos [Scope and IETF … Brian E Carpenter
- Re: [Rfced-future] "oversees" [was Scope and IETF… Brian E Carpenter
- Re: [Rfced-future] Publication vetos [Scope and I… Lars Eggert
- Re: [Rfced-future] Publication vetos [Scope and I… Russ Housley
- Re: [Rfced-future] Publication vetos [Scope and I… Russ Housley
- Re: [Rfced-future] Publication vetos [Scope and I… Lars Eggert
- Re: [Rfced-future] Publication vetos [Scope and I… Brian E Carpenter
- Re: [Rfced-future] Publication vetos [Scope and I… Russ Housley
- Re: [Rfced-future] Publication vetos [Scope and I… Scott O. Bradner
- Re: [Rfced-future] Publication vetos [Scope and I… Larry Masinter
- Re: [Rfced-future] Scope and IETF 108 proposals Nevil Brownlee
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Martin Thomson
- Re: [Rfced-future] Scope and IETF 108 proposals Joel M. Halpern
- Re: [Rfced-future] Scope and IETF 108 proposals Michael StJohns
- Re: [Rfced-future] Scope and IETF 108 proposals Mark Nottingham
- Re: [Rfced-future] Scope and IETF 108 proposals Martin Thomson
- Re: [Rfced-future] Scope and IETF 108 proposals Mark Nottingham
- Re: [Rfced-future] Scope and IETF 108 proposals Jay Daley
- Re: [Rfced-future] Scope and IETF 108 proposals Eric Rescorla
- Re: [Rfced-future] Scope and IETF 108 proposals John Levine
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Christian Huitema
- Re: [Rfced-future] Scope and IETF 108 proposals S Moonesamy
- Re: [Rfced-future] Scope and IETF 108 proposals Martin J. Dürst
- Re: [Rfced-future] Scope and IETF 108 proposals S Moonesamy
- Re: [Rfced-future] Scope and IETF 108 proposals Martin J. Dürst
- Re: [Rfced-future] Scope and IETF 108 proposals Eric Rescorla
- Re: [Rfced-future] Scope and IETF 108 proposals Eric Rescorla
- Re: [Rfced-future] Scope and IETF 108 proposals Christopher Wood
- Re: [Rfced-future] Scope and IETF 108 proposals Eliot Lear
- Re: [Rfced-future] Scope and IETF 108 proposals John Levine
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Eric Rescorla
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Larry Masinter
- Re: [Rfced-future] Scope and IETF 108 proposals Joel M. Halpern
- Re: [Rfced-future] Scope and IETF 108 proposals Eric Rescorla
- Re: [Rfced-future] Scope and IETF 108 proposals John R. Levine
- Re: [Rfced-future] Scope and IETF 108 proposals Mark Nottingham
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] "oversees" [was Scope and IETF… Nico Williams
- Re: [Rfced-future] "oversees" [was Scope and IETF… Brian E Carpenter
- Re: [Rfced-future] "oversees" [was Scope and IETF… Jay Daley
- Re: [Rfced-future] "oversees" [was Scope and IETF… Nico Williams
- Re: [Rfced-future] "oversees" [was Scope and IETF… Christian Huitema
- Re: [Rfced-future] "oversees" [was Scope and IETF… Michael StJohns
- Re: [Rfced-future] "oversees" [was Scope and IETF… Christian Huitema
- Re: [Rfced-future] "oversees" [was Scope and IETF… Nico Williams
- Re: [Rfced-future] "oversees" [was Scope and IETF… Nico Williams
- Re: [Rfced-future] "oversees" [was Scope and IETF… Christian Huitema
- Re: [Rfced-future] Scope and IETF 108 proposals Eliot Lear
- Re: [Rfced-future] "oversees" [was Scope and IETF… S Moonesamy
- Re: [Rfced-future] Scope and IETF 108 proposals Eric Rescorla
- Re: [Rfced-future] "oversees" [was Scope and IETF… Eric Rescorla
- Re: [Rfced-future] Scope and IETF 108 proposals Eliot Lear
- Re: [Rfced-future] "oversees" [was Scope and IETF… Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Mark Nottingham
- Re: [Rfced-future] Scope and IETF 108 proposals Martin Thomson
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Martin Thomson
- Re: [Rfced-future] Scope and IETF 108 proposals Carsten Bormann
- Re: [Rfced-future] Scope and IETF 108 proposals Eliot Lear
- Re: [Rfced-future] Scope and IETF 108 proposals Carsten Bormann
- Re: [Rfced-future] Scope and IETF 108 proposals Brian Rosen
- Re: [Rfced-future] Scope and IETF 108 proposals Carsten Bormann
- Re: [Rfced-future] Scope and IETF 108 proposals Ted Lemon
- Re: [Rfced-future] Scope and IETF 108 proposals Adrian Farrel
- Re: [Rfced-future] Scope and IETF 108 proposals Carsten Bormann
- Re: [Rfced-future] Scope and IETF 108 proposals Ted Lemon
- Re: [Rfced-future] Scope and IETF 108 proposals Carsten Bormann
- Re: [Rfced-future] Scope and IETF 108 proposals Eliot Lear
- Re: [Rfced-future] Scope and IETF 108 proposals Ted Lemon
- Re: [Rfced-future] Scope and IETF 108 proposals Carsten Bormann
- Re: [Rfced-future] Scope and IETF 108 proposals Christian Huitema
- Re: [Rfced-future] Scope and IETF 108 proposals Eric Rescorla
- Re: [Rfced-future] Standing behind the RPC (was: … Adrian Farrel
- [Rfced-future] Standing behind the RPC (was: Scop… Jay Daley
- Re: [Rfced-future] Scope and IETF 108 proposals John Levine
- Re: [Rfced-future] Standing behind the RPC Brian E Carpenter
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Standing behind the RPC (was: … Jay Daley
- Re: [Rfced-future] Scope and IETF 108 proposals Larry Masinter
- Re: [Rfced-future] Scope and IETF 108 proposals Brian E Carpenter
- Re: [Rfced-future] Standing behind the RPC (was: … Eliot Lear
- Re: [Rfced-future] Standing behind the RPC (was: … Adrian Farrel
- Re: [Rfced-future] Standing behind the RPC (was: … Eliot Lear
- Re: [Rfced-future] Standing behind the RPC (was: … Adrian Farrel
- Re: [Rfced-future] Standing behind the RPC (was: … John Levine
- Re: [Rfced-future] Standing behind the RPC Brian E Carpenter
- Re: [Rfced-future] Standing behind the RPC Martin Thomson
- Re: [Rfced-future] Standing behind the RPC Eric Rescorla
- Re: [Rfced-future] Standing behind the RPC Michael StJohns
- Re: [Rfced-future] Standing behind the RPC Eric Rescorla
- Re: [Rfced-future] Standing behind the RPC Jay Daley
- Re: [Rfced-future] Standing behind the RPC Brian E Carpenter