RE: ISSN for RFC Series under Consideration

"Hallam-Baker, Phillip" <pbaker@verisign.com> Fri, 23 May 2008 14:49 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 381CC28C277; Fri, 23 May 2008 07:49:52 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54B5328C287 for <ietf@core3.amsl.com>; Fri, 23 May 2008 07:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.9
X-Spam-Level:
X-Spam-Status: No, score=-5.9 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A2QArVqCSOEE for <ietf@core3.amsl.com>; Fri, 23 May 2008 07:49:50 -0700 (PDT)
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by core3.amsl.com (Postfix) with ESMTP id 96EBA3A6B24 for <ietf@ietf.org>; Fri, 23 May 2008 07:49:20 -0700 (PDT)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35]) by robin.verisign.com (8.12.11/8.13.4) with ESMTP id m4NEmX2l006104; Fri, 23 May 2008 07:49:17 -0700
Received: from MOU1WNEXMB09.vcorp.ad.vrsn.com ([10.25.15.197]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 23 May 2008 07:49:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: ISSN for RFC Series under Consideration
Date: Fri, 23 May 2008 07:49:03 -0700
Message-ID: <2788466ED3E31C418E9ACC5C316615572FF8F4@mou1wnexmb09.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: ISSN for RFC Series under Consideration
Thread-Index: Aci8Iae5r/nl7fgHSc6MSYFBLg/ktgAwJPuL
References: <C45AE963.389F6%mshore@cisco.com><00FD433C-24C0-4007-B44E-8E073B9BC757@shinkuro.com><0BDFFF51DC89434FA33F8B37FCE363D511F9504F@zcarhxm2.corp.nortel.com> <B1C1C7EE297828A38C9943D3@[172.22.20.167]>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "John C Klensin" <klensin@jck.com>, "Ed Juskevicius" <edj@nortel.com>, "Steve Crocker" <steve@shinkuro.com>, "Marshall Eubanks" <tme@multicasttech.com>
X-OriginalArrivalTime: 23 May 2008 14:49:04.0419 (UTC) FILETIME=[25495F30:01C8BCE4]
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: multipart/mixed; boundary="===============2044777122=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Some points:

1) If the objective is to have a URN for RFCs this has already been done:

RFC 2648: http://www.ietf.org/rfc/rfc2648.txt "A URN Namespace for IETF Documents"

These identifiers must be the canonical identifiers for the RFC series. But they need not be the only identifiers.

2) Schemes which rely on paying registrars to sell people numbers are probably unsustainable in the long run unless there is a business reason to use that specific number.

This is certainly the case for IP numbers. I don't see the business reason for this particular application. Hence I don't see a value in purchasing a DOI identifier at the reported $1500/annum or for accepting one for free use. I would consider that to be an endorsement and I don't think that the IETF or ISOC should get any further into that game than it alrady has.

3) Whether the documents are paper or digital is now irrelevant. Dead tree publication technology will certainly disappear at some point. My book sells in both paper and Kindle editions. The killer application of Kindle appears to be sale of periodicals and newspapers rather than just books.

The industry has a clear business need and so they will apply ISSNs to this new field regardless of what the rules might say on the matter. 

4) ISSNs are used in the library system. They are used in the Z39.50 protocol which is the principal protocol used to support that infrastructure today. I think we should get one.

 

5) This topic is a very interesting one and thus one on which a large number of people may have an opinion. The problems raised in the ESDS BOF are very similar.

Because it is an area where many people may have an opinion it appears to me that the decisive technical breakthrough we might need in this area might well be to develop a technology that allows people to have separate opinions in this area and not attempt to impose more homogeneity than is actually required.

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf