Re: ISSN for RFC Series under Consideration

"Tom.Petch" <> Thu, 22 May 2008 10:10 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id AAD963A6AF6; Thu, 22 May 2008 03:10:39 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id EC2453A6AB4; Thu, 22 May 2008 03:10:10 -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 y9nf4zLzoZ55; Thu, 22 May 2008 03:09:59 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D46A33A6AE5; Thu, 22 May 2008 03:09:58 -0700 (PDT)
X-Trace: 84428085/$ACCEPTED/pipex-customers/
X-SBRS: None
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuIEAK7iNEg+vI4V/2dsb2JhbACLX6N0Aw
X-IronPort-AV: E=Sophos;i="4.27,524,1204502400"; d="scan'208";a="84428085"
X-IP-Direction: IN
Received: from (HELO allison) ([]) by with SMTP; 22 May 2008 11:09:57 +0100
Message-ID: <014301c8bbea$f9243460$0601a8c0@allison>
From: "Tom.Petch" <>
To: "Ray Pelletier" <>, "IETF Discussion" <>, "IAOC" <>, "The IESG" <>, "RFC Editor" <>, "IAB" <>, "Working Group Chairs" <>
References: <>
Subject: Re: ISSN for RFC Series under Consideration
Date: Thu, 22 May 2008 09:39:07 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "Tom.Petch" <>
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

Yes, I think that this is an excellent idea and should be pursued.

I note that this will also give us a URN (RFC3044).  Any thoughts on what the
URN might in future resolve to?

Tom Petch

----- Original Message -----
From: "Ray Pelletier" <>
To: "IETF Discussion" <>rg>; "IAOC" <>rg>; "The IESG"
<>rg>; "RFC Editor" <>rg>; "IAB" <>rg>;
"Working Group Chairs" <>
Sent: Wednesday, May 21, 2008 7:52 PM
Subject: ISSN for RFC Series under Consideration

> 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,, 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
> Trustee
> _______________________________________________
> IETF mailing list

IETF mailing list