Re: ISSN for RFC Series under Consideration

Eric Rescorla <ekr@networkresonance.com> Wed, 21 May 2008 23:06 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 CB1FC3A6A4E; Wed, 21 May 2008 16:06: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 735E93A67FB; Wed, 21 May 2008 16:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.388
X-Spam-Level:
X-Spam-Status: No, score=0.388 tagged_above=-999 required=5 tests=[AWL=2.987, 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 Ff04LSVobrIB; Wed, 21 May 2008 16:06:09 -0700 (PDT)
Received: from romeo.rtfm.com (romeo.rtfm.com [74.95.2.173]) by core3.amsl.com (Postfix) with ESMTP id 3CB653A6966; Wed, 21 May 2008 16:06:09 -0700 (PDT)
Received: from romeo.rtfm.com (localhost.rtfm.com [127.0.0.1]) by romeo.rtfm.com (Postfix) with ESMTP id EB8C85081A; Wed, 21 May 2008 16:09:51 -0700 (PDT)
Date: Wed, 21 May 2008 16:09:51 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: Melinda Shore <mshore@cisco.com>
Subject: Re: ISSN for RFC Series under Consideration
In-Reply-To: <C45A11F7.38960%mshore@cisco.com>
References: <48349682.6040803@gmail.com> <C45A11F7.38960%mshore@cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Message-Id: <20080521230951.EB8C85081A@romeo.rtfm.com>
Cc: Working Group Chairs <wgchairs@ietf.org>, IAB <iab@ietf.org>, IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, IAOC <iaoc@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

At Wed, 21 May 2008 17:52:55 -0400,
Melinda Shore wrote:
> 
> On 5/21/08 5:39 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote:
> > Possibly not, but there is still a crusty old world of academic
> > publications with traditional reference styles out there, and an ISSN
> > will make it much more straightforward to cite RFCs in peer-reviewed
> > publications. +1 that it's a no-brainer.
> 
> Hi - I'm really not trying to be a contrarian, just trying to
> sort through the actual issues here.  I don't think I've ever seen
> a reference that included an ISSN.  I've also never seen one
> used as a subject header (index term) in cataloging.  The only
> time I've personally seen them used is as *descriptive* information
> in a  catalog (library catalog, publisher's catalog, etc.).  I'm
> sure someone will be happy to dig up a counterexample but
> I do think they're pretty unusual.  Really, what are the odds
> that someone knows the ISSN but not the title or the author or
> the publisher or ... ?

I agree with Melinda here. I can't remember ever seeing anything
like an ISBN or an ISSN used as a citation in an academic paper.

-Ekr
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf