Re: [Rfced-future] Scope and IETF 108 proposals
Michael StJohns <msj@nthpermutation.com> Mon, 29 June 2020 00:14 UTC
Return-Path: <msj@nthpermutation.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 67DF83A0FD6 for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 17:14:42 -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=nthpermutation-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 h2sN4uUARm-x for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 17:14:40 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 902003A0842 for <rfced-future@iab.org>; Sun, 28 Jun 2020 17:14:40 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id x62so11654129qtd.3 for <rfced-future@iab.org>; Sun, 28 Jun 2020 17:14:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=xUVbdheLe04IgAf4X1BFk6l3HbYrkn5UXi48UOPp2Ao=; b=WDtEPXgmYR+ElvjUvnCj9wyV+jAkoDGbkUzHaarmXPhDbvNmTN4z4Bl7iyfUTy1nkA 00mpCHamn027nxBf5IEFoVoGbtW83gUYBNJslha5iqLyVV3fkxgdd3v++7wqhDMU9TfN MXo+/a7L5/b0b+I2pnghMONJv5Z2KA8wJNzNUu5R4pL2dESBnKCLlAlkF0FC+E7igOQ2 PIQ70W/dWur8/iAnaonnPiwQ3RhOF8ShAqWW8N+96NTbUAq5QoUbp75PvF2MKimfmJ6P StfNVHLmlNSL84lZUXkEaQMeKwfQJHuR4s3cx7JTFiDDAkZhXd6+uwWo5eAyovYSCjQa fQ2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=xUVbdheLe04IgAf4X1BFk6l3HbYrkn5UXi48UOPp2Ao=; b=h0iJuwG4YQvFbkLG+Gwc4hTocN7bGYqC77fL/SGGD1ygxBR7qcj9/VydG4YLQqhKW3 6O6z9ARvGMlWUA1BW4855CZxywPt51rPxbLiZBl3HyG0OaWXpL1SIEczQWvB7PeI83fl YKEJgGX4+Vqvq2Xu7Hilv2Bn6huEadnPtcsXwrz9w3+lmLzMdVbcmOJxOoOAFCg7/tJl gfuOdWH69IwYnwDzql50dXh/49gNcuVD/afLuIYjkiSKNj8LxImn+bomq64UwzXxkXiq WyiQFpri2SNM/4syDj1aFhln/vJeBkV8AEbrV92Z8nbntjRLLsJW7xBJj8SnhmZx62CI yJNg==
X-Gm-Message-State: AOAM533ZZE+cIMX8fs9VV7YV0Uj4zMfrv2o3KFxzGXQG9a995015W/GF uWHrHXw1PNhx66AeyvgBGY8pE9jqqBoBVA==
X-Google-Smtp-Source: ABdhPJzVlM4McHUrjc1A3jSUVNuY9U2VBdPVQFnE3neo67kVhMcIYiyBqVBBJsOGikhdGjRE47DKoQ==
X-Received: by 2002:ac8:134a:: with SMTP id f10mr13678917qtj.131.1593389679040; Sun, 28 Jun 2020 17:14:39 -0700 (PDT)
Received: from [192.168.1.115] (pool-71-163-188-115.washdc.fios.verizon.net. [71.163.188.115]) by smtp.gmail.com with ESMTPSA id r49sm17642985qtr.11.2020.06.28.17.14.38 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 28 Jun 2020 17:14:38 -0700 (PDT)
To: rfced-future@iab.org
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>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <dc41e1eb-35c6-b678-65e2-db638f330018@nthpermutation.com>
Date: Sun, 28 Jun 2020 20:14:37 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <befe8914-996a-d4f0-f9ef-cc49d882839c@joelhalpern.com>
Content-Type: multipart/alternative; boundary="------------48CEC9F068CC9443CC25CD3E"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/nHJC9cjXhlydaOaTApTU50J_I18>
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:14:42 -0000
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] 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