Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 04 July 2019 01:30 UTC

Return-Path: <ajs@anvilwalrusden.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 0A0B01200E7 for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 18:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=fIWDyoNL; dkim=pass (1024-bit key) header.d=yitter.info header.b=i3GmRKB0
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 d3t6EzuHKJnX for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 18:30:13 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DB841200D7 for <ietf@ietf.org>; Wed, 3 Jul 2019 18:30:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id D4036BCCE5 for <ietf@ietf.org>; Thu, 4 Jul 2019 01:30:11 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1562203811; bh=xZhyEZ0WAfzz+/AdPYWsc8HlDnPZhOFfbaUsL6+wKt4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=fIWDyoNLJLouHU0zYEEEaRzONuTKhPbuMcD7pUpXc89/exUej3pJ+xOiepFHfmnQG GOFAr2yQqfBS/CpO1WclG2KauYrmrzL9WietDe5HdaIwROi8hPdnFofLPIbojl/RG3 5Z1oj5ATBjvKbbNY4+yHYZ69BdCaVB6lqaKYHPhc=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ckU7y3JhBuYv for <ietf@ietf.org>; Thu, 4 Jul 2019 01:30:10 +0000 (UTC)
Date: Wed, 03 Jul 2019 21:30:09 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1562203810; bh=xZhyEZ0WAfzz+/AdPYWsc8HlDnPZhOFfbaUsL6+wKt4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=i3GmRKB0DKllMYQbuOby5zHZmxHmuP2wRsME/CF+TB4+u2skQlnPH23GwmGIvzxAF Q7v/LqBniShfzgFuI+YzPyKaEWWpHa+hMbiB/Hry2FLNX0X8Pt8SL626wak8ZWa7jG Fehc1759BvZXBt7Blh29kbkfvp1gDW6lIPtpOAUc=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Things that used to be clear (was Re: Evolving Documents (nee "Living Documents") side meeting at IETF105.)
Message-ID: <20190704013009.dlifopcbm2umnqo7@mx4.yitter.info>
References: <CAHw9_iKv7xDY-rT98F_BAEvGOGbWGL7UpXS42rSVLsHB+=SOZg@mail.gmail.com> <4567879e-aa29-aeae-72e9-33d148d30eed@network-heretics.com> <CAL02cgToQWmOrfOxS_dc4KRtT9e0PXNzmhWZHkRUyV_3V=E-mQ@mail.gmail.com> <0856af71-4d84-09d1-834d-12ac7252420c@network-heretics.com> <CAL02cgQ9qWVUTPW=Cpx=r32k3i1PLgfp5ax0pKMdH0nKObcKTg@mail.gmail.com> <e8d28a7f-128d-e8d0-17d3-146c6ff5b546@joelhalpern.com> <CAHw9_i+UBs85P+gjcF6BJd1_WD2qFrrYCnXb4rtcG9Hepqm37w@mail.gmail.com> <796c1f6c-cd67-2cd5-9a98-9059a0e516f8@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <796c1f6c-cd67-2cd5-9a98-9059a0e516f8@network-heretics.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UYG5g3L0DvvE0TIBs9cGDeHm5Rc>
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, 04 Jul 2019 01:30:15 -0000

Hi,

I work for ISOC but don't represent it in this discussion.  Also, I
seem to be sending more mail than is my habit today.

On Wed, Jul 03, 2019 at 07:21:26PM -0400, Keith Moore wrote:

> difficulties.    It used to be clear that you didn't deploy implementations
> based on Proposed Standard, but people did anyway.

When was that "clear"?  Just to pick a random example, RFC 2181
includes clarifications to the DNS specification that are absolutely
critical to the way DNS actually works, and that are certainly widely
deployed.  It's arguably something that ought to be considered a
formal part of STD 13.  It was published in 1997 and is a Proposed
Standard.  Given that STD 13 is only 10 years older than that, we've
lived with this Proposed Standard for much longer than we lived with
the unclear bits 2181 was designed to address.

And, of course, when STD 13 was published as RFCs 1034 and 1035 back
in 1987, it _wasn't_ an Internet standard, yet it seemed to get
deployed.  Indeed, the whole idea of "Internet Standard" seems to be
rather fluid leading up to the publication of RFC 1310, which came out
in 1992.  I note that RFC 1011, from 1987, lists the DNS with
"Recommended" status, but does not refer to the protocol documents we
rely on today but instead refers to RFCs 881-883.

I'm not trying to be querulous.  But some of my recent experiences
make me leery of assertions about how things got deployed in the past,
because I don't think that things were nearly as tidy as many people
today seem to be suggesting they were.  I was not among the people
connected to the Internet in the 1980s, but I know when I connected in
the 1990s I was both surprised how well things worked and dismayed at
how poorly they worked, often at the same time.  That experience, at
least, has not changed!

Best regards,

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com