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

Julian Reschke <julian.reschke@gmx.de> Tue, 10 May 2011 05:15 UTC

Return-Path: <julian.reschke@gmx.de>
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 8B90EE066A for <ietf@ietfa.amsl.com>; Mon, 9 May 2011 22:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.565
X-Spam-Level:
X-Spam-Status: No, score=-104.565 tagged_above=-999 required=5 tests=[AWL=-1.966, 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 fFA85ZQ8GewT for <ietf@ietfa.amsl.com>; Mon, 9 May 2011 22:15:49 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 3EC2CE0665 for <ietf@ietf.org>; Mon, 9 May 2011 22:15:47 -0700 (PDT)
Received: (qmail invoked by alias); 10 May 2011 05:15:44 -0000
Received: from p508FCFB0.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.207.176] by mail.gmx.net (mp023) with SMTP; 10 May 2011 07:15:44 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19S6KIA3/lSvAKNn7VL67rCKReyn02jr+eq02aSW6 mbAn4V6qAqbjC0
Message-ID: <4DC8C9FB.6000604@gmx.de>
Date: Tue, 10 May 2011 07:15:39 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: How to pay $47 for a copy of RFC 793
References: <20110509234100.5411.qmail@joyce.lan> <CD34047985A5E024EA6F866C@PST.JCK.COM>
In-Reply-To: <CD34047985A5E024EA6F866C@PST.JCK.COM>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: John Levine <johnl@iecc.com>, mnot@mnot.net, 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: Tue, 10 May 2011 05:15:50 -0000

On 10.05.2011 03:44, John C Klensin wrote:
> John,
>
> Depends on where you look.  DOIs are popular in some
> communities, URNs in others, and, of course, some communities
> have not discovered either.  For most purposes, DOIs and URNs
> can be considered functionally equivalent, but one of the
> differences is that if we had to pay the usual fees for DOIs to
> assign them to RFCs, we might have to start charging for RFCs to
> cover those costs :-).  For more on the URN approach to
> identifying articles, papers, and similar things, you might look
> in on what the URNBIS WG is doing and why.

Reminder: we have a URN scheme of IETF documents. Maybe we should use it.

> Mark's (slightly tongue in cheek, I think) suggestion of URLs
> actually doesn't work because they generally identify locations
> at which objects can be found, rather than the object itself
> (location-independent).  But that is orthogonal to the question
> of preferences for DOIs versus URNs.

Well, if the organization minting the HTTP URIs is committed to 
stability, they are almost as good as URNs. Or better, given the fact 
that you can drop them into the address bar of a browser :-)

Best regards, Julian