Re: The IETF, Standards process, and the impact on the RFC series document production

Keith Moore <moore@network-heretics.com> Sat, 05 October 2019 03:10 UTC

Return-Path: <moore@network-heretics.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 5FEBD120047 for <ietf@ietfa.amsl.com>; Fri, 4 Oct 2019 20:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 rrJcOkr-UKvV for <ietf@ietfa.amsl.com>; Fri, 4 Oct 2019 20:10:22 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6CED120020 for <ietf@ietf.org>; Fri, 4 Oct 2019 20:10:22 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 1609921FFD; Fri, 4 Oct 2019 23:10:20 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 04 Oct 2019 23:10:20 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=sIdkZs GixF75JIwtvqnz79+qn9lpAnzvmuu45ObPZlk=; b=VHQcw/AzUHNHaQDn/BT4vp CgZ6gCx0eJlFimDVctndU/YPKfhOLVT/hT2WeCWjzlQJxYr+pRwBpizVlZvh5yWH 21rz54oUxUxqYO5ZqmkTVgmP1G83cmadEsqcY551DmL9OaKwA94DBN6mel7tjsQl PYqVJaVMr88Xc9/1FObY8svWQ3ZVb47cX7bTUwKTnAPV8Q7339hExJSpibvn/QK0 a3bcOg6DXJRA5mNWiUGPJJLtj9jivtzJjy4NQvd764QN6HEd97UPgZ9uIJbk7wEo oRJGTHuIcyghpFTiFoL3arYe7CsivDBushM8tDIsGgzRWOPni0ZlyqtXiy9ouK3A ==
X-ME-Sender: <xms:mwmYXZfKqtoiyw3qg6rAFLsDqD5NFoHi7XSlCLRtRdYhjXjtjaWL8g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrhedvgdeiiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtsegrtderre dtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthifohhr khdqhhgvrhgvthhitghsrdgtohhmqeenucfkphepuddtkedrvddvuddrudektddrudehne curfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvght ihgtshdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:mwmYXcf17lCfrT_-6FnlKuPRdDWnw5izv0tl03kQ8WN4e78Ahtw_ng> <xmx:mwmYXUMPlyRoW3WqWKRTPfHh7y5R_Deihq4Q6fC33tTj4oLZz-K0eA> <xmx:mwmYXbKnFKx6JSqUuo9B2OCR-oMpaaCK1Wluo6fBhRwCgRrK3oUXMA> <xmx:nAmYXf_C7W-BSOPffRNE5A6BDBWOdUWXElUhIvWk5VbIqxUnXXP2cQ>
Received: from [192.168.1.97] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 70F438005B; Fri, 4 Oct 2019 23:10:19 -0400 (EDT)
Subject: Re: The IETF, Standards process, and the impact on the RFC series document production
To: ietf@ietf.org
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> <3a67d528-ed48-8aa2-0514-67a8f09de76d@gmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <08b40e41-2f12-7a43-09b5-736294adc6e7@network-heretics.com>
Date: Fri, 04 Oct 2019 23:10:18 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <3a67d528-ed48-8aa2-0514-67a8f09de76d@gmail.com>
Content-Type: multipart/alternative; boundary="------------70FD0E5F3620846210961835"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2uj6a0GTD4EipNgQryGF-T9l-QQ>
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: Sat, 05 Oct 2019 03:10:24 -0000

On 10/4/19 10:40 PM, Brian E Carpenter wrote:

>>> Implementing our standards involves a treasure hunt
>>> to find how many RFC have to be read before understanding the whole
>>> picture.
>> This is problematic, but inherent, not so much in the RFC series, but in
>> the way we've chosen to do our standards process.
> Bingo! Changing the RFC series*will not*  fix this problem.

If I understand what problem is being described, I'm not sure changing 
the standards process would address it either.   (Though I do suspect 
that some changes are in order for other reasons.)

Most standards that are used on a large scale will need to be amended 
and/or extended over time.    Attempting to get everything right the 
first time can easily doom a standard to failure for any of multiple 
reasons (e.g. irrelevance, or too much complexity, or too little ability 
to adapt to changing conditions).

In a sense, the extensions and amendments are signs of success. If 
nobody used the standard, there would probably not be sufficient energy 
to make the changes.

Keith