RE: ISSN for RFC Series under Consideration

"Ed Juskevicius" <edj@nortel.com> Thu, 22 May 2008 06:01 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 AD17C3A6A50; Wed, 21 May 2008 23:01:17 -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 668503A6B9E for <ietf@core3.amsl.com>; Wed, 21 May 2008 23:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 rW5gEqe1em+2 for <ietf@core3.amsl.com>; Wed, 21 May 2008 23:01:14 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id A8C613A6AAC for <ietf@ietf.org>; Wed, 21 May 2008 23:01:13 -0700 (PDT)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id m4M606j22257; Thu, 22 May 2008 06:00:06 GMT
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: Thu, 22 May 2008 02:01:15 -0400
Message-ID: <0BDFFF51DC89434FA33F8B37FCE363D511F9504C@zcarhxm2.corp.nortel.com>
In-Reply-To: <002801c8bb6f$331160c0$6801a8c0@oemcomputer>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: ISSN for RFC Series under Consideration
Thread-Index: Aci7b1B39F3ycm+eRKSKrSe0hizK3AAX5HTA
References: <C459DF4E.388EC%mshore@cisco.com> <002801c8bb6f$331160c0$6801a8c0@oemcomputer>
From: "Ed Juskevicius" <edj@nortel.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi -

> What would it take to get them cataloged individually?
>
> Randy

I believe that getting each RFC cataloged individually would not
be possible using an ISSN, so we would need to employ ISBNs.

My understanding of ISBNs is as follows:

In the US, the ISBN Agency is Bowker
http://www.bowker.com/index.php/index.php/component/content/article/1/2.

 
Their faq
http://www.bowker.com/index.php/supportfaq-isbn/49-support-isbn/350-faqs
-isbn-general
defines the products eligible for an ISBN and standards do
fit in the definition.  This faq also discusses the purpose
and why/when an ISBN should be used.
 
To apply ISBNs to RFC, the process would need to be something like:

- obtain a block of ISBN numbers (e.g. 1,000 of them)
- note that a block of 1,000 is $1570 per
  https://commerce.bowker.com/standards/cgi-bin/isbn.asp 
- then assign an ISBN number to each RFC before it publication,
  and register each not-yet-published RFC against the ISBN per
 
http://www.bowker.com/index.php/supportfaq-isbn/49-support-isbn/381-faqs
-isbn-howtouse  

Setting this up take work and a modest on-going budget. Once in place,
the ongoing effort would be less.  That being said, ISBN numbers are not
free, so I think we'd need to identify some tangible benefits to really
doing this, before deciding to proceed.


Regards,

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