Re: [Rfced-future] Scope and IETF 108 proposals
Jay Daley <jay@ietf.org> Mon, 29 June 2020 00:56 UTC
Return-Path: <jay@ietf.org>
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 95D3B3A089C for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 17:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 mlWX_Kk1RJRx; Sun, 28 Jun 2020 17:56:55 -0700 (PDT)
Received: from jays-mbp.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 73A5B3A0887; Sun, 28 Jun 2020 17:56:54 -0700 (PDT)
From: Jay Daley <jay@ietf.org>
Message-Id: <419D1FE3-9879-4553-90EF-914FC23B5A12@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FB4F1982-C090-4C8E-B959-8FAFDAF72CF1"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Mon, 29 Jun 2020 12:56:52 +1200
In-Reply-To: <CACOFP=iAzB+hrtZcu4yaDv9mpmxSybGTc-cugWC2Hv==-zTTdg@mail.gmail.com>
Cc: rfced-future@iab.org
To: Nevil Brownlee <nevil.brownlee@gmail.com>
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> <CACOFP=iAzB+hrtZcu4yaDv9mpmxSybGTc-cugWC2Hv==-zTTdg@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/BxbGWFYgXZ06O20nO2XZFh651TI>
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: Mon, 29 Jun 2020 00:56:58 -0000
> On 27/06/2020, at 3:01 PM, Nevil Brownlee <nevil.brownlee@gmail.com> wrote: > > 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 <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 :-) Some questions: Conceptually there are the following layers at which the RSE needs to operate: a. the long-term strategic level of where the series goes b. the medium-term managerial level of what tools are used, whether the SVG implementation is rethought, what performance is expected of the RPC, what the minimum standards are for a document to be accepted for processing, etc c. the short-term operational level of whether X change should be made the vocabulary, how Y should be rendered It is not clear to me what role you see for the RSE/RSEB at each of these levels, specifically: q1. Am I correct in assuming from section 2 "RSE Responsibilities" that you still see the role of the RSE as convening and managing the community process that agrees the long-term strategy? q2. If so then is the only role of the RSEB to assist in calling consensus or does the RSEB have a role in representing the community view? q3. How do you see the discussions/decisions for the managerial level working between the RSE/RSEB/Community? (i.e. it’s not clear to me from your document what role, if any, the community has in this) q4. Does the RSEB have any role at all in the operational level or is that left to the RSE, working with whatever team/process they determine is appropriate? It may be easier to answer those questions with your own definition of the levels. thanks Jay > > Cheers, Nevil > > On Thu, Jun 25, 2020 at 11:43 AM Martin Thomson <mt@lowentropy.net <mailto: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 <mailto:Rfced-future@iab.org> > https://www.iab.org/mailman/listinfo/rfced-future <https://www.iab.org/mailman/listinfo/rfced-future> > > > -- > ----------------------------------- > Nevil Brownlee, Taupo, NZ > -- > Rfced-future mailing list > Rfced-future@iab.org > https://www.iab.org/mailman/listinfo/rfced-future -- Jay Daley IETF Executive Director jay@ietf.org
- [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