Re: ISSN for RFC Series under Consideration

Steve Crocker <steve@shinkuro.com> Wed, 21 May 2008 19:18 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 264503A68C9; Wed, 21 May 2008 12:18:14 -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 C40433A6989; Wed, 21 May 2008 12:18:12 -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 FFLDDv5cPEn2; Wed, 21 May 2008 12:18:11 -0700 (PDT)
Received: from execdsl.com (mail.shinkuro.com [216.194.124.237]) by core3.amsl.com (Postfix) with ESMTP id C83313A68B4; Wed, 21 May 2008 12:18:11 -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 16673507; Wed, 21 May 2008 13:14:32 -0600
In-Reply-To: <p06240813c45a240358e7@[165.227.249.200]>
References: <48346149.8040603@isoc.org> <p06240813c45a240358e7@[165.227.249.200]>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <2C63EC2C-E28F-4EB0-AE86-BF80ADF28D67@shinkuro.com>
From: Steve Crocker <steve@shinkuro.com>
Subject: Re: ISSN for RFC Series under Consideration
Date: Thu, 22 May 2008 03:17:42 +0800
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.753)
Cc: IAOC <iaoc@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

Naw.  The ISSN has to be on the document itself.  As you point out,  
this isn't something to be done with Internet Drafts, so it falls  
naturally to the RFC Editor, not to the individual authors.

Steve


On May 22, 2008, at 3:14 AM, Paul Hoffman wrote:

> Mostly sounds fine, with one small glitch.
>
> At 1:52 PM -0400 5/21/08, Ray Pelletier wrote:
>> 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.
>
> The value of adding "ISSN: 12345678" to each RFC seems small,
> particularly relative to the cost of everyone having to update their
> tools and so on. Also, we would have to tell people *not* to put the
> ISSN designation in their Internet Drafts (which are not part of the
> RFC series), but then switch it on for the RFC, and so on.
>
> The cost of putting "ISSN: 12345678" on a few pages at rfc-editor.org
> and ietf.org is tiny and hopefully sufficient for the statement above.
>
> --Paul Hoffman
> _______________________________________________
> 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