Re: Proposed IESG statement on referencing documents behind a paywall

Stewart Bryant <stewart.bryant@gmail.com> Thu, 13 June 2019 10:49 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 1A7F2120110 for <wgchairs@ietfa.amsl.com>; Thu, 13 Jun 2019 03:49:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 Bklj_JO2ULRC for <wgchairs@ietfa.amsl.com>; Thu, 13 Jun 2019 03:49:39 -0700 (PDT)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (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 7F9D312010D for <wgchairs@ietf.org>; Thu, 13 Jun 2019 03:49:39 -0700 (PDT)
Received: by mail-wr1-x42e.google.com with SMTP id p13so10134363wru.10 for <wgchairs@ietf.org>; Thu, 13 Jun 2019 03:49:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Awh7n/c9HUUv7jiMjiUFmh6lIV0qP/wDI57kHaDUTEY=; b=LcFB8bgnaW0v1N5CrrAXv8/aP/P8EhmEaDpdusf4L0czFugHnqKgWoYkPIAWBQnz53 MhZjoNHz5hTM4RNXQJ4rvsa7GoFYSLgKJVqFEG9aIGMcVwLR/T+AwyknoaBMCw90rj11 UcoPA6l3t2WWVikbzSs3SpJsVyF5K8Xga4E+9tPjkO49xQEXZaF2GWDKyIXx874y1flR cRReWLRuqg4xUB8a8q7RpW1D67YuGg0hVLe3Q2t+GzH/dbcT2CCiwZjNztt+ECbKnFZd NicxcBV8ZYB3jHyluqdda+DFvkzwUUTuEH4Y2unRZeLL6KsXDt176eM+PP3U+szPKRTq guZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Awh7n/c9HUUv7jiMjiUFmh6lIV0qP/wDI57kHaDUTEY=; b=SR2507B+UAp/jI5FUnnwkruA6khRdKXDxPZ5pZaUy6CNhQcokAIqofh0I3uH6RCdNk XkWoZOW39oyVnEtiTM5ot/53D/XQlGCOMEPWqwV5n4p1hIVJxvHB/eIg/SukxOR0JQ/E oA7PkNIJIeQd93RuukJWMQhiYQOIqV1zSG9EIJdAqwevQfUBUazlWQt5PsqfGu+cP+vx vKhaA6xDIehdJxlyJr41zDOT3Rdo+8jDhPgyvvvDAKjLttbOTb8xhfsxoB5FsU8eli6P fDqRwGj+I0LVQwQI0yOg5h0tGxkJi7l+DqjB6fTECj21F5aQTTTBzK587xJ989C/rBaV 6eMg==
X-Gm-Message-State: APjAAAVu30kYE97vqwEpsSBeyf1PGA0/cSbQiuexza2cV92NiPTV2JpB oGD+L0sT4v2Yn4m5DTXNTwOpSEe3
X-Google-Smtp-Source: APXvYqwPzE9047YTLr5XLVqb6xc+WCoNZ/PXQjO/ogiMgMPYUuDR5WD4qXDr0SLAawm2SmOumCpxOA==
X-Received: by 2002:adf:b68a:: with SMTP id j10mr7753712wre.88.1560422977673; Thu, 13 Jun 2019 03:49:37 -0700 (PDT)
Received: from [192.168.178.22] ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id t198sm3968548wmt.2.2019.06.13.03.49.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Jun 2019 03:49:37 -0700 (PDT)
Subject: Re: Proposed IESG statement on referencing documents behind a paywall
To: Suresh Krishnan <suresh.krishnan@gmail.com>, Toerless Eckert <tte@cs.fau.de>
Cc: wgchairs@ietf.org
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>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <fca4c812-e7f4-5745-7129-a91d25c80af6@gmail.com>
Date: Thu, 13 Jun 2019 11:49:36 +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: <A5DEA6C2-61AD-45AE-B80C-4B369DDBE100@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/Sb4T29sEcz3VyVehhATThTDy130>
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 10:49:42 -0000

Please remember that there are many independent IEEE groups and IEEE1588
is part of the Test and Measurement group not 802.

WRT to IEEE1588v2, we negotiated its release to the IETFfor use in
IETF work, from before the time it was published. We did this when I was 
a chair of TICTOC. It has therefore been available on request for this 
purpose for its entire lifetime. I have not been asked for a copy for 
many years. Did we simply forget that we had access to this material?

- Stewart


On 13/06/2019 04:45, Suresh Krishnan wrote:
> Hi Toerless,
> 
>> On Jun 12, 2019, at 6:31 PM, Toerless Eckert <tte@cs.fau.de> wrote:
>>
>> Thanks Suresh
>>
>> 1) Is there a specific event or events tha ha let to picking up this
>> topic now ? Just curious, because i thought we have lived with this
>> situation for a long time unchanged. E.g.: has IEEE raised its prices (which i
>> would know because of my companies subscription...) ?
> 
> Yes. This is a result of a document going through the IETF process. The document in question is the draft that became RFC8575. It referred to the IEEE1588 spec that described some of the parameters being used in the yang module.
> 
>>
>> 2) Associated ask:
>>
>> I would like IETF if we can have a process by which IEEE
>> documents that are references to IETF document can be made
>> available FOR FREE to the reviewers of those drafts during the draft->RFC process.
>> Aka: Some form of IEEE membership account for IETF WG chairs, simple
>> email statement from reviewer back to chair to not disseminate the
>> document, and then chairs could pass on those documents as requested by
>> reviewers.
>>
>> Note that i would love to see this not only for normative but also
>> informative IEEE references to help reviewers.
>>
>> I know this does not scale to arbitrary SDOs, but IEEE seems to be the
>> most important one, and i think this should work for IEEE, and i can't
>> see how this would run the risk of being massively abused if we have WG chairs in
>> control of access.
> 
> 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."
> 
> Thanks
> Suresh
>