Re: How to pay $47 for a copy of RFC 793

Eric Burger <eburger@standardstrack.com> Mon, 09 May 2011 12:12 UTC

Return-Path: <eburger@standardstrack.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 969C7E0795 for <ietf@ietfa.amsl.com>; Mon, 9 May 2011 05:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level:
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, 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 D35EkUmAJ6OB for <ietf@ietfa.amsl.com>; Mon, 9 May 2011 05:12:38 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [66.117.3.189]) by ietfa.amsl.com (Postfix) with ESMTP id BD3A6E06CA for <ietf@ietf.org>; Mon, 9 May 2011 05:12:38 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Message-Id:References:To:X-Mailer; b=y2jrlTgtcVGfH+2FdA3qxD4t+5YWa9zMhsB4Mxze4s9whOfxyGN5YxqPyWkZ1j6CFrARkbORtrhsuNcOGcZOgce9qfszfh0N99yTMX8tdCtnca3SAo+IjMQVYWnX9vxT;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.126]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QJO1S-0005OY-C1; Mon, 09 May 2011 03:49:06 -0700
Subject: Re: How to pay $47 for a copy of RFC 793
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary="Apple-Mail-21-213594544"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <09015639CC2A89B93663FBF0@PST.JCK.COM>
Date: Mon, 09 May 2011 06:51:48 -0400
Message-Id: <27DE75AD-F1AB-47DB-B2B2-A7DAA1BE7A1E@standardstrack.com>
References: <4DC71403.9010505@isi.edu> <09015639CC2A89B93663FBF0@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
Cc: IETF <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: Mon, 09 May 2011 12:12:39 -0000

Agreeing with John here re: it's just a bug.

IEEE Xplore regularly does "deals" (read: free) to add publishers to the digital library. It is part of the network effect from their perspective: if you are more likely to get a hit using their service, you are more likely to use the service.

We (RFC Editor? IAOC? Me as an individual?) can approach IEEE to add the RFC series to Xplore.

On May 9, 2011, at 1:32 AM, John C Klensin wrote:

> 
> 
> --On Sunday, May 08, 2011 15:06 -0700 Bob Braden
> <braden@isi.edu> wrote:
> 
>> I just discovered an astonishing example of misinformation,
>> shall we say, in the IEEE electric power community. There is
>> an IEEE standards document C37.118, entitled (you don't care)
>> "IEEE Standard for Synchrophasors for Power Systems
>> C37-118(TM)-2005", which is currently of great importance for
>> the instrumentation of the national power grid. I just noticed
>> that it references RFC 793, and for curiosity looked to see
>> how it was referenced. I found:
>> 
>>    [B8] RFC 793-1981,Transmission Control Protocol DARPA
>> Internet Program Protocol Specification.[12]
>> ...
>> Now, it has always been IETF's (and even before there was an
>> IETF, Jon Postel's) policy to allow people to sell RFCs. What
>> astonishes me is that clever people in the IEEE don't know
>> RFCs are available free online. I guess RFCs remain so
>> counter-cultural that industrial types don't get it. I wonder
>> how many other IEEE standards contain similar RFC-for-pay
>> references..
> 
> Bob,
> 
> What you presumably remember, but others reading this may not,
> was just how many comments Jon made about the impossibility of
> preventing fools from throwing their money away.  And, of
> course, it is in the interest of Global Engineering Documents
> --which, in the era in which few folks had direct access to the
> Internet was one of the better sources for miscellaneous
> technical standards documents-- to let people continue to
> believe that they are a convenient and standard (sic) source.
> 
> 
> 
> --On Sunday, May 08, 2011 21:26 -0400 "John R. Levine"
> <johnl@iecc.com> wrote:
> 
>> ...
>> This isn't an enormous project, but it requires figuring out
>> which online libraries are worth getting into, making the
>> necessary arrangements with them (which may or may not involve
>> money), a batch process to load in all the existing RFCs, and
>> arrange with the production house to ensure that each new RFC
>> gets listed as it's published.  Most of these systems include
>> abstracts and forward and backward references, which will
>> doubtless require some debugging to make them work reliably.
>> 
>> Like I said, it's a good project for the new RFC series
>> editor.  It should be a lot easier than deciding how to put
>> Chinese names into RFCs.
> 
> +1
> 
> I do note, however, that RFCs appear to be listed in ACM's Guide
> to Computing Literature (essentially part of the ACM Digital
> Library at this stage).  Putting "Transmission Control Protocol"
> into the search mechanism turns up RFC 793 in a hurry.  And,
> behold, they have full text available and retrieving it works
> without any charges other than the access fees for the Digital
> Library itself.  "RFC Editor" is even on their list of
> publishers for search purposes.  
> 
> The problem is that the titles they index do not contain the RFC
> numbers, so looking up "RFC793" or "RFC 793".  That is not a
> decision to avoid indexing the series (which would require the
> process John outlines to reverse) but a bug.   I have filed a
> bug report as Digital Library feedback.
> 
>    john
> 
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf