Re: ISSN for RFC Series under Consideration

Melinda Shore <> Wed, 21 May 2008 18:32 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id 9B0B73A6B76; Wed, 21 May 2008 11:32:08 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 515AB3A6B76 for <>; Wed, 21 May 2008 11:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WqLPvOH4Dqbe for <>; Wed, 21 May 2008 11:32:03 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 25C573A6AFB for <>; Wed, 21 May 2008 11:32:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,522,1204520400"; d="scan'208";a="8897206"
Received: from ([]) by with ESMTP; 21 May 2008 14:32:06 -0400
Received: from ( []) by (8.12.11/8.12.11) with ESMTP id m4LIW6Iv014736; Wed, 21 May 2008 14:32:06 -0400
Received: from ( []) by (8.13.8/8.13.8) with ESMTP id m4LIW65N005846; Wed, 21 May 2008 18:32:06 GMT
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 May 2008 14:31:40 -0400
Received: from ([]) by ([]) via Exchange Front-End Server ([]) with Microsoft Exchange Server HTTP-DAV ; Wed, 21 May 2008 18:31:40 +0000
User-Agent: Microsoft-Entourage/
Date: Wed, 21 May 2008 14:31:47 -0400
Subject: Re: ISSN for RFC Series under Consideration
From: Melinda Shore <>
To: Randy Presuhn <>, IETF Discussion <>
Message-ID: <>
Thread-Topic: ISSN for RFC Series under Consideration
Thread-Index: Aci7cO0tK6ahzCdkEd2vvgAKleNSdA==
In-Reply-To: <002801c8bb6f$331160c0$6801a8c0@oemcomputer>
Mime-version: 1.0
X-OriginalArrivalTime: 21 May 2008 18:31:40.0703 (UTC) FILETIME=[E96D12F0:01C8BB70]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1293; t=1211394727; x=1212258727; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;;; z=From:=20Melinda=20Shore=20<> |Subject:=20Re=3A=20ISSN=20for=20RFC=20Series=20under=20Con sideration |Sender:=20 |To:=20Randy=20Presuhn=20<>,=0A =20=20=20=20=20=20=20=20IETF=20Discussion=20<>; bh=DQV1RioqRLPD+1uncqjDi3daW66olw9183A5dJy0Z0o=; b=qiOLSP1HuIfFpcw4pHxryp5oSQ0ruSDlDQE37drnXLunbQyfvls1vUKl6h rdcYhAto+WBUusDZofXAFdi8kB0B6uuTAB7vrjvKvGPUjf3+rgZfViRQ8eTR pjJxTWhfZF;
Authentication-Results: rtp-dkim-2;; dkim=pass ( sig from verified; );
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On 5/21/08 2:19 PM, "Randy Presuhn" <> wrote:
> What would it take to get them cataloged individually?

Interest in having them cataloged individually.  I believe LC
catalogs everything it receives.  I've been out of librarianship
long enough not to know how they receive electronic-only material.

There are a couple of RFCs in the OCLC database but not a lot,
and they seem to under the subject heading "Computer networks--
standards".  Cataloging helps solve the problem of finding the
document.  Subject headers and classification help solve the
problem of finding the information in the document.  As university
libraries are apparently currently classifying RFCs the subject
classification is so broad as to be useless and I would guess
that there's not currently a problem with locating the documents
(for reasonable people, anyway).  I think the answer to the
question of how easy it is to locate the *information* in the
documents (i.e. information retrieval) is a lot less clear
but I'm not sure the necessarily broad categories in the
LC subject classifications would help with that problem at all
(in fact, I'm pretty sure it wouldn't).

But more information is usually better than less information,
so what the heck.


IETF mailing list