Re: "community" for the RFC series (was: Re: [rfc-i] [IAB] New proposal/New SOW comment period)
John C Klensin <john-ietf@jck.com> Thu, 03 October 2019 23:22 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41AC2120112; Thu, 3 Oct 2019 16:22:50 -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, SPF_HELO_NONE=0.001, SPF_NONE=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 QdRRyIub-tIV; Thu, 3 Oct 2019 16:22:48 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FF5712010D; Thu, 3 Oct 2019 16:22:48 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1iGAQk-000GdK-Jw; Thu, 03 Oct 2019 19:22:42 -0400
Date: Thu, 03 Oct 2019 19:22:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: rfc-interest@rfc-editor.org, iab@iab.org, IETF <ietf@ietf.org>
Subject: Re: "community" for the RFC series (was: Re: [rfc-i] [IAB] New proposal/New SOW comment period)
Message-ID: <0317B8D6A3D37783A98C524A@PSB>
In-Reply-To: <120cf3cb-31a6-7cc9-d6e3-7daee0f9d11d@cs.tcd.ie>
References: <394203C8F4EF044AA616736F@PSB> <4097464f-d038-2439-5ca5-70bac46b25ea@huitema.net> <69DAA6BBBE243BAD98926154@PSB> <750a842a-b527-82b9-e8b8-1d23fdc5cc72@cs.tcd.ie> <31b3720b-c8f1-3964-ae30-ce391007b3aa@gmail.com> <120cf3cb-31a6-7cc9-d6e3-7daee0f9d11d@cs.tcd.ie>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3uiu1lhWz7kmW7nDHVbBdsPwbxQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Oct 2019 23:22:50 -0000
Stephen, --On Thursday, October 3, 2019 21:40 +0100 Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > (Changing the subject, hope that's ok) Probably overdue although I wanted my note to reflect the subject line Christian used. So thanks. General comment: I think Brian's I-D is a very important contribution to what I increasingly see as the key discussion. I think (at least) the three of us agree that discussion is due or overdue (except insofar as we see the core issues as having been settled in July 2018). From my personal standpoint, whatever the IAB or RSOC decide to do to be sure there isn't a break in the RFC Editor Function on Heather's departure is very nearly irrelevant except insofar as those decisions foreclose or preempt options for the future of the RFC Series. Unfortunately, I see a very real risk of such foreclosure or preemption occurring, whether by accident or intentionally. >... >> Not in a few words, but may I point to >> https://tools.ietf.org/html/draft-carpenter-request-for-comme >> nts ? > > Sure. I recall reading that before. > >> The most relevant text is: >> >> The reasonable conclusion from the above is that none of >> the I* organisations (IETF Trust, IETF LLC, IETF, IESG, >> IAB or ISOC) can claim exclusivity of ownership or control >> over the RFC series. It is community property and must >> operate on behalf of the community as a whole. > > I'm not sure that considering this in terms of who owns or > controls what is our best bet TBH, even though that is partly > in contention I guess. It may be easier to first roughly > define what is meant by a "larger community" (though I may > be wrong about that as I often am;-). I would suggest that it implies not only "readers of RFCs" (your categorization later in your note) but everyone who is dependent on them. To the extent to which we want to be even partially as an engineering body rather than a recorder of common industry practices (a long note I wrote about that some time ago, but was assured that no one had read, might be relevant here) that means publication, not only of documents that describe the IETF's conclusions but documents that explain why the IETF might be wrong under some circumstances and what should be done instead. It includes procurement people who want to be sure that whatever they buy conforms to some standard. That implies that the standard has to be clear and stable but not that they will ever read it (if things don't work and they call in the lawyers, it may imply that the latter, and experts they hire, would need to read it carefully). That, in turn, raises some issues about what "the standard" for a particular topic or protocol really is, which segues into the Newtrk work that the IESG at the time blew off but the underlying issues are as significant now as ever. >From my point of view, very few of those issues are actually separable from each other and, as Brian points out, it "would be a serious mistake to try to fix the IETF's process only by fiddling with the RFC series". I'd actually go a bit further and suggest that it is hard to think clearly about the RFC Editor Function without understanding what the IETF --and those who are, or should be, dependent on its work-- actually need and want. If, for example, the IETF were to go significantly in the direction of turning technical specifications into living documents, then a different publication model might be needed (it may be helpful to remember that Newtrk never anticipated ISDs or other summary documents being part if the RFC Series and subject to its constraints. On the other hand, if the IETF were to move in the direction of 5 year review cycles and completely replacing earlier documents, that would also force large changes in the relationship between IETF technical specs and the RFC Series. > I guess one could extend it to people affected by the RFC > series, but then you're up to 7.7 billion and counting > which doesn't seem right really. See above. I think that, wrt the RFC Series and the RFC Editor function, it would help a lot if the IETF and IAB assumed the role of trustees for that broader community, thought carefully about what that would mean, shared those thoughts as widely as possible, and opened them for discussion. >... best, john
- New proposal/New SOW comment period Sarah Banks
- Re: New proposal/New SOW comment period Michael StJohns
- Re: New proposal/New SOW comment period Stephen Farrell
- Re: New proposal/New SOW comment period Sarah Banks
- Re: New proposal/New SOW comment period Matthew A. Miller
- Re: New proposal/New SOW comment period Eliot Lear
- RE: [rfc-i] New proposal/New SOW comment period Adrian Farrel
- Re: New proposal/New SOW comment period S Moonesamy
- Sergeant-at-Armss and New proposal/New SOW commen… John C Klensin
- Re: Sergeant-at-Armss and New proposal/New SOW co… Bob Hinden
- Re: Sergeant-at-Armss and New proposal/New SOW co… Keith Moore
- Re: Sergeant-at-Armss and New proposal/New SOW co… Adam Roach
- Re: Sergeant-at-Armss and New proposal/New SOW co… Keith Moore
- Re: Sergeant-at-Armss and New proposal/New SOW co… Adam Roach
- Re: Sergeant-at-Armss and New proposal/New SOW co… Bob Hinden
- Re: Sergeant-at-Armss and New proposal/New SOW co… Adam Roach
- Re: Sergeant-at-Armss and New proposal/New SOW co… Michael StJohns
- Re: Sergeant-at-Armss and New proposal/New SOW co… Keith Moore
- Re: Sergeant-at-Armss and New proposal/New SOW co… Michael
- Re: Sergeant-at-Armss and New proposal/New SOW co… Adam Roach
- Re: Sergeant-at-Armss and New proposal/New SOW co… Michael
- Re: Sergeant-at-Armss and New proposal/New SOW co… Masataka Ohta
- Re: Sergeant-at-Armss and New proposal/New SOW co… Keith Moore
- Re: Sergeant-at-Armss and New proposal/New SOW co… Benjamin Kaduk
- Re: Sergeant-at-Armss and New proposal/New SOW co… Eric Rescorla
- Re: Sergeant-at-Armss and New proposal/New SOW co… Randy Bush
- Re: Sergeant-at-Armss and New proposal/New SOW co… Benjamin Kaduk
- Re: Sergeant-at-Armss and New proposal/New SOW co… John C Klensin
- Re: Sergeant-at-Armss and New proposal/New SOW co… Keith Moore
- Re: Sergeant-at-Armss and New proposal/New SOW co… Eric Rescorla
- Re: Sergeant-at-Armss and New proposal/New SOW co… Randy Bush
- Re: Sergeant-at-Armss and New proposal/New SOW co… Eric Rescorla
- Re: Sergeant-at-Armss and New proposal/New SOW co… Randy Bush
- Re: Sergeant-at-Armss and New proposal/New SOW co… Keith Moore
- Re: Sergeant-at-Armss and New proposal/New SOW co… Eric Rescorla
- Re: Sergeant-at-Armss and New proposal/New SOW co… Melinda Shore
- Re: [rfc-i] New proposal/New SOW comment period Eliot Lear
- Re: Sergeant-at-Armss and New proposal/New SOW co… Masataka Ohta
- Re: Sergeant-at-Armss and New proposal/New SOW co… Masataka Ohta
- Re: Sergeant-at-Armss and New proposal/New SOW co… Leif Johansson
- Re: Sergeant-at-Armss and New proposal/New SOW co… Masataka Ohta
- Re: [rfc-i] New proposal/New SOW comment period S Moonesamy
- Re: Sergeant-at-Armss and New proposal/New SOW co… Bob Hinden
- Re: New proposal/New SOW comment period Michael StJohns
- Re: [rfc-i] New proposal/New SOW comment period Michael StJohns
- SAA Do's and Don'ts Michael StJohns
- Re: SAA Do's and Don'ts Keith Moore
- Re: SAA Do's and Don'ts Melinda Shore
- tone policing (was: SAA Do's and Don'ts) Keith Moore
- Re: Sergeant-at-Armss and New proposal/New SOW co… Theodore Y. Ts'o
- Re: [rfc-i] New proposal/New SOW comment period Adam Roach
- Re: SAA Do's and Don'ts John C Klensin
- Re: SAA Do's and Don'ts Masataka Ohta
- Re: tone policing (was: SAA Do's and Don'ts) Mark Nottingham
- Re: tone policing Keith Moore
- Re: tone policing Mark Nottingham
- Re: SAA Do's and Don'ts Keith Moore
- Re: tone policing Keith Moore
- Re: tone policing Masataka Ohta
- Re: tone policing Mark Nottingham
- Re: tone policing Keith Moore
- Re: tone policing Mark Nottingham
- Re: tone policing Rob Sayre
- Re: tone policing Stephen Farrell
- Re: tone policing Keith Moore
- Re: tone policing Melinda Shore
- Re: tone policing Masataka Ohta
- Re: tone policing Masataka Ohta
- Re: tone policing Keith Moore
- Re: tone policing Adam Roach
- Re: tone policing Keith Moore
- Re: tone policing Ted Lemon
- Re: tone policing Keith Moore
- Re: [rfc-i] New proposal/New SOW comment period Michael StJohns
- Re: tone policing lloyd.wood@yahoo.co.uk
- Re: tone policing Rob Sayre
- Re: [rfc-i] New proposal/New SOW comment period Adam Roach
- Re: tone policing Adam Roach
- Re: tone policing Masataka Ohta
- Re: tone policing Dan Harkins
- Re: tone policing Rob Sayre
- Re: tone policing Ted Lemon
- Re: tone policing Keith Moore
- Re: tone policing Ted Lemon
- Re: tone policing Keith Moore
- Re: tone policing Christer Holmberg
- Re: tone policing Ted Lemon
- Re: tone policing Paul Wouters
- Re: tone policing Keith Moore
- Re: tone policing Nick Hilliard
- Re: tone policing Keith Moore
- Re: tone policing Nick Hilliard
- Re: tone policing Ted Lemon
- Re: tone policing Dirk-Willem van Gulik
- Re: tone policing Ted Lemon
- Re: tone policing Dan Harkins
- Re: tone policing Adam Roach
- Re: tone policing Keith Moore
- Re: tone policing ned+ietf
- Re: tone policing Dan Harkins
- Re: tone policing Randy Bush
- Re: tone policing Theodore Y. Ts'o
- Re: Sergeant-at-Armss and New proposal/New SOW co… Spencer Dawkins at IETF
- Re: tone policing Masataka Ohta
- Re: tone policing Patrik Fältström
- Re: [rfc-i] New proposal/New SOW comment period Sarah Banks
- Re: [rfc-i] New proposal/New SOW comment period Sarah Banks
- Re: [rfc-i] New proposal/New SOW comment period Sarah Banks
- RE: [rfc-i] New proposal/New SOW comment period Adrian Farrel
- Re: tone policing lloyd.wood
- Re: [rfc-i] New proposal/New SOW comment period Michael StJohns
- Re: [rfc-i] New proposal/New SOW comment period Michael StJohns
- Re: [rfc-i] New proposal/New SOW comment period Sarah Banks
- Re: [rfc-i] New proposal/New SOW comment period Spencer Dawkins at IETF
- Re: tone policing Salz, Rich
- Re: tone policing Keith Moore
- Re: tone policing Ted Lemon
- Re: tone policing Keith Moore
- Re: tone policing Ted Lemon
- Re: tone policing Viktor Dukhovni
- Re: tone policing Keith Moore
- Re: tone policing Ted Lemon
- Re: tone policing Keith Moore
- Re: tone policing Paul Wouters
- Re: tone policing Salz, Rich
- Re: tone policing Doug Royer
- Re: tone policing Keith Moore
- Re: tone policing Dan Harkins
- Re: tone policing Joel M. Halpern
- Re: tone policing Salz, Rich
- Re: tone policing Salz, Rich
- Re: tone policing Bron Gondwana
- Re: tone policing Dan Harkins
- Re: tone policing Stephen Farrell
- Re: tone policing Brian E Carpenter
- Re: tone policing Dan Harkins
- Re: tone policing Bron Gondwana
- Re: tone policing Masataka Ohta
- Re: tone policing Dan Harkins
- Re: tone policing Ted Lemon
- Re: tone policing Randy Bush
- Re: tone policing Leif Johansson
- Agenda Denial Was: tone policing Phillip Hallam-Baker
- Re: Agenda Denial Was: tone policing Ted Lemon
- Re: Agenda Denial Was: tone policing Paul Wouters
- BIMI: Re: tone policing Phillip Hallam-Baker
- Re: Agenda Denial Was: tone policing Keith Moore
- Re: Agenda Denial Was: tone policing Keith Moore
- Re: Agenda Denial Was: tone policing Ted Lemon
- Re: tone policing Keith Moore
- Re: Agenda Denial Was: tone policing Keith Moore
- Re: Agenda Denial Was: tone policing Stan Kalisch
- Re: Agenda Denial Was: tone policing Dan Harkins
- Re: Agenda Denial Was: tone policing Nico Williams
- Re: Agenda Denial Was: tone policing Phillip Hallam-Baker
- Re: Agenda Denial Was: tone policing Phillip Hallam-Baker
- Re: Agenda Denial Was: tone policing Keith Moore
- Re: tone policing Bron Gondwana
- Re: New proposal/New SOW comment period John C Klensin
- Re: New proposal/New SOW comment period Michael Richardson
- Re: New proposal/New SOW comment period John C Klensin
- Re: New proposal/New SOW comment period Sarah Banks
- Re: New proposal/New SOW comment period Sarah Banks
- Re: [rfc-i] New proposal/New SOW comment period Ted Lemon
- Re: [IAB] New proposal/New SOW comment period Christian Huitema
- Re: [rfc-i] New proposal/New SOW comment period Sarah Banks
- Re: [rfc-i] New proposal/New SOW comment period Ted Lemon
- Re: [rfc-i] New proposal/New SOW comment period Brian E Carpenter
- Re: [rfc-i] New proposal/New SOW comment period Henrik Levkowetz
- Re: [rfc-i] New proposal/New SOW comment period Leif Johansson
- Re: New proposal/New SOW comment period John C Klensin
- Re: New proposal/New SOW comment period (off-topi… S Moonesamy
- Re: New proposal/New SOW comment period Sarah Banks
- Re: [IAB] New proposal/New SOW comment period John C Klensin
- Re: [IAB] New proposal/New SOW comment period Stephen Farrell
- Re: [rfc-i] [IAB] New proposal/New SOW comment pe… Brian E Carpenter
- "community" for the RFC series (was: Re: [rfc-i] … Stephen Farrell
- Re: "community" for the RFC series Brian E Carpenter
- Re: "community" for the RFC series (was: Re: [rfc… John C Klensin
- Re: [IAB] New proposal/New SOW comment period Christian Huitema
- Re: "community" for the RFC series Stephen Farrell
- The IETF, Standards process, and the impact on th… Michael StJohns
- Re: The IETF, Standards process, and the impact o… Nico Williams
- Re: The IETF, Standards process, and the impact o… John C Klensin
- Re: The IETF, Standards process, and the impact o… John C Klensin
- Re: The IETF, Standards process, and the impact o… John C Klensin
- Re: The IETF, Standards process, and the impact o… Nico Williams
- Re: The IETF, Standards process, and the impact o… Michael StJohns
- Re: "community" for the RFC series Christian Huitema
- Re: The IETF, Standards process, and the impact o… Nico Williams
- Re: The IETF, Standards process, and the impact o… Keith Moore
- Re: The IETF, Standards process, and the impact o… John C Klensin
- Re: The IETF, Standards process, and the impact o… Nico Williams
- Re: "community" for the RFC series Leif Johansson
- Re: "community" for the RFC series Stephen Farrell
- Re: "community" for the RFC series Randy Bush
- Re: "community" for the RFC series Brian E Carpenter
- Re: The IETF, Standards process, and the impact o… Brian E Carpenter
- Re: The IETF, Standards process, and the impact o… Keith Moore
- Re: [rfc-i] "community" for the RFC series Henrik Levkowetz
- Re: "community" for the RFC series John C Klensin
- Re: "community" for the RFC series Stephen Farrell
- Re: The IETF, Standards process, and the impact o… Randy Presuhn
- Re: The IETF, Standards process, and the impact o… Christian Huitema
- Re: "community" for the RFC series S Moonesamy
- Re: "community" for the RFC series Brian E Carpenter
- Re: "community" for the RFC series Michael StJohns
- Re: "community" for the RFC series Stephen Farrell
- Re: "community" for the RFC series Stephen Farrell
- Re: "community" for the RFC series Brian E Carpenter
- Re: The IETF, Standards process, and the impact o… Michael Richardson
- Re: "community" for the RFC series Christian Huitema
- Re: "community" for the RFC series Christian Huitema
- Re: "community" for the RFC series Brian E Carpenter
- Re: "community" for the RFC series Stephen Farrell
- Re: "community" for the RFC series Keith Moore
- Re: "community" for the RFC series Christian Huitema
- Re: "community" for the RFC series Stephen Farrell
- Re: [IAB] "community" for the RFC series Colin Perkins
- Re: "community" for the RFC series Brian E Carpenter
- Re: "community" for the RFC series Keith Moore
- Re: "community" for the RFC series Brian E Carpenter