IETF Logo Mail Archive

Re: ISSN for RFC Series under Consideration

Melinda Shore <mshore@cisco.com> Thu, 22 May 2008 13:14 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 4D7ED3A6AE5; Thu, 22 May 2008 06:14:05 -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 48F6D3A6AE5 for <ietf@core3.amsl.com>; Thu, 22 May 2008 06:14:03 -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 zDQYasgG8CxD for <ietf@core3.amsl.com>; Thu, 22 May 2008 06:13:57 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 1CC103A6ADE for <ietf@ietf.org>; Thu, 22 May 2008 06:13:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,524,1204520400"; d="scan'208";a="9025194"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 22 May 2008 09:14:03 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4MDE3ob016526; Thu, 22 May 2008 09:14:03 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4MDE3wQ012099; Thu, 22 May 2008 13:14:03 GMT
Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 May 2008 09:12:11 -0400
Received: from 10.86.115.77 ([10.86.115.77]) by xmb-rtp-205.amer.cisco.com ([64.102.31.59]) via Exchange Front-End Server email.cisco.com ([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; Thu, 22 May 2008 13:11:55 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 22 May 2008 09:12:03 -0400
Subject: Re: ISSN for RFC Series under Consideration
From: Melinda Shore <mshore@cisco.com>
To: John C Klensin <john-ietf@jck.com>, Ed Juskevicius <edj@nortel.com>, Randy Presuhn <randy_presuhn@mindspring.com>
Message-ID: <C45AE963.389F6%mshore@cisco.com>
Thread-Topic: ISSN for RFC Series under Consideration
Thread-Index: Aci8DW0Jq2yLeCgAEd2vvgAKleNSdA==
In-Reply-To: <05AC5FC14BC5C80D8ADB7C46@[172.22.20.167]>
Mime-version: 1.0
X-OriginalArrivalTime: 22 May 2008 13:12:11.0904 (UTC) FILETIME=[72583800:01C8BC0D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1165; t=1211462043; x=1212326043; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mshore@cisco.com; z=From:=20Melinda=20Shore=20<mshore@cisco.com> |Subject:=20Re=3A=20ISSN=20for=20RFC=20Series=20under=20Con sideration |Sender:=20 |To:=20John=20C=20Klensin=20<john-ietf@jck.com>,=20Ed=20Jus kevicius=20<edj@nortel.com>,=0A=20=20=20=20=20=20=20=20Randy =20Presuhn=20<randy_presuhn@mindspring.com>; bh=4JMhxUtmxb5L6GwGbVXlP1eDScLZxWwX99ym5aTPD/M=; b=KiEFl/0+vtNYTO0ldRvVtEYeohpbt993vj0xTuhae0PIktktNG5gKPbRQq hL1UwYQ1e4n09Mp8NFGpkHC/Uigp5gHhOD/DkD14P9YukhaLMJP0dxa/Nyga k/NtI4gm/K;
Authentication-Results: rtp-dkim-1; header.From=mshore@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: IETF Discussion <ietf@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

On 5/22/08 8:51 AM, "John C Klensin" <john-ietf@jck.com> wrote:
> Indeed, another way of looking at this question is that deciding
> to register an ISSN for the RFC series really does not preclude
> anything else (including, were we so inclined, putting DOIs on
> each RFC) and we should therefore be asking "ISSN or not ISSN"
> with all questions about other sorts of identifiers and
> cataloging being viewed as separate.

I think the cataloging question is probably central to the
question of whether or not to bother with an ISSN.  I don't
think an ISSN has any practical value other than that it
increases the likelihood that LC will catalog the series/
serial and that libraries will then start sticking it into
their electronic holdings.  Now, I'm not sure I see an
advantage to getting libraries to pick up RFCs given how
trivial it is to find them online, but that's another matter.
Another advantage is discrimination in the event that some other
serial publication is also called "Request for Comments," but
again I'm not sure that's an actual problem.  But mainly,
getting an ISSN gets the series into the library system.

Melinda

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

v2.23.0 | Report a Bug | By Email