Re: How to pay $47 for a copy of RFC 793
John C Klensin <john-ietf@jck.com> Thu, 12 May 2011 14:42 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6E96E06A3 for <ietf@ietfa.amsl.com>; Thu, 12 May 2011 07:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ung7U08qBlcT for <ietf@ietfa.amsl.com>; Thu, 12 May 2011 07:42:13 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 60932E06BE for <ietf@ietf.org>; Thu, 12 May 2011 07:42:12 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QKX5T-0008NG-NS; Thu, 12 May 2011 10:41:59 -0400
Date: Thu, 12 May 2011 10:41:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: Steven Bellovin <smb@cs.columbia.edu>, Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: How to pay $47 for a copy of RFC 793
Message-ID: <4B943854EB9CB71C682ABB89@PST.JCK.COM>
In-Reply-To: <C5EDCF1C-E0EA-43A7-B1C4-FFC399F52DBF@cs.columbia.edu>
References: <4DC71403.9010505@isi.edu> <4DC9ACA3.7030808@necom830.hpcl.titech.ac.jp> <C5EDCF1C-E0EA-43A7-B1C4-FFC399F52DBF@cs.columbia.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2011 14:42:17 -0000
--On Wednesday, May 11, 2011 16:43 -0400 Steven Bellovin <smb@cs.columbia.edu> wrote: >> It is a lot more time (and money) saving to search free >> versions before entering transactions to purchase them than >> to rely blindly on PubMed, IEEE, ACM, google scholar etc. > > Unfortunately, the IEEE has tightened its copyright policy; see > http://www.ieee.org/publications_standards/publications/rights > /paperversionpolicy.html for details. Steve, It seems to me that this policy applies to documents published by the IEEE and that it has no direct effect on IETF (or RFC Editor)-published documents. Interestingly, it is also very similar to a generally-understood historical version of the policy wrt RFCs at least before the IETF community started practicing "amateur lawyer": I-Ds and other prepublication documents basically belong to the authors and they can do with them as they like (the IETF Trust is now insisting on attaching copyright notices to I-Ds; let's not start another debate about the legitimacy of that practice). By contrast, RFCs involve some value-added by the RFC Editor, copyright assertions have been made for a decade or two, and "we" have tried to control derivative publications. The main difference is also familiar: the IETF wants to limit reproduction permission for published versions (presumably to continue to make money on them to offset other expenses) while we permit unlimited distribution and reproduction without special permission as long as the documents are intact or meet specific other criteria. A second difference is that we've never asked folks to go find online versions of I-Ds and update them to point explicitly to the successor RFCs. I have no idea how one actually does that or enforces it but, in principle, it is an idea we might actually find it beneficial to consider. Finally, the IEEE insists on formal copyright transfer at a well-defined point (and, as far as I know, always has). "We" don't think we need that. best, john
- How to pay $47 for a copy of RFC 793 Bob Braden
- Re: How to pay $47 for a copy of RFC 793 todd glassey
- Re: How to pay $47 for a copy of RFC 793 todd glassey
- Re: How to pay $47 for a copy of RFC 793 Yoav Nir
- Re: How to pay $47 for a copy of RFC 793 John Levine
- Re: How to pay $47 for a copy of RFC 793 John R. Levine
- Re: How to pay $47 for a copy of RFC 793 Steven Bellovin
- Re: How to pay $47 for a copy of RFC 793 John C Klensin
- Re: How to pay $47 for a copy of RFC 793 Mark Nottingham
- Re: How to pay $47 for a copy of RFC 793 Ole Jacobsen
- RE: How to pay $47 for a copy of RFC 793 Michel Py
- Re: How to pay $47 for a copy of RFC 793 Stefan Winter
- Re: How to pay $47 for a copy of RFC 793 Eric Burger
- RE: How to pay $47 for a copy of RFC 793 Worley, Dale R (Dale)
- Re: How to pay $47 for a copy of RFC 793 Bob Braden
- Re: How to pay $47 for a copy of RFC 793 Marshall Eubanks
- Re: How to pay $47 for a copy of RFC 793 Doug Barton
- Re: How to pay $47 for a copy of RFC 793 John Levine
- Re: How to pay $47 for a copy of RFC 793 Steve Crocker
- Re: How to pay $47 for a copy of RFC 793 Dave Crocker
- Re: How to pay $47 for a copy of RFC 793 John C Klensin
- RE: How to pay $47 for a copy of RFC 793 Ross Callon
- Re: How to pay $47 for a copy of RFC 793 Pekka Savola
- Re: How to pay $47 for a copy of RFC 793 Julian Reschke
- Re: How to pay $47 for a copy of RFC 793 John C Klensin
- RE: How to pay $47 for a copy of RFC 793 John C Klensin
- Re: How to pay $47 for a copy of RFC 793 John Levine
- Re: How to pay $47 for a copy of RFC 793 John C Klensin
- Re: How to pay $47 for a copy of RFC 793 J.D. Falk
- Re: How to pay $47 for a copy of RFC 793 Harald Alvestrand
- Re: Google Scholar, was How to pay $47 for a copy… John Levine
- Re: Google Scholar, was How to pay $47 for a copy… Harald Alvestrand
- Re: Google Scholar, was How to pay $47 for a copy… Paul Hoffman
- Re: Google Scholar, was How to pay $47 for a copy… Klaas Wierenga
- Re: How to pay $47 for a copy of RFC 793 Thomas Dreibholz
- Re: Google Scholar, was How to pay $47 for a copy… Harald Alvestrand
- Re: Google Scholar, was How to pay $47 for a copy… John C Klensin
- Re: How to pay $47 for a copy of RFC 793 Eric Burger
- Re: Google Scholar, was How to pay $47 for a copy… Harald Alvestrand
- Re: How to pay $47 for a copy of RFC 793 Masataka Ohta
- Re: How to pay $47 for a copy of RFC 793 Eric Burger
- Re: How to pay $47 for a copy of RFC 793 Masataka Ohta
- Re: How to pay $47 for a copy of RFC 793 John Levine
- Re: How to pay $47 for a copy of RFC 793 Masataka Ohta
- RE: How to pay $47 for a copy of RFC 793 Yoav Nir
- RE: How to pay $47 for a copy of RFC 793 Yaakov Stein
- RE: How to pay $47 for a copy of RFC 793 Yaakov Stein
- Re: How to pay $47 for a copy of RFC 793 Stephane Bortzmeyer
- RE: How to pay $47 for a copy of RFC 793 John R. Levine
- Re: How to pay $47 for a copy of RFC 793 Florian Weimer
- Re: How to pay $47 for a copy of RFC 793 Steven Bellovin
- Re: How to pay $47 for a copy of RFC 793 Joe Touch
- Re: How to pay $47 for a copy of RFC 793 SM
- Re: How to pay $47 for a copy of RFC 793 John C Klensin
- Re: How to pay $47 for a copy of RFC 793 Steven Bellovin
- Re: How to pay $47 for a copy of RFC 793 Joe Touch
- Re: How to pay $47 for a copy of RFC 793 Joe Touch
- Re: How to pay $47 for a copy of RFC 793 Bob Hinden
- Re: How to pay $47 for a copy of RFC 793 John C Klensin
- Re: How to pay $47 for a copy of RFC 793 Florian Weimer
- Re: How to pay $47 for a copy of RFC 793 Bob Hinden
- Re: How to pay $47 for a copy of RFC 793 Steve Crocker
- Re: How to pay $47 for a copy of RFC 793 Julian Reschke
- The XML page cannot be displayed t.petch
- Re: The XML page cannot be displayed Julian Reschke
- Re: The XML page cannot be displayed Simon Perreault
- Re: The XML page cannot be displayed Marc Manthey
- Re: The XML page cannot be displayed t.petch
- Re: The XML page cannot be displayed Doug Barton
- Re: The XML page cannot be displayed t.petch
- Re: The XML page cannot be displayed Julian Reschke
- Re: The XML page cannot be displayed Simon Perreault