IETF Logo Mail Archive

Re: Proposed IESG statement on referencing documents behind a paywall

Toerless Eckert <tte@cs.fau.de> Thu, 13 June 2019 13:09 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 C01AE12013A for <wgchairs@ietfa.amsl.com>; Thu, 13 Jun 2019 06:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 b7A2JsAzUiU8 for <wgchairs@ietfa.amsl.com>; Thu, 13 Jun 2019 06:09:24 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9824B120153 for <wgchairs@ietf.org>; Thu, 13 Jun 2019 06:09:24 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 15CDD54807D; Thu, 13 Jun 2019 15:09:20 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 05533440041; Thu, 13 Jun 2019 15:09:19 +0200 (CEST)
Date: Thu, 13 Jun 2019 15:09:19 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Cc: wgchairs@ietf.org
Subject: Re: Proposed IESG statement on referencing documents behind a paywall
Message-ID: <20190613130919.a2kb4zibqey2yyvm@faui48f.informatik.uni-erlangen.de>
References: <7A67EAB1-08D4-4901-8A43-0563C64EBA1B@gmail.com> <132C3DCF-8AB4-4928-8F48-5D7A2E29859F@gmail.com> <20190612223145.my2uxqhr2zrs74z4@faui48f.informatik.uni-erlangen.de> <A5DEA6C2-61AD-45AE-B80C-4B369DDBE100@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A5DEA6C2-61AD-45AE-B80C-4B369DDBE100@gmail.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/7HYsPJLqiuxJxOWgnuNNWvfs9o8>
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 13:09:27 -0000

On Wed, Jun 12, 2019 at 11:45:26PM -0400, Suresh Krishnan wrote:
> Yes. This would be great, and we have managed to get free access to most (but not all) of the IEEE specs when needed. Also, we have different kind of relationships with different IEEE groups. e.g. we have had a very close relationship with IEEE 802 over the years and the published standards are mostly available for free. For the document mentioned above, we did make arrangements to make the document available for anyone who wanted to review. I started a second IETF Last call with the following message appended
> 
> "If you would like to review this document and
> would like a copy of the [IEEE1588] reference specification, please send a
> note to the Responsible AD <tictoc-ads@ietf.org> and the tictoc working
> group chairs <tictoc-chairs@ietf.org> and we will provide you a copy of 
> the document."

Maybe the easiest way would be to find someone friendly at IEEE to sponsor a
corporate account at IEEE or the like to enable this.

Cheers
    Toerless

v2.23.0 | Report a Bug | By Email