Re: ISSN for RFC Series under Consideration

John C Klensin <john-ietf@jck.com> Thu, 22 May 2008 13:22 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 0E9A628C293; Thu, 22 May 2008 06:22:20 -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 2D05628C191 for <ietf@core3.amsl.com>; Thu, 22 May 2008 06:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 xwcCfBlT8VoW for <ietf@core3.amsl.com>; Thu, 22 May 2008 06:22:15 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 85E5128C291 for <ietf@ietf.org>; Thu, 22 May 2008 06:21:00 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1JzAj4-00010q-If; Thu, 22 May 2008 09:20:59 -0400
Date: Thu, 22 May 2008 09:20:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <mshore@cisco.com>, Ed Juskevicius <edj@nortel.com>, Randy Presuhn <randy_presuhn@mindspring.com>
Subject: Re: ISSN for RFC Series under Consideration
Message-ID: <BDF06638A493A954ED0DF9A4@[172.22.20.167]>
In-Reply-To: <C45AE963.389F6%mshore@cisco.com>
References: <C45AE963.389F6%mshore@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
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

bb

--On Thursday, 22 May, 2008 09:12 -0400 Melinda Shore
<mshore@cisco.com> wrote:

> 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,

It is my understanding (more or less third-hand and I no longer
remember the details) that we've been asked about an ISSN by
other bodies, perhaps bodies who are concerned about the exact
discrimination problem you identify.  I believe that at least
one of those bodies was an academic journal or other standards
body that was queasy about referencing RFCs by URL only.  

The problem for them is, of course, not _finding_ the RFCs but
knowing that something that they find is authoritatively part of
the IETF/ RFC-Editor RFC series.  Whether they should or not,
ISSNs are official enough to make them less anxious about that
type of question.

     john



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