BCP97bis and "freely available"

John C Klensin <john-ietf@jck.com> Mon, 18 October 2021 13:33 UTC

Return-Path: <john-ietf@jck.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 64B2A3A13B9 for <ietf@ietfa.amsl.com>; Mon, 18 Oct 2021 06:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 XwPIcDR7QnGJ for <ietf@ietfa.amsl.com>; Mon, 18 Oct 2021 06:33:50 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88FD83A0DE2 for <ietf@ietf.org>; Mon, 18 Oct 2021 06:33:48 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1mcSls-000P9o-Hl; Mon, 18 Oct 2021 09:33:44 -0400
Date: Mon, 18 Oct 2021 09:33:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
cc: ietf <ietf@ietf.org>
Subject: BCP97bis and "freely available"
Message-ID: <8E6C9FDEA828F341AA36F39C@PSB>
In-Reply-To: <849D7F9E-8AD4-4CE8-A66C-358FB1F2E6AE@tzi.org>
References: <CAL0qLwbwvs2Cp_urgJ=hzc6yEMGDaz3C0xf6RQXRrB89wAx=Rw@mail.gmail.com> <CAL0qLwavK5dYdmYPVxdMT5rA=jBZv1cEyAsVBEWOD7p9MoZR1g@mail.gmail.c om> <CAL0qLwa4ChOsuMkmoP_sAGv3Wn2AcSz1OkijmxZzP+MGvnwviA@mail.gmail.com> <849D7F9E-8AD4-4CE8-A66C-358FB1F2E6AE@tzi.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jgtrU-i8pTPcBb7_8GFOFLSUR9A>
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:33:59 -0000

Hi.

In looking through the new -01 draft (even though this text has
not changed) I noticed something that I sort of hinted at
yesterday in responding to other comments.

You need to define "freely available" and do so precisely.  

We have historically considered printed books and articles in
established journals to be suitable for normative references
from the RFC Series ("down" really has nothing to do with that
criterion) even if buying the book or obtaining the journal was
expensive.  In theory, there was always a trip to the library.
Some of the standards from other SDOs have the same property:
they are often very expensive unless one's organization is a
member that gets them for free, but many libraries and other
repositories do have them available.

Of course, some of us have access to better technical libraries
than others. That is an economic and cultural problem I don't
know how to fix, but I'm fairly sure that pushing in the
direction of "must be available online, with no restrictions and
no cost" would be quite self-destructive for the IETF.

"Freely available" does not necessarily imply "free" (zero cost).

By contrast, one can imagine a reference to a restricted
corporate document, some types of prepublication drafts, and, if
the world continues to fragment, even the detailed description
of how some equipment operates.  In those cases, the document
may just not be "available" to many IETF participants even
though, if someone were allowed to access it, it would be at no
cost.

So the I-D should be very clear about what it is talking about.
Then, if needed, we can have a better discussion about the
requirements.

best,
    john