RE: ISSN for RFC Series under Consideration

"Ed Juskevicius" <edj@nortel.com> Thu, 22 May 2008 14:15 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 953D528C18E; Thu, 22 May 2008 07:15:38 -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 7C66F3A67A2 for <ietf@core3.amsl.com>; Thu, 22 May 2008 07:15:35 -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 N1a-9nFzYtke for <ietf@core3.amsl.com>; Thu, 22 May 2008 07:15:33 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55]) by core3.amsl.com (Postfix) with ESMTP id 0A80528C27D for <ietf@ietf.org>; Thu, 22 May 2008 07:15:32 -0700 (PDT)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id m4MEFWm12308; Thu, 22 May 2008 14:15:33 GMT
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: Thu, 22 May 2008 10:15:09 -0400
Message-ID: <0BDFFF51DC89434FA33F8B37FCE363D511F9504F@zcarhxm2.corp.nortel.com>
In-Reply-To: <00FD433C-24C0-4007-B44E-8E073B9BC757@shinkuro.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: ISSN for RFC Series under Consideration
Thread-Index: Aci8DqQUJuxUBt1kRWOPfyCOSj13vgABYH8Q
References: <C45AE963.389F6%mshore@cisco.com> <00FD433C-24C0-4007-B44E-8E073B9BC757@shinkuro.com>
From: "Ed Juskevicius" <edj@nortel.com>
To: "Steve Crocker" <steve@shinkuro.com>, "Marshall Eubanks" <tme@multicasttech.com>
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

Steve:

> Every so often someone suggests RFCs are not first class
> documents and hence not comparable to, say, "real"
> standards documents. Getting traditional identifiers attached
> to them might squelch some of this nonsense.

I have the impression that we would be pioneering the use of an ISSN to
identify a standards' series, if we choose to do this.  The "real"
standards from other organizations seem to be identified with individual
ISBNs.

Would the purveyors of nonsense be squelched by an ISSN, or emboldened?
Some might cite our decision as yet another example of the IETF doing
something different and 'non-standard'.

Marshall, to your point:

> It is easy to find RFC's now, but it may not be in a century.
>
> This may seem silly, but I think that RFCs will still
> have relevance in a century and, having experience
> searching for 100+ year old astronomical publications
> and data, in my opinion, RFC's need to be cataloged in
> libraries.
>
> Libraries have running code for the maintenance of
> intellectual property over centuries; the IETF does not.

I agree with you 100%.  I think this is indeed a tangible and desirable
objective.

Best Regards,

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