Re: The IETF, Standards process, and the impact on the RFC series document production
Nico Williams <nico@cryptonector.com> Fri, 04 October 2019 19:32 UTC
Return-Path: <nico@cryptonector.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 04D3412003E for <ietf@ietfa.amsl.com>; Fri, 4 Oct 2019 12:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 ym_4_Ze2VkfL for <ietf@ietfa.amsl.com>; Fri, 4 Oct 2019 12:32:55 -0700 (PDT)
Received: from bonobo.elm.relay.mailchannels.net (bonobo.elm.relay.mailchannels.net [23.83.212.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55B59120025 for <ietf@ietf.org>; Fri, 4 Oct 2019 12:32:55 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 857F27404D4; Fri, 4 Oct 2019 19:32:54 +0000 (UTC)
Received: from pdx1-sub0-mail-a65.g.dreamhost.com (100-96-35-142.trex.outbound.svc.cluster.local [100.96.35.142]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 21097740660; Fri, 4 Oct 2019 19:32:54 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a65.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.17.5); Fri, 04 Oct 2019 19:32:54 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Name-Stupid: 56e0f28136953bc1_1570217574360_2212079153
X-MC-Loop-Signature: 1570217574360:3708115194
X-MC-Ingress-Time: 1570217574360
Received: from pdx1-sub0-mail-a65.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a65.g.dreamhost.com (Postfix) with ESMTP id 64D9C7FAD7; Fri, 4 Oct 2019 12:32:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=taclvJ5NN5vUiXIf46BDFFru6ck=; b=AwT8blldcQS x2NM935OHV7/Pktn/w5N5coJNU6jt/phR/EWhhEwN2YhjbldhwfLJb7Ku9ww9WTG d/0Q4WHye8YlXxJC1rtXVfXQgVpyx2wcAVoZ2pQnvqXvQ2lSb6URklSP4R0o9dd9 6B/324s5uKErw/gLwyuAPsUyoyMOgyQE=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a65.g.dreamhost.com (Postfix) with ESMTPSA id C1A267FADB; Fri, 4 Oct 2019 12:32:47 -0700 (PDT)
Date: Fri, 04 Oct 2019 14:32:45 -0500
X-DH-BACKEND: pdx1-sub0-mail-a65
From: Nico Williams <nico@cryptonector.com>
To: Michael StJohns <mstjohns@comcast.net>
Cc: ietf@ietf.org
Subject: Re: The IETF, Standards process, and the impact on the RFC series document production
Message-ID: <20191004193244.GI5002@localhost>
References: <394203C8F4EF044AA616736F@PSB> <4097464f-d038-2439-5ca5-70bac46b25ea@huitema.net> <69DAA6BBBE243BAD98926154@PSB> <371c3b14-8bfc-a476-3ff9-7268485bad12@huitema.net> <87a3e050-6e94-fcb0-70b8-cb907a029a0f@comcast.net> <20191004164815.GG5002@localhost> <a134ec7b-df81-435c-b9af-6ec43d5d5735@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
In-Reply-To: <a134ec7b-df81-435c-b9af-6ec43d5d5735@comcast.net>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrhedugddufedvucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtugfgjggfsehtkeertddtredunecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecukfhppedvgedrvdekrddutdekrddukeefnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopehlohgtrghlhhhoshhtpdhinhgvthepvdegrddvkedruddtkedrudekfedprhgvthhurhhnqdhprghthheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqedpmhgrihhlfhhrohhmpehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmpdhnrhgtphhtthhopehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bz_uFOWvuYN-2lDx4ntQ7beKuLU>
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: Fri, 04 Oct 2019 19:32:57 -0000
On Fri, Oct 04, 2019 at 01:55:15PM -0400, Michael StJohns wrote: > On 10/4/2019 12:48 PM, Nico Williams wrote: > > The ITU-T has a much better document naming scheme, and they too have an > > immutability property. Thus ASN.1 is the x.680 document series (x.680, > > x.681, x.682) and the encoding rules for ASN.1 are the x.690 series, > > and each document gets a "version number" in the form of publication > > year and month, and old versions remain accessible and unchanged. > > *laugh* But then you end up with weirdnesses like X.500 vs X.509. I *know* > why the certificate stuff started out in Directory oh so many years ago, but > in hindsight maybe not where it should be today? You could always assign a new series identifier when an old one stops bein relevant to a larger family. And, frankly, though I detest x.400 and x.500 as much as anyone, the series naming is just fine. I couldn't care less that ITU-T's PKI series is x.509 which means it's related to ITU-T's x.500 directory series. (x.509 and PKIX being related to x.500 is why we have the monstrosity of x.500 naming in PKIX, but we're moving past that, and we've done a lot of PKIX work here instead of there.) The point is that series naming is very helpful in reducing the number of things I have to recall in order to find a relevant specification. Organizing knowledge is, in fact, helpful. If I'm looking for some ASN.1 encoding rules spec, I just start by looking for x.690 and go from there. Try that with RFCs -- you'll need a search engine, and the RFC-Editor's search engine is damned near useless, while the I-D tracker is ever so slightly better, but still, nothing like free-text search. Now, maybe we just need to improve those search engines, or outsource the whole thing to general purpose search engines. But because these documents are the sort that can be organized with relatively little effort, doing so seems like no-brainer. An argument that organizing RFCs this way would be more expensive that one might think would be an interesting argument. An argument that it would be less useful than one might think would also be interesting. That related series might diverge in time is not really an interesting argument, IMO. > Or you end up with something like DNS running out of series numbers > and others requiring a series for a single document. ITU tends to be I wouldn't give lonely RFCs a series number, nor did it follow from what I wrote that I would. > MUCH more formal about which documents and standards they will even > start working on (e.g. a "work plan") before they ever start > allocating numbers. They also *require* a document to reviewed each > period of time and updated - that would be a substantial change to our Not relevant to the series concept. > model. Then you have things like TLS 1.0, 1.1, 1.2 and 1.3 that > share a negotiating strategy and have similar protocols, but might be > hard to characterize as the same protocol in the ISO model meaning. The point is to organize the specs in a meaningful way. For users and implementors, organizing TLS 1.0 through 1.3 as a single versioned series is perfectly reasonable. If at some point we end up wanting a new series for just TLS 1.53, then we could do that too. > If you go into the other direction, you get things like IEEE 802.11 which > depends on 802.1 and has a bunch of sub standards ( *pun intended*) such as > 802.11ac and that collection seems to change each time I go looking. Thus versioning. There has to be some degree of immutability. But also some degree of familiarity where it's useful. > In any event I think it's TANSTAAFL - you pick one approach, you close off > others and each has its own flaws. Not so. You could have a document appear in any of zero, one, or N > 1 series -- whatever's appropriate. > I'm not opposed to having the conversation, but we need to pick something > that works for how we do things, or we need to change how we do standards. > And that's a conversation I'm not sure we're quite yet ready to have. If you laugh at, and discount an idea without considering it in any seriousness, then you're right: you're not ready to have that discussion. Nico --
- 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