Re: ISSN for RFC Series under Consideration

Steve Crocker <steve@shinkuro.com> Thu, 22 May 2008 13:20 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 CAC9228C286; Thu, 22 May 2008 06:20:33 -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 496BA28C191 for <ietf@core3.amsl.com>; Thu, 22 May 2008 06:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.47
X-Spam-Level:
X-Spam-Status: No, score=-1.47 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129]
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 gztNJSEclVG9 for <ietf@core3.amsl.com>; Thu, 22 May 2008 06:20:31 -0700 (PDT)
Received: from execdsl.com (mail.shinkuro.com [216.194.124.237]) by core3.amsl.com (Postfix) with ESMTP id 7275028C145 for <ietf@ietf.org>; Thu, 22 May 2008 06:20:31 -0700 (PDT)
Received: from [122.152.144.88] (HELO [172.16.17.65]) by execdsl.com (CommuniGate Pro SMTP 4.2.7) with ESMTP id 16676004; Thu, 22 May 2008 07:16:53 -0600
In-Reply-To: <C45AE963.389F6%mshore@cisco.com>
References: <C45AE963.389F6%mshore@cisco.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <00FD433C-24C0-4007-B44E-8E073B9BC757@shinkuro.com>
From: Steve Crocker <steve@shinkuro.com>
Subject: Re: ISSN for RFC Series under Consideration
Date: Thu, 22 May 2008 09:20:33 -0400
To: Melinda Shore <mshore@cisco.com>
X-Mailer: Apple Mail (2.753)
Cc: John C Klensin <john-ietf@jck.com>, Steve Crocker <steve@shinkuro.com>, 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

Every so often someone suggests RFCs are not first class documents  
and hence not comparable to, say, "real" standards documents.   
Getting traditional identifiers attached to them might squelch some  
of this nonsense.

Steve

On May 22, 2008, at 9:12 AM, Melinda Shore wrote:

> On 5/22/08 8:51 AM, "John C Klensin" <john-ietf@jck.com> wrote:
>> 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.
>
> I think the cataloging question is probably central to the
> question of whether or not to bother with an ISSN.  I don't
> think an ISSN has any practical value other than that it
> increases the likelihood that LC will catalog the series/
> serial and that libraries will then start sticking it into
> their electronic holdings.  Now, I'm not sure I see an
> advantage to getting libraries to pick up RFCs given how
> trivial it is to find them online, but that's another matter.
> Another advantage is discrimination in the event that some other
> serial publication is also called "Request for Comments," but
> again I'm not sure that's an actual problem.  But mainly,
> getting an ISSN gets the series into the library system.
>
> Melinda
>
> _______________________________________________
> IETF mailing list
> IETF@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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