IETF Logo Mail Archive

Re: ISSN for RFC Series under Consideration

Melinda Shore <mshore@cisco.com> Thu, 22 May 2008 11:21 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 71EB73A6925; Thu, 22 May 2008 04:21:26 -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 919B93A6916 for <ietf@core3.amsl.com>; Thu, 22 May 2008 04:21:24 -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=[AWL=0.000, 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 MJ8aIMj0I1yt for <ietf@core3.amsl.com>; Thu, 22 May 2008 04:21:23 -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 5DC2E3A681D for <ietf@ietf.org>; Thu, 22 May 2008 04:21:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,524,1204520400"; d="scan'208";a="9017407"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 22 May 2008 07:21:27 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4MBLRGM019790; Thu, 22 May 2008 07:21:27 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4MBLRsM017718; Thu, 22 May 2008 11:21:27 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 07:21:27 -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 11:18:22 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 22 May 2008 07:18:30 -0400
Subject: Re: ISSN for RFC Series under Consideration
From: Melinda Shore <mshore@cisco.com>
To: Ed Juskevicius <edj@nortel.com>, Randy Presuhn <randy_presuhn@mindspring.com>
Message-ID: <C45ACEC6.389E5%mshore@cisco.com>
Thread-Topic: ISSN for RFC Series under Consideration
Thread-Index: Aci7b1B39F3ycm+eRKSKrSe0hizK3AAX5HTAAAurebU=
In-Reply-To: <0BDFFF51DC89434FA33F8B37FCE363D511F9504C@zcarhxm2.corp.nortel.com>
Mime-version: 1.0
X-OriginalArrivalTime: 22 May 2008 11:21:27.0573 (UTC) FILETIME=[FA03C450:01C8BBFD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=620; t=1211455287; x=1212319287; c=relaxed/simple; s=rtpdkim2001; 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:=20Ed=20Juskevicius=20<edj@nortel.com>,=0A=20=20=20=20= 20=20=20=20Randy=20Presuhn=20<randy_presuhn@mindspring.com>; bh=7yGFhyjMhREiDdxcjL8e/u0arrWqF0Ngu8sV+SI2yb0=; b=KgQuWdKiCdKqhw5YyUNgaHTfFhTNTIDfvRbFf78InwLJYB/0oTjwRmHpfs fvrIGlDr2bUtSPh+IkZtNteYzPaD502b464qH8Z0sZW22b5iKJjHgsaE/8gL aubkZDQX2S;
Authentication-Results: rtp-dkim-2; header.From=mshore@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 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 2:01 AM, "Ed Juskevicius" <edj@nortel.com> wrote:
> I believe that getting each RFC cataloged individually would not
> be possible using an ISSN, so we would need to employ ISBNs.

No, not necessarily.  A serial published as a serial
("The Bulletin of the Singapore Guppy Society") is cataloged
as such, while a monograph series that has an ISSN may have the
monographs cataloged individually (this is under the Anglo-
American Cataloging Rules rev 2, and there may be some national
variations).  

Getting an ISSN in no way prevents individual RFCs from being
cataloged individually.

Melinda

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

v2.23.0 | Report a Bug | By Email