Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.

Keith Moore <moore@network-heretics.com> Wed, 03 July 2019 20:45 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 8A1E81200DB for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 13:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 SJXe4OZgW5iT for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 13:45:15 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 214D41200C7 for <ietf@ietf.org>; Wed, 3 Jul 2019 13:45:15 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0344722196; Wed, 3 Jul 2019 16:45:14 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 03 Jul 2019 16:45:14 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding: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=YH2pW2w5WapXOjJajvJgB/R9DVkUufMjITnenBYmc I8=; b=KJuPwNbKJMl3NxzdqBb5bI5CBtUJ87vUPhltu9D8PvN5h3t72bru62I8p 2VXu0kJUVk4zfPKleIKF+HDYOYmllZuZrjlj3jdiFaAsJCAqh9mHw/YB4D5IO4qS pICovr+rDdUMMNbk5uHmo/zc3oUol5ebo2rpRJ+COiMvqv1Qu7fKgFojnEZQoRCf D8ht17iMvrAWFpHqmYmRfLFm4/eyf2QvjBRyiG2EjmWG++mP9iSY9NMtZ8Nk4ReZ gd/O/jmpQsUthP6Qt7N4rCh1TvJBQRzhu3OL1NqUVeh0DZSITOruQOeaHgY6KmHy S+1ROMHJoRxwujXK5YaLq/pY6Y3mA==
X-ME-Sender: <xms:2BMdXcSW4VftGmAl-W0-NsycAy0c_GpOolnMBf8qlLR-gBnp1xXYiA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrfedtgdduheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucfkphepuddtkedrvddvuddrudektddrud ehnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghr vghtihgtshdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:2RMdXeA-Vq5Y-ZQfw3w4ysvLoNhAiQCXocQuUDi_eIXVKYPkMowpPA> <xmx:2RMdXU3yYK9M_hhl_-gpae1JkA22Vi-5vl6i93J7M_J8yGFMJV1fFw> <xmx:2RMdXUVi8_nlLX1_jwl5Gh2SdiPr6B2sy6QLp4ngoT5iB7sMJ1gsuA> <xmx:2RMdXRKSw-bzQ2ElWNw0oozAG7behgHVgfq8YPqPRTlo-fAcOitlzQ>
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 638C78005A; Wed, 3 Jul 2019 16:45:12 -0400 (EDT)
Subject: Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.
To: ietf@ietf.org
References: <CAHw9_iKv7xDY-rT98F_BAEvGOGbWGL7UpXS42rSVLsHB+=SOZg@mail.gmail.com> <4567879e-aa29-aeae-72e9-33d148d30eed@network-heretics.com> <20190703203949.GC3508@localhost>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <f3fd95d5-48ab-85ac-f36c-64dd887e4cc3@network-heretics.com>
Date: Wed, 03 Jul 2019 16:45:11 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1
MIME-Version: 1.0
In-Reply-To: <20190703203949.GC3508@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4SOzCZ6_cznV5cDFl06EEct9PHk>
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: Wed, 03 Jul 2019 20:45:18 -0000

On 7/3/19 4:39 PM, Nico Williams wrote:
> On Wed, Jul 03, 2019 at 04:10:13PM -0400, Keith Moore wrote:
>> On 7/3/19 4:04 PM, Warren Kumari wrote:
>>> TL;DR: Being able to mark a specific version of an *Internet Draft* as
>>> “stable” would often be useful. By encoding information in the name
>>> (stable-foo-bar-00) we can do this.
>>>
>>> Heather and I will be holding a side meeting at IETF 105 to discuss
>>> the idea and get feedback.
>>> When: Tue, July 23, 3:00pm – 4:30pm
>>> Where: C2 (21st Floor)
>> It seems to me that this would defeat the entire purpose of Internet-Drafts
>> and serve to circumvent the IETF process.    There should be no expectation
>> of stability until a document has reached IETF-wide consensus.
> Implementors regularly ship pre-RFC code...

Yes, and it's quite often inappropriate for them to do so, a disservice 
to their customers and sometimes to the whole Internet.

(there are specific cases when doing so is mostly harmless, especially 
if there's a seamless way to upgrade without disruption.... but there 
are many cases for which this is not possible.)

> But this doesn't have to be about shipping prior to RFC publication.  It
> can be just about limiting the impact of future edits on existing code
> that hopefully has not yet shipped anyways.
>
> Now, this can be done _today_ by convention -- you just write in the I-D
> that version starting at version -XX only backwards-compatible changes
> will be entertained.

And in general, it's inappropriate for a WG (or author of a 
standards-track document) to do that before IETF consensus has been reached.

Keith