Re: Proposed IESG statement on referencing documents behind a paywall

Suresh Krishnan <suresh.krishnan@gmail.com> Thu, 13 June 2019 03:45 UTC

Return-Path: <suresh.krishnan@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 A1B93120152 for <wgchairs@ietfa.amsl.com>; Wed, 12 Jun 2019 20:45:30 -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 BwJRzEMjKlup for <wgchairs@ietfa.amsl.com>; Wed, 12 Jun 2019 20:45:28 -0700 (PDT)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 9996012008B for <wgchairs@ietf.org>; Wed, 12 Jun 2019 20:45:28 -0700 (PDT)
Received: by mail-yb1-xb2d.google.com with SMTP id g62so7232449ybg.7 for <wgchairs@ietf.org>; Wed, 12 Jun 2019 20:45:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=eabKS3ydxXy9EnbMfKAIZ1rA3hg+Wt19/KZ6vA1uN68=; b=QC8PX4BpNcjBEoB6VDpu3u1rm0V8PqJYzi9ByuE93GrGYUD+wYCTBmT5WbQl8X+fqh 4reHTSuwsYyXEwJo7JISt5Za196qPIXBuyI0isnCg6B+iX71XmGWWmkBCgzvtpG+RaO4 QjzxIzXNSWqFmyLQNWYQ9TfNXALMaiy2eOQM6HAPsTUKZa745FhPQnHaycDPYBNAltgA 2XTjgZyWZZH89boeQKI/D0gKf7c1xP7EHlRsdHAAIB+TmIe//VsVK/7psWNMJIIwNbKx gAc78r4EdQZvZx981gSjY+f1sQKWNysDGtN9HOW/2olTnbqG+tn0S7xCXVOmNLFfYf94 WveA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=eabKS3ydxXy9EnbMfKAIZ1rA3hg+Wt19/KZ6vA1uN68=; b=j8HjJUYETmsthFlMfoF3Whg3w68XB1eMKDW4fHH2phKcaYhkQbkhb/fduYiqV3ny4V wDulmOBZSNAcLmKHY6QBjvqJWI7cY7xYbk7jSQ+HZS+tGn8GULwp5ZTMN187PTurLFcZ ZLQE1tesZeiL6cMzR3iHFn7/wGFLt70IP/xZBqQdNV1qxNsBF2FAMKk+qz/yXIgkYP94 MJy3H2Zhtz3f75hFTXOWD0597YgM4UzAGD0OJMNQh0V4Jnf6qZD/9kMTlt0kvcd2M/DZ yPpzdbxVleHgz9/J50xSEt53XRjgZ0Qsx4+W3kQS5YvXAT9Eu1SVAjOl2si8q1VmwNlA bp2w==
X-Gm-Message-State: APjAAAUrfiNUAzKwpQiwSQF5yjdnARNaO6c+lEti0fGSlU3GrauP1JFC FnCrILuWfd2I8S0pcoHBu1U=
X-Google-Smtp-Source: APXvYqwysF8XJjQfzD2UPFLmTZDaK/h3mcaEcqIERKgrKzz7bCYyQXvTJefST7mavkxF4YssH/v7BQ==
X-Received: by 2002:a25:b086:: with SMTP id f6mr33733672ybj.481.1560397527742; Wed, 12 Jun 2019 20:45:27 -0700 (PDT)
Received: from [10.0.0.15] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id 204sm464665ywx.54.2019.06.12.20.45.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Jun 2019 20:45:26 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Proposed IESG statement on referencing documents behind a paywall
From: Suresh Krishnan <suresh.krishnan@gmail.com>
In-Reply-To: <20190612223145.my2uxqhr2zrs74z4@faui48f.informatik.uni-erlangen.de>
Date: Wed, 12 Jun 2019 23:45:26 -0400
Cc: Fred Baker <fredbaker.ietf@gmail.com>, wgchairs@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5DEA6C2-61AD-45AE-B80C-4B369DDBE100@gmail.com>
References: <7A67EAB1-08D4-4901-8A43-0563C64EBA1B@gmail.com> <132C3DCF-8AB4-4928-8F48-5D7A2E29859F@gmail.com> <20190612223145.my2uxqhr2zrs74z4@faui48f.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/zqBaS8FUeVVRr28fucvoBOIOb-I>
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 03:45:31 -0000

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