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

Yoav Nir <ynir@checkpoint.com> Sun, 08 May 2011 23:06 UTC

Return-Path: <ynir@checkpoint.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 7F132E0729 for <ietf@ietfa.amsl.com>; Sun, 8 May 2011 16:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.898
X-Spam-Level:
X-Spam-Status: No, score=-8.898 tagged_above=-999 required=5 tests=[AWL=1.700, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 Puier+plJEbp for <ietf@ietfa.amsl.com>; Sun, 8 May 2011 16:06:26 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id E26FFE06B1 for <ietf@ietf.org>; Sun, 8 May 2011 16:06:25 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p48N6Nuh014595 for <ietf@ietf.org>; Mon, 9 May 2011 02:06:23 +0300
X-CheckPoint: {4DC72F10-12-1B221DC2-FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 9 May 2011 02:06:23 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Mon, 9 May 2011 02:06:23 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: IETF Discussion <ietf@ietf.org>
Date: Mon, 09 May 2011 02:06:17 +0300
Subject: Re: How to pay $47 for a copy of RFC 793
Thread-Topic: How to pay $47 for a copy of RFC 793
Thread-Index: AcwN1IwKSGbvEtx0QGOWgIGgqsR32Q==
Message-ID: <61277E1A-ED35-43DA-B65A-0A95F69427B0@checkpoint.com>
References: <4DC71403.9010505@isi.edu>
In-Reply-To: <4DC71403.9010505@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_61277E1AED3543DAB65A0A95F69427B0checkpointcom_"
MIME-Version: 1.0
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: Sun, 08 May 2011 23:06:30 -0000

A bargain!  RFC 5996 goes for $58.

Does it come leather-bound with the title gold-stamped on the cover?

On May 9, 2011, at 1:06 AM, Bob Braden 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]

OK so far, except maybe for the DARPA part. Now look at footnote 12:

   12   RFC standards are available from Global Engineering Documents, 15 Inverness Way East, Englewood, CO 80112, USA (http://global.ihs.com/).

Going to that web site, you find:

RFC 793 - Complete Document
Revision / Edition: 81    Chg:    Date: 09/00/81
TRANSMISSION CONTROL PROTOCOL DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION

Comments:
Superseding Document:
Page Count:     90
In Stock:       Yes
Hardcopy Price:          $ 47.00        <cart_button.gif><http://global.ihs.com/shopping_cart.cfm?currency_code=USD&customer_id=21254C2B2E0A&shopping_cart_id=2925583B2B4B30204E5B5D37220A&rid=Z56&input_doc_number=RFC%20793&mid=5280&input_doc_number=RFC%20793&country_code=US&lang_code=ENGL&item_s_key=00123981&item_key_date=180331&electronic_delivery=N&shopping_cart_action=insert&input_doc_number=RFC%20793&input_doc_title=&origin=>

and:

Customers who purchased RFC 793 have also purchased
        EIA-748<http://global.ihs.com/doc_detail.cfm?currency_code=USD&customer_id=21254C2B2E0A&shopping_cart_id=2925583B2B4B30204E5B5D37220A&rid=Z56&input_doc_number=RFC%20793&mid=5280&input_doc_number=RFC%20793&country_code=US&lang_code=ENGL&input_doc_number=RFC%20793&input_doc_title=&item_s_key=00280332&item_key_date=920531&origin=DSSC> : EARNED VALUE MANAGEMENT SYSTEMS
        IETF RFC 2460<http://global.ihs.com/doc_detail.cfm?currency_code=USD&customer_id=21254C2B2E0A&shopping_cart_id=2925583B2B4B30204E5B5D37220A&rid=Z56&input_doc_number=RFC%20793&mid=5280&input_doc_number=RFC%20793&country_code=US&lang_code=ENGL&input_doc_number=RFC%20793&input_doc_title=&item_s_key=00503465&item_key_date=010031&origin=DSSC> : INTERNET PROTOCOL, VERSION 6 (IPV6) SPECIFICATION
        RFC 768<http://global.ihs.com/doc_detail.cfm?currency_code=USD&customer_id=21254C2B2E0A&shopping_cart_id=2925583B2B4B30204E5B5D37220A&rid=Z56&input_doc_number=RFC%20793&mid=5280&input_doc_number=RFC%20793&country_code=US&lang_code=ENGL&input_doc_number=RFC%20793&input_doc_title=&item_s_key=00122904&item_key_date=190403&origin=DSSC> : USER DATAGRAM PROTOCOL
        RFC 791<http://global.ihs.com/doc_detail.cfm?currency_code=USD&customer_id=21254C2B2E0A&shopping_cart_id=2925583B2B4B30204E5B5D37220A&rid=Z56&input_doc_number=RFC%20793&mid=5280&input_doc_number=RFC%20793&country_code=US&lang_code=ENGL&input_doc_number=RFC%20793&input_doc_title=&item_s_key=00122565&item_key_date=180331&origin=DSSC> : INTERNET PROTOCOL DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION

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 Braden

<ATT00002..txt>