ISSN for RFC Series under Consideration

Ray Pelletier <rpelletier@isoc.org> Wed, 21 May 2008 17:51 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 890AE3A6A4F; Wed, 21 May 2008 10:51:12 -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 3095F28C103 for <ietf@core3.amsl.com>; Wed, 21 May 2008 10:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.865
X-Spam-Level:
X-Spam-Status: No, score=-100.865 tagged_above=-999 required=5 tests=[AWL=-0.866, BAYES_50=0.001, USER_IN_WHITELIST=-100]
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 7cmF1siH2MtQ for <ietf@core3.amsl.com>; Wed, 21 May 2008 10:51:11 -0700 (PDT)
Received: from smtp137.iad.emailsrvr.com (smtp137.iad.emailsrvr.com [207.97.245.137]) by core3.amsl.com (Postfix) with ESMTP id 2D4663A6966 for <ietf@ietf.org>; Wed, 21 May 2008 10:51:11 -0700 (PDT)
Received: from relay3.r3.iad.emailsrvr.com (localhost [127.0.0.1]) by relay3.r3.iad.emailsrvr.com (SMTP Server) with ESMTP id D5D5544C25E; Wed, 21 May 2008 13:51:14 -0400 (EDT)
Received: by relay3.r3.iad.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTP id A57F444C257; Wed, 21 May 2008 13:51:14 -0400 (EDT)
Message-ID: <48346149.8040603@isoc.org>
Date: Wed, 21 May 2008 13:52:09 -0400
From: Ray Pelletier <rpelletier@isoc.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, zh, zh-cn, zh-hk, zh-sg, zh-tw, ja
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>, IAOC <iaoc@ietf.org>, The IESG <iesg@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>, IAB <iab@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
Subject: ISSN for RFC Series under Consideration
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

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.  

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