Re: Proposed IESG statement on referencing documents behind a paywall

Stewart Bryant <stewart.bryant@gmail.com> Fri, 14 June 2019 11:12 UTC

Return-Path: <stewart.bryant@gmail.com>
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 7C6D21201AF for <wgchairs@ietfa.amsl.com>; Fri, 14 Jun 2019 04:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 pODKEU9QySqH for <wgchairs@ietfa.amsl.com>; Fri, 14 Jun 2019 04:12:33 -0700 (PDT)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 035D8120077 for <wgchairs@ietf.org>; Fri, 14 Jun 2019 04:12:33 -0700 (PDT)
Received: by mail-wm1-x335.google.com with SMTP id u8so1921000wmm.1 for <wgchairs@ietf.org>; Fri, 14 Jun 2019 04:12:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=p/7kO9s11lKRiCVZJfMI1EIqfGyZmu4YFwaQc5GL7Ko=; b=Ax02JpzTDuGr3cILxtrWwRLfpsP5UYGz5RdW1fM3WB/vHVuvDqtcay7cEPrfOlV+WS wy847qo6kl7oNAG76b1CzdzGISNvM6fbX/6Oeq+sOcrZ0yACLfPHFjE1qmzynT9ukhdj llCLVVgHBbCmJI0vPPIgVzG1fwFMj4A35T9dkoyBMt+4CY9U2dB1RWbHU1hR0/isKNVm tYltjf/wDELr+cxjzY5EGHXiXs5VtLJelwkM/kutrSRex1WhQehc6hsqdzGPXaarVFHr NdGmcuDeFqbYSgf1MisLlFK/1O0RDZUwn4gn/0yaK4pZ9O0zrU+5xHGRgaB5T4HHdkgJ LjzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=p/7kO9s11lKRiCVZJfMI1EIqfGyZmu4YFwaQc5GL7Ko=; b=EhJKEycmb5Zof8vB/LmfTbi5fFiATqicJyRwajns5Y7F/Aze9XtG9tQw73C3LW8uhT MUfYDE3EY3jfov6WMY+AG6RftjA0xBOFGXSs4JUARZZh2IT8pkqLIMoOJWJmwpJyBmVN wSvhIIENkQxDWr3mehwD1/iICxJv0VjHPrmS2nieio/jH7hOnP5Nat+aAaV2yttDwItG tU6gV16UTtWJoD9iADbORobDjTWZQvM+JIRAQoP/eXc/WjxedV2YPaG1bK4x4yxIq9D2 taNVREue/P286zwZuxLicKLxnrh9l8qRWWw2kSUJbBi59X7voiC9B2KbEl/TVnv/yXya aM1Q==
X-Gm-Message-State: APjAAAVbOKCm1yQv4w25rQ/NgIKS614e/Z4XvOz0jhY2wcguU9oJcM6D dDX5b2e3xewJsZEktZ+D7iQ3eziX++0=
X-Google-Smtp-Source: APXvYqyyt8wQHQ/R9rjthu1SlHnVm5Sv1HyPZvYktPAIBqxZU5IgfeJScIyHr3nLQYDSOYh5XfJZjg==
X-Received: by 2002:a1c:701a:: with SMTP id l26mr7221537wmc.32.1560510751189; Fri, 14 Jun 2019 04:12:31 -0700 (PDT)
Received: from [192.168.178.22] ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id b2sm3082500wrp.72.2019.06.14.04.12.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Jun 2019 04:12:30 -0700 (PDT)
Subject: Re: Proposed IESG statement on referencing documents behind a paywall
To: Suresh Krishnan <suresh.krishnan@gmail.com>, wgchairs@ietf.org
References: <7A67EAB1-08D4-4901-8A43-0563C64EBA1B@gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <ba5a5d20-1199-abf5-a4c5-047bd281cbf1@gmail.com>
Date: Fri, 14 Jun 2019 12:12:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <7A67EAB1-08D4-4901-8A43-0563C64EBA1B@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/SkaUOua6yt32a7V0yGv7l1NsdfA>
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: Fri, 14 Jun 2019 11:12:35 -0000


On 12/06/2019 23:00, Suresh Krishnan wrote:
> *** START TEXT ***
> 
> As described in Section 7.1 of RFC 2026, RFCs may have normative
> references on external standards.
> 
> In some cases, however, those references are themselves not generally
> available (for instance, they might be accessible only after paying
> a fee). This can interfere both with the ability of implementers
> to implement the protocol as well as with the ability of the IETF
> community to review it.
> 
> In such cases:
> 
> 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.
> 
> 2. The reference MUST be explicitly noted as part of the IETF Last
>   Call. If such a note is omitted, the last call MUST be repeated
>   after including it.

3. Where the reference has been made available to the WG for the
purposes of their work, this fact, together with details of how
reviewers can gain access to the reference for the purposes of their
review MUST also be provided as part of IETF Last Call.

- Stewart


> 
> *** END TEXT ***