RE: ISSN for RFC Series under Consideration

"Glen Zorn" <glenzorn@comcast.net> Thu, 29 May 2008 02:36 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 4D9773A6CFD; Wed, 28 May 2008 19:36:40 -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 ABD5D3A68E8 for <ietf@core3.amsl.com>; Wed, 28 May 2008 19:36:38 -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=[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 dFEDXs-S-Nnd for <ietf@core3.amsl.com>; Wed, 28 May 2008 19:36:37 -0700 (PDT)
Received: from QMTA03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by core3.amsl.com (Postfix) with ESMTP id 98B9C3A6CE5 for <ietf@ietf.org>; Wed, 28 May 2008 19:36:37 -0700 (PDT)
Received: from OMTA03.westchester.pa.mail.comcast.net ([76.96.62.27]) by QMTA03.westchester.pa.mail.comcast.net with comcast id XBqV1Z0040bG4ec530BY00; Thu, 29 May 2008 02:36:03 +0000
Received: from gwzPC ([124.120.220.106]) by OMTA03.westchester.pa.mail.comcast.net with comcast id XEaj1Z00G2JL9M03P00000; Thu, 29 May 2008 02:36:41 +0000
X-Authority-Analysis: v=1.0 c=1 a=dMZebQ6EAAAA:8 a=48vgC7mUAAAA:8 a=yrusXkzAbj15BFeYbK8A:9 a=KpyBj7YPQ4WyYbXlqUcA:7 a=U0wHPqihszrNzwHy_Fy_CL5UZJcA:4 a=7Zfzu0Ws3woA:10 a=lZB815dzVvQA:10 a=QJAqVYndk0IA:10
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Ray Pelletier'" <rpelletier@isoc.org>
References: <48346149.8040603@isoc.org>
In-Reply-To: <48346149.8040603@isoc.org>
Subject: RE: ISSN for RFC Series under Consideration
Date: Thu, 29 May 2008 09:34:18 +0700
Message-ID: <000d01c8c134$9ee61c80$dcb25580$@net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Aci7a0q/SHvj74NTRnuEdTOEuIbV/AFyG9MQ
Content-Language: en-us
Cc: 'Working Group Chairs' <wgchairs@ietf.org>, 'IAB' <iab@ietf.org>, 'IETF Discussion' <ietf@ietf.org>, 'IAOC' <iaoc@ietf.org>, 'The IESG' <iesg@ietf.org>, 'RFC Editor' <rfc-editor@rfc-editor.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

Ray Pelletier <rpelletier@isoc.org> writes:

> The IETF Trust is considering applying to the U.S. Library of Congress
> to obtain an International Standard Serial Number (ISSN) for the RFC
> Series and would like community input to inform its decision.  The
> Trust
> may take up this matter on June 11th.

This idea doesn't seem harmful, at least, but I question the utility of
making references to the RFC series "compact and globally unique" or making
such references easier to construct.  I suppose that someone somewhere has
referenced the entire RFC series (as opposed to a small set of RFCs) but
I've never actually seen it...

> 
> An ISSN is applied to serials - print or non-print publications issued
> in parts.  A serial is  expected to continue indefinitely. Serials
> include magazines, newspapers, annuals, journals, proceedings,
> transactions of societies, and monographic series. Other SDOs, such as
> the IEEE, have obtained ISSNs for their publications.  A single ISSN
> uniquely identifies a title regardless of language or country in which
> published, without the burden of a complex bibliographic description.
> The ISSN itself has no significance other than the unique
> identification
> of a serial.
> 
> The Trust believes there are advantages to indentifying the RFC Series
> with an ISSN.  Among them,
> 1. Make reference to the series compact and globally unique;
> 2. Make the series, and individual RFCs, easier to reference in some
> contexts;
> 3. Results in accurate citing of serials by scholars, researchers,
> abstracters, and librarians;
> 4. ISSN registrations are maintained in an international data base and
> are made available in the ISSN Register online
> 
> According to the Library of Congress, www.loc.gov/issn/, for serials
> available only in online versions, the ISSN should appear on the title
> screen or home page and/or in the masthead or other areas where
> information about publisher, frequency, subscribing, copyright, etc. is
> given.
> 
> There is no cost associated with obtaining ISSNs.
> 
> Ray Pelletier
> IAD
> Trustee
> 
> _______________________________________________
> 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