RE: ISSN for RFC Series under Consideration

"Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com> Wed, 21 May 2008 19:49 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 48DE33A6B76; Wed, 21 May 2008 12:49:23 -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 6143C3A6B2B; Wed, 21 May 2008 12:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 25SM0fjuIWv4; Wed, 21 May 2008 12:49:20 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.245.51]) by core3.amsl.com (Postfix) with SMTP id 450C928C257; Wed, 21 May 2008 12:49:20 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: Donald.Eastlake@motorola.com
X-Msg-Ref: server-13.tower-119.messagelabs.com!1211399363!31967796!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.189.100.102]
Received: (qmail 17053 invoked from network); 21 May 2008 19:49:23 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102) by server-13.tower-119.messagelabs.com with SMTP; 21 May 2008 19:49:23 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate4.mot.com (8.12.11/Motorola) with ESMTP id m4LJnNlY015717; Wed, 21 May 2008 12:49:23 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id m4LJnMB4028781; Wed, 21 May 2008 14:49:22 -0500 (CDT)
Received: from de01exm64.ds.mot.com (de01exm64.am.mot.com [10.176.8.15]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id m4LJnL9L028766; Wed, 21 May 2008 14:49:21 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: ISSN for RFC Series under Consideration
Date: Wed, 21 May 2008 15:49:19 -0400
Message-ID: <3870C46029D1F945B1472F170D2D979003D0FCEE@de01exm64.ds.mot.com>
In-Reply-To: <2C63EC2C-E28F-4EB0-AE86-BF80ADF28D67@shinkuro.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: ISSN for RFC Series under Consideration
thread-index: Aci7d3zAZCdkDesZSVi50iTYQ1cOkgAAnBiA
References: <48346149.8040603@isoc.org><p06240813c45a240358e7@[165.227.249.200]> <2C63EC2C-E28F-4EB0-AE86-BF80ADF28D67@shinkuro.com>
From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
To: "IETF Discussion" <ietf@ietf.org>
X-CFilter-Loop: Reflected
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

Yes, this seems like a good idea and I don't see why anyone would have
to do any work other than the RFC Editor. Are the tools we use really so
brittle that adding a line with "ISSN xxxx-xxxx" or "urn:ISSN:xxxx-xxxx"
or whatever somewhere in the upper left corner of the first page of an
RFC will break them?

Donald

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Steve Crocker
Sent: Wednesday, May 21, 2008 3:18 PM
To: IETF Discussion
Cc: IAOC
Subject: Re: ISSN for RFC Series under Consideration

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
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf