RE: BCP97bis

ned+ietf@mauve.mrochek.com Mon, 18 October 2021 13:05 UTC

Return-Path: <ned+ietf@mauve.mrochek.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 8E8A83A1363 for <ietf@ietfa.amsl.com>; Mon, 18 Oct 2021 06:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 t6qUfUmu0z2P for <ietf@ietfa.amsl.com>; Mon, 18 Oct 2021 06:05:26 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (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 8D31D3A135B for <ietf@ietf.org>; Mon, 18 Oct 2021 06:05:17 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01S53VG00ZW000JTG6@mauve.mrochek.com> for ietf@ietf.org; Mon, 18 Oct 2021 06:00:07 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01S51OYHBMZ4005PTU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 18 Oct 2021 05:59:59 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Cc: 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, 'Michael Richardson' <mcr+ietf@sandelman.ca>, "'Joel M. Halpern'" <jmh@joelhalpern.com>, 'IETF' <ietf@ietf.org>
Message-id: <01S53VFTRVD6005PTU@mauve.mrochek.com>
Date: Mon, 18 Oct 2021 05:49:08 -0700 (PDT)
Subject: RE: BCP97bis
In-reply-to: "Your message dated Sat, 16 Oct 2021 18:20:51 -0700" <00cf01d7c2f5$3a43fff0$aecbffd0$@acm.org>
References: <CAL0qLwbwvs2Cp_urgJ=hzc6yEMGDaz3C0xf6RQXRrB89wAx=Rw@mail.gmail.com> <CAL0qLwavK5dYdmYPVxdMT5rA=jBZv1cEyAsVBEWOD7p9MoZR1g@mail.gmail.com> <C657F78F-FF99-4898-8A08-844B32589DDE@vigilsec.com> <CAL0qLwbLqyWSqFGL2x-FpXXD19QG9-eZkrnTVm_fxt3tUfZSgg@mail.gmail.com> <C92D456E-63ED-453B-8F33-3AAECA40D1DA@vigilsec.com> <27721119-D39D-427D-8EEE-C5027DA15B06@akamai.com> <007c01d7c2dc$9090c780$b1b25680$@acm.org> <5385fd6f-b7a7-3baa-1374-f4d8d87216fd@joelhalpern.com> <6454.1634428177@localhost> <6702b78c-037f-f5fd-78a6-901a999dab54@gmail.com> <00cf01d7c2f5$3a43fff0$aecbffd0$@acm.org>
To: Larry Masinter <LMM@acm.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GYwU3Zd8HfZuhFNXIigON73aqgU>
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: Mon, 18 Oct 2021 13:05:32 -0000

> This goes into the same mix as "SDO's rethinking business model".
> Surely IEEE would benefit from working citations from IETF to IEEE
> documents, in a form that IEEE commits to stability.


> https://www.w3.org/blog/news/archives/2875

> References to resources that can't be read by IETF reviewers
> should not be accepted -- perhaps there were some cases in the
> past but things have changed.

Speaking as a media type reviewer, I require free access to the relevant
standards before I'll review a media type in the standards tree. This has led
various special arrangements to access specifications that would otherwise cost
$$$.

Note that this doesn't mean that free access is required for everyone. The
requirements for media types in the standards tree are that there be a  stable,
publicly available specification. Free availability is not part of it.

> References to resources that are available now but you're worried they will
> be moved or exhobitantly paywalled or lost -- keep "if needed" copies.

While I'm not aware of it happening, it's theoretically possible for a
standards organization to fail and take all of its specifications with it,
just like any other organization.

In the case of media types, what constitutes a standards organization able to
register types in the standards tree is up to the IESG to access. In theory
that assessment includes an accessment of the organizations likely stability.

				Ned

> Just to take "stability of reference" off the table. I read of legal
> documents and judements being subject to this for similar archival goals.

> --
> https://LarryMasinter.net https://interlisp.org