![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
> > >Here is a concrete suggestion. > >We (for some definition of we) have the Internet Journal, which is >paper. >Publish a "Supplement of the Internet Journal," in paper, or on line, >which is > >- physically published 3 times a year >- has all of the RFC's published since then The average RFC is 30 pages, and the average publication rate is O(30) per month. That seems to work out to 3600 pages to be published with each Internet Journal. Bob Braden >- includes the level 1 RFC errata as available >- includes other notes like RFC's that have been made obsolete, etc. >- charge it to cover costs at least (say, $ 500 / year for a >subscription). > >This would be picked up by at least some libraries, and would solve >the "on-line is ephemera" problem. > >Regards >Marshall > > > > > >> 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 > From ietf-bounces at ietf.org Thu May 22 10:08:56 2008 Return-Path: <ietf-bounces at ietf.org> X-Original-To: ietf-archive at megatron.ietf.org Delivered-To: ietfarch-ietf-archive at core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8230F3A6B0F; Thu, 22 May 2008 10:08:56 -0700 (PDT) X-Original-To: ietf at core3.amsl.com Delivered-To: ietf at core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C86A3A68FD for <ietf at core3.amsl.com>; Thu, 22 May 2008 10:08:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.227 X-Spam-Level: X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372, 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 ml5zR74eYGzm for <ietf at core3.amsl.com>; Thu, 22 May 2008 10:08:19 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 8198A3A68D6 for <ietf at ietf.org>; Thu, 22 May 2008 10:08:19 -0700 (PDT) Received: from ewe.isi.edu (ewe.isi.edu [128.9.160.219]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m4MH7eBI010005; Thu, 22 May 2008 10:07:43 -0700 (PDT) Message-Id: <6.1.2.0.2.20080522100543.0254d3e0 at boreas.isi.edu> X-Sender: braden at boreas.isi.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Thu, 22 May 2008 10:08:19 -0700 To: Marshall Eubanks <tme at multicasttech.com> From: Bob Braden <braden at ISI.EDU> Subject: Re: ISSN for RFC Series under Consideration In-Reply-To: <80F67881-35FF-4748-BF2B-0AB28A1C2003 at multicasttech.com> References: <C45AE963.389F6%mshore at cisco.com> <00FD433C-24C0-4007-B44E-8E073B9BC757 at shinkuro.com> <0BDFFF51DC89434FA33F8B37FCE363D511F9504F at zcarhxm2.corp.nortel.com> <B1C1C7EE297828A38C9943D3 at [172.22.20.167]> <80F67881-35FF-4748-BF2B-0AB28A1C2003 at multicasttech.com> Mime-Version: 1.0 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: braden at isi.edu Cc: IETF Discussion <ietf at ietf.org> X-BeenThere: ietf at 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 at ietf.org?subject=unsubscribe> List-Archive: <http://www.ietf.org/pipermail/ietf> List-Post: <mailto:ietf at ietf.org> List-Help: <mailto:ietf-request at ietf.org?subject=help> List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-bounces at ietf.org Errors-To: ietf-bounces at ietf.org > > >Here is a concrete suggestion. > >We (for some definition of we) have the Internet Journal, which is >paper. >Publish a "Supplement of the Internet Journal," in paper, or on line, >which is > >- physically published 3 times a year >- has all of the RFC's published since then The average RFC is 30 pages, and the average publication rate is O(30) per month. That seems to work out to 3600 pages to be published with each Internet Journal. Bob Braden >- includes the level 1 RFC errata as available >- includes other notes like RFC's that have been made obsolete, etc. >- charge it to cover costs at least (say, $ 500 / year for a >subscription). > >This would be picked up by at least some libraries, and would solve >the "on-line is ephemera" problem. > >Regards >Marshall > > > > > >> 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 > >> desir>> desirable objective. > > > > Indeed. And libraries, especially the subset of libraries that > > have national archival responsibilities, do pay attention to > > these identifiers. > > > > john > > > >_______________________________________________ >IETF mailing list >IETF at ietf.org >https://www.ietf.org/mailman/listinfo/ietf _______________________________________________ IETF mailing list IETF at ietf.org https://www.ietf.org/mailman/listinfo/ietf able objective. > > > > Indeed. And libraries, especially the subset of libraries that > > have national archival responsibilities, do pay attention to > > these identifiers. > > > > john > > > >_______________________________________________ >IETF mailing list >IETF at ietf.org >https://www.ietf.org/mailman/listinfo/ietf _______________________________________________ IETF mailing list IETF at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.