Re: ISSN for RFC Series under Consideration

Nevil Brownlee <> Thu, 22 May 2008 15:32 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id 99F8B28C1BA; Thu, 22 May 2008 08:32:47 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 86DE83A68FA; Wed, 21 May 2008 15:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XVVPh-FvuQtx; Wed, 21 May 2008 15:16:40 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 77FF43A67EC; Wed, 21 May 2008 15:16:39 -0700 (PDT)
Received: from localhost (localhost.localdomain []) by (Postfix) with ESMTP id 76B6A18901; Thu, 22 May 2008 10:16:43 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xoFF06BHUIv5; Thu, 22 May 2008 10:16:43 +1200 (NZST)
Received: from [] ( []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTP id 252DF188FD; Thu, 22 May 2008 10:16:43 +1200 (NZST)
In-Reply-To: <>
References: <>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <>
From: Nevil Brownlee <>
Subject: Re: ISSN for RFC Series under Consideration
Date: Thu, 22 May 2008 10:16:42 +1200
To: Melinda Shore <>
X-Mailer: Apple Mail (2.753)
X-Mailman-Approved-At: Thu, 22 May 2008 08:32:46 -0700
Cc: Working Group Chairs <>, IAB <>, IETF Discussion <>, Julian Reschke <>, IAOC <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all:

In a former life I published a Theatre Technology newsletter; we got an
ISSN for it, as a result two libraries asked for copies of each issue so
that they could archive them.  That was the only effect.

So, I agree with Melinda - it's worth getting an ISSN, and recognition
from the Library world, but it's unlikely to have any other effect.

Cheers, Nevil

  Nevil Brownlee                    Computer Science Department | ITS
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand

On 22/05/2008, at 9:52 AM, Melinda Shore wrote:

> On 5/21/08 5:39 PM, "Brian E Carpenter"  
> <> wrote:
>> Possibly not, but there is still a crusty old world of academic
>> publications with traditional reference styles out there, and an ISSN
>> will make it much more straightforward to cite RFCs in peer-reviewed
>> publications. +1 that it's a no-brainer.
> Hi - I'm really not trying to be a contrarian, just trying to
> sort through the actual issues here.  I don't think I've ever seen
> a reference that included an ISSN.  I've also never seen one
> used as a subject header (index term) in cataloging.  The only
> time I've personally seen them used is as *descriptive* information
> in a  catalog (library catalog, publisher's catalog, etc.).  I'm
> sure someone will be happy to dig up a counterexample but
> I do think they're pretty unusual.  Really, what are the odds
> that someone knows the ISSN but not the title or the author or
> the publisher or ... ?
> 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 don't see any disadvantage to doing it, it's just that I
> can't see much advantage, either.  I figure we should just
> go ahead and do it and not have any expectations that the
> RFCs will be any more accessible, any more searchable, etc.
> More like a change in status than a change in substance.
> Melinda
IETF mailing list