Re: [Rfced-future] Scope and IETF 108 proposals
Eric Rescorla <ekr@rtfm.com> Mon, 29 June 2020 01:05 UTC
Return-Path: <ekr@rtfm.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 2F2963A1008 for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 18:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=rtfm-com.20150623.gappssmtp.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 BKV1CAGmkMGd for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 18:05:56 -0700 (PDT)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) (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 B1CFD3A0882 for <rfced-future@iab.org>; Sun, 28 Jun 2020 18:05:55 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id h22so9003681lji.9 for <rfced-future@iab.org>; Sun, 28 Jun 2020 18:05:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7AWJKrVzQ4sGI+HXJVUin0W6wnlglnZGZtQrSbT+3nA=; b=P+k5r0lPWd7kFfez+sJN4E2sbdC9QTZHsJnMJGLcWUEu/wJUWDaBrzYXBavJsNmGor TLLhfQUwF9o5RNw3S84xtegoZT1BklM8gdxnXjp9PaNWm8eWkh6KWSv+hxuXkURMYnor EpW49Liz8yWAx+P+KXdpNIFeNy7HnFT49JjVysye5ZOiw8CM4tetunTKfFVLH8k9X/5Y 53Nf7HKMapnOS/kEwjk+2YEKLvJw8yeN6zRWWxrE4/fqz1rc4D3gS8XZyEA9W1xQywpp /YgUnclYymLdjt0yK+pYPhZn+WXCTGIlqSNWbf19LasBDjy2rnWNFsygTc/L8vIcMz1u ItVA==
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=7AWJKrVzQ4sGI+HXJVUin0W6wnlglnZGZtQrSbT+3nA=; b=dK5Hu8ldPqtyUZd8RonsgY6vzH006wBXtGeZ72eoE8guWlhkOtgn3391pAt9ZTf9bj vdjzV80sytc/Cd4CQl03EhPhlPXKVvk+VmqNTftSf0oRcVcZNvDSWrBeJg8Z2MKYuqJM hqdywovc4bmqgAyIVe/lkcarCPRh5Abn0KTB3wLnOyXfOaR/0+ujVOWQxQQTK3AgdhtA cmdNF0y6g5ZIKm4pFHCXq06IKXF1rV/+pGAf6pymcDK6/hBEfrPW5F8ycdy45p8ZkPRf EQPeOG6qT51dcLo0IyxGOb/oEf2CTmwWbhNAJVDH41/Oju7EpKqYJYxkxdcK8XXX+pQX YntQ==
X-Gm-Message-State: AOAM530Qo6tneAmrPlzbdHcV3hfUAtNE2TK6rX6zM8fymVlyX5mx0yuf sRO84dTxIO3VYHaXSjzyYI9B5OKkb4SHx3OSSAkDN21dHLw=
X-Google-Smtp-Source: ABdhPJxK7WMhnPxFUej61s6KxXIeT1hEoAmztqZWoaWSW/8/mpj9lnHtbd7xfJV/y7Uco1kOl+Wl1jooEz3+zmlf1NY=
X-Received: by 2002:a2e:2a42:: with SMTP id q63mr7208593ljq.265.1593392753742; Sun, 28 Jun 2020 18:05:53 -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> <CACOFP=iAzB+hrtZcu4yaDv9mpmxSybGTc-cugWC2Hv==-zTTdg@mail.gmail.com> <cfd9512d-b61e-4438-9ce3-102f6ddaebe7@www.fastmail.com> <befe8914-996a-d4f0-f9ef-cc49d882839c@joelhalpern.com> <dc41e1eb-35c6-b678-65e2-db638f330018@nthpermutation.com> <3EDDC9C7-BA91-4E18-AB1C-8E77E95627B2@mnot.net>
In-Reply-To: <3EDDC9C7-BA91-4E18-AB1C-8E77E95627B2@mnot.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 28 Jun 2020 18:05:17 -0700
Message-ID: <CABcZeBN57B409GY0uNOOSpn6v=OW-6m87067JCSSfnDPOP-uiA@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Michael StJohns <msj@nthpermutation.com>, rfced-future@iab.org
Content-Type: multipart/alternative; boundary="000000000000133d3605a92ea918"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/re3-6PdkBTWnlfwVgNSH_AZLlV0>
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 01:05:58 -0000
On Sun, Jun 28, 2020 at 5:23 PM Mark Nottingham <mnot@mnot.net> wrote: > The suggestion was to have more than one more specialised role, not to > promote 'leadership by committee.' This has been discussed a number of > times previously, due to the very high bar created by the combination of > requirements we current place on the position (as Martin mentioned). > This aside, I don't really understand the "leadership by committee" argument here. Here at the IETF we design protocols which will run on billions of nodes using a collaborative consensus-based process. I find it surprising that people think we can't use this process for the much lower stakes question of how our documents ought to be shaped. -Ekr > > On 29 Jun 2020, at 10:14 am, Michael StJohns <msj@nthpermutation.com> > wrote: > > > > On 6/28/2020 7:50 PM, Joel M. Halpern wrote: > >> In my view, the reason we need a person to do this is that leadership > by committee is essential equivalent to a recipe for disaster. And I do > think we want leadership. > >> > >> Yours, > >> joel > > Strong +1 here. One of the reasons for having a senior person in this > role is so that the attention paid to the strategic evolution of the series > does not wax and wane based on the current hobbyhorses of the leadership or > their companies, or upon other loud voices. I have no problems with > those voices influencing strategy, but I have strong problems with those > voices directing strategy - especially if they change directions every 6 > months or a year. > > > > We've had at least 4 people with the "rare and difficult" [Aside: > difficult?] combination of attributes so I'm not sure where Martin is > coming from here. It may be that he doesn't agree that those are the > right attributes for the role, but that's a whole other discussion. I > would expect with some luck, and with an IETF that respects what an expert > can bring to the role, we will be able to find someone who won't run > screaming into the night after they meet us. > > > > Mike > > > > > > > >> On 6/28/2020 7:47 PM, Martin Thomson wrote: > >>> On Sat, Jun 27, 2020, at 13:01, Nevil Brownlee wrote: > >>>> 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 > >>> > >>> This is very much not what I had in mind. We should not insist on > having a role that depends on finding an individual with a rare and > difficult combination of attributes. And I don't think that you can > support that function by taking a program with open participation and > consensus processes and reduce that to 5 people (+stream manager ex > officio) who are responsible for approving strategy. > >>> > >>> Perhaps you can start by explaining why you think we need to have an > individual perform these functions. > >>> > >> > > > > > > -- > > Rfced-future mailing list > > Rfced-future@iab.org > > https://www.iab.org/mailman/listinfo/rfced-future > > -- > Mark Nottingham https://www.mnot.net/ > > -- > Rfced-future mailing list > Rfced-future@iab.org > https://www.iab.org/mailman/listinfo/rfced-future >
- [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