Re: ISSN for RFC Series under Consideration

John C Klensin <> Thu, 22 May 2008 15:32 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id 2E72F28C29A; Thu, 22 May 2008 08:32:49 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2A15B3A6A77 for <>; Thu, 22 May 2008 05:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id c3qbqsmcrKLz for <>; Thu, 22 May 2008 05:49:38 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 287C43A684C for <>; Thu, 22 May 2008 05:49:38 -0700 (PDT)
Received: from [] (helo=localhost) by with esmtp (Exim 4.34) id 1JzAEm-000PyH-JS; Thu, 22 May 2008 08:49:41 -0400
Date: Thu, 22 May 2008 08:49:37 -0400
From: John C Klensin <>
To: Melinda Shore <>, Ed Juskevicius <>, Randy Presuhn <>
Subject: Re: ISSN for RFC Series under Consideration
Message-ID: <4A0F036479661726D92A0F14@[]>
In-Reply-To: <>
References: <>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
X-Mailman-Approved-At: Thu, 22 May 2008 08:32:46 -0700
Cc: IETF Discussion <>
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


--On Thursday, 22 May, 2008 07:18 -0400 Melinda Shore
<> wrote:

> On 5/22/08 2:01 AM, "Ed Juskevicius" <> wrote:
>> I believe that getting each RFC cataloged individually would
>> not be possible using an ISSN, so we would need to employ
>> ISBNs.
> No, not necessarily.  A serial published as a serial
> ("The Bulletin of the Singapore Guppy Society") is cataloged
> as such, while a monograph series that has an ISSN may have the
> monographs cataloged individually (this is under the Anglo-
> American Cataloging Rules rev 2, and there may be some national
> variations).  
> Getting an ISSN in no way prevents individual RFCs from being
> cataloged individually.

Of course not.  It doesn't even prevent individual RFCs, or
clusters of RFCs, being assigned ISBNs or, if one feels like
setting them to music or performing them in public and releasing
audio or video of those forms ISMNs or ISANs (the assorted
acronyms are left as an exercise for the reader).

Indeed, another way of looking at this question is that deciding
to register an ISSN for the RFC series really does not preclude
anything else (including, were we so inclined, putting DOIs on
each RFC) and we should therefore be asking "ISSN or not ISSN"
with all questions about other sorts of identifiers and
cataloging being viewed as separate.   Stated that way, I think
the answer to the ISSN question is pretty close to "some
advantages, very low cost, no possible reason why not"


IETF mailing list