Re: Proposed IESG statement on referencing documents behind a paywall

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 13 June 2019 01:17 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0542E120177 for <wgchairs@ietfa.amsl.com>; Wed, 12 Jun 2019 18:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 8VHQF6kSwMps for <wgchairs@ietfa.amsl.com>; Wed, 12 Jun 2019 18:17:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCBCC120018 for <wgchairs@ietf.org>; Wed, 12 Jun 2019 18:17:29 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 0C01D380BE for <wgchairs@ietf.org>; Wed, 12 Jun 2019 21:16:04 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 3E1BC1301; Wed, 12 Jun 2019 21:17:28 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3CB6991F for <wgchairs@ietf.org>; Wed, 12 Jun 2019 21:17:28 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: wgchairs@ietf.org
Subject: Re: Proposed IESG statement on referencing documents behind a paywall
In-Reply-To: <7A67EAB1-08D4-4901-8A43-0563C64EBA1B@gmail.com>
References: <7A67EAB1-08D4-4901-8A43-0563C64EBA1B@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 12 Jun 2019 21:17:28 -0400
Message-ID: <19514.1560388648@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/ZcJAbbd2pFLX4TkHedQwl_RHDic>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2019 01:17:32 -0000

Suresh Krishnan <suresh.krishnan@gmail.com> wrote:
    > In the past we have dealt with a few drafts that have had normative
    > references to paywalled documents and we have dealt with them on a
    > case-by-case basis (usually during or after IETF last call). In order
    > to get the working groups involved earlier in the process, the IESG is
    > working on issuing a statement on how to deal with such drafts and we
    > would greatly appreciate input from WG chairs on this topic. This is
    > the proposed text of the statement

Thank you for taking this on.
I hope that this means that the open-stand.org effort will also get rebooted,
although I recognize that's more an ISOC/LLC thing.

    > 1. The WG MUST be explicitly informed of any such normative reference
    > and the WG MUST reach consensus that it is acceptable. The
    > document shepherd MUST include this information in the shepherd
    > writeup.

I find this acceptable first step of the process.

I'm not sure what the WG should do when I say
  "Please take this work out of the IETF if I can't implement
   or validate an implementation without document FOO"

And, btw, I don't consider a non-paywall with some https://tosdr.org/
click through.  I want a URL for the document. When I click on it, I get the
document.  When I put a #foobar on the URL, I can reference a section of it,
and when I copy and paste from it into an email, I'm not violating their
copyright.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-