Re: ISSN for RFC Series under Consideration

John Levine <johnl@iecc.com> Wed, 21 May 2008 22:50 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 B901C3A67FB; Wed, 21 May 2008 15:50:55 -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 323D23A67FB for <ietf@core3.amsl.com>; Wed, 21 May 2008 15:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.899
X-Spam-Level:
X-Spam-Status: No, score=-10.899 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, 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 taD1maJd40et for <ietf@core3.amsl.com>; Wed, 21 May 2008 15:50:53 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 965203A67E2 for <ietf@ietf.org>; Wed, 21 May 2008 15:50:52 -0700 (PDT)
Received: (qmail 83074 invoked from network); 21 May 2008 22:49:18 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 21 May 2008 22:49:18 -0000
Date: 21 May 2008 22:50:56 -0000
Message-ID: <20080521225056.55795.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: ISSN for RFC Series under Consideration
In-Reply-To: <C45A11F7.38960%mshore@cisco.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Cc: mshore@cisco.com
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

>The practical benefit I see here is getting the Library of
>Congress (and who knows?  maybe the British Library, etc.)
>to catalog the series as a series, but again I'm unclear on
>the practical benefit, since RFCs are incredibly easy to find
>*as* RFCs; that is to say, by the information by which the
>series will be cataloged and classified.

I used to publish an actual paper magazine with paid subscriptions.
(The Journal of C Language Translation, ISSN 1042-7521)

The ISSN made it much easier for my subscribers, who were mostly
libraries who used subscription agents like Ebsco, to order the
magazine, because the ISSN let them find the price and where to send
the order.  In this regard, it is similar to the ISBN that everyone
uses to order books.  But, of course, this is all irrelevant for RFCs
which are distributed online for free.

I don't see any disadvantage to getting an ISSN other than the tiny
effort to update the publishing tools to put it in a header line, but
I also don't see any benefit.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Information Superhighwayman wanna-be, http://www.johnlevine.com, ex-Mayor
"More Wiener schnitzel, please", said Tom, revealingly.
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf