Re: Proposed IESG statement on referencing documents behind a paywall
Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 12 June 2019 22:38 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 5F9BE1201A0 for <wgchairs@ietfa.amsl.com>; Wed, 12 Jun 2019 15:38:48 -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 HtR8arlBiJz3 for <wgchairs@ietfa.amsl.com>; Wed, 12 Jun 2019 15:38:46 -0700 (PDT)
Received: from outgoing-alum.mit.edu (outgoing-alum.mit.edu [18.7.68.33]) (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 A340B12017C for <wgchairs@ietf.org>; Wed, 12 Jun 2019 15:38:46 -0700 (PDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id x5CMcico025043 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <wgchairs@ietf.org>; Wed, 12 Jun 2019 18:38:45 -0400
Subject: Re: Proposed IESG statement on referencing documents behind a paywall
To: wgchairs@ietf.org
References: <7A67EAB1-08D4-4901-8A43-0563C64EBA1B@gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <4c45183b-6636-d39b-6970-dce49af1ecbb@alum.mit.edu>
Date: Wed, 12 Jun 2019 18:38:44 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; 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-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/qj0Ti2j1PllAwcXzVCZdL_tqHug>
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: Wed, 12 Jun 2019 22:38:49 -0000
IMO it would be better if the citation explicitly indicated that this document has a pay wall or limited access. Thanks, Paul On 6/12/19 6:00 PM, Suresh Krishnan wrote: > Hi chairs, > 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 > > *** 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. > > *** END TEXT *** > > Please go over this text and let me know if you have any concerns, comments, or additions by 2019/06/26. > > Thanks > Suresh >
- Re: Proposed IESG statement on referencing docume… Stephen Farrell
- Proposed IESG statement on referencing documents … Suresh Krishnan
- Re: Proposed IESG statement on referencing docume… Fred Baker
- Re: Proposed IESG statement on referencing docume… Toerless Eckert
- Re: Proposed IESG statement on referencing docume… Paul Kyzivat
- Re: Proposed IESG statement on referencing docume… Bernie Volz (volz)
- RE: Proposed IESG statement on referencing docume… tobias.gondrom
- Re: Proposed IESG statement on referencing docume… Salz, Rich
- Re: Proposed IESG statement on referencing docume… Michael Richardson
- Re: Proposed IESG statement on referencing docume… Toerless Eckert
- Re: [EXTERNAL] [BOFChairs] Proposed IESG statemen… Deen, Glenn (NBCUniversal)
- Re: [EXTERNAL] [BOFChairs] Proposed IESG statemen… Toerless Eckert
- Re: Proposed IESG statement on referencing docume… Suresh Krishnan
- Re: Proposed IESG statement on referencing docume… Suresh Krishnan
- Re: [BOFChairs] Proposed IESG statement on refere… Deen, Glenn (NBCUniversal)
- Re: Proposed IESG statement on referencing docume… Stewart Bryant
- Re: Proposed IESG statement on referencing docume… Stewart Bryant
- Re: Proposed IESG statement on referencing docume… Toerless Eckert
- Re: Proposed IESG statement on referencing docume… Karen O'Donoghue
- Re: [EXTERNAL] [BOFChairs] Proposed IESG statemen… Michael Richardson
- Re: Proposed IESG statement on referencing docume… Michael Richardson
- Re: Proposed IESG statement on referencing docume… Andrew G. Malis
- Re: [BOFChairs] Proposed IESG statement on refere… Heather Flanagan
- RE: Proposed IESG statement on referencing docume… Linda Dunbar
- Re: Proposed IESG statement on referencing docume… Stewart Bryant
- Re: [BOFChairs] Proposed IESG statement on refere… Toerless Eckert
- Re: Proposed IESG statement on referencing docume… Toerless Eckert
- Re: [BOFChairs] Proposed IESG statement on refere… Michael Richardson
- Re: Proposed IESG statement on referencing docume… Suresh Krishnan
- Re: Proposed IESG statement on referencing docume… Suresh Krishnan
- Re: Proposed IESG statement on referencing docume… Suresh Krishnan
- Re: [EXTERNAL] [BOFChairs] Proposed IESG statemen… Suresh Krishnan
- Re: Proposed IESG statement on referencing docume… Suresh Krishnan
- Re: Proposed IESG statement on referencing docume… Suresh Krishnan
- Re: Proposed IESG statement on referencing docume… Stewart Bryant
- Re: Proposed IESG statement on referencing docume… Salz, Rich
- RE: Proposed IESG statement on referencing docume… Black, David
- Re: Proposed IESG statement on referencing docume… Sean Turner
- Re: [BOFChairs] Proposed IESG statement on refere… Heather Flanagan
- Re: [BOFChairs] Proposed IESG statement on refere… Sean Turner
- Re: Proposed IESG statement on referencing docume… Keith Drage
- RE: Proposed IESG statement on referencing docume… Roni Even (A)