Re: [rfc-i] Paper as an archival format for RFCs
Craig Partridge <craig@tereschau.net> Thu, 16 February 2017 22:49 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5385C129632 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 16 Feb 2017 14:49:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.091
X-Spam-Level:
X-Spam-Status: No, score=-4.091 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" header.d=tereschau.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3fRPkiah0o_y for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 16 Feb 2017 14:49:48 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEAC3124281 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 16 Feb 2017 14:49:48 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 81112B80FFB; Thu, 16 Feb 2017 14:49:48 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 8ACEEB80FFB for <rfc-interest@rfc-editor.org>; Thu, 16 Feb 2017 14:49:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tereschau.net
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1fPLNYL6P8m for <rfc-interest@rfc-editor.org>; Thu, 16 Feb 2017 14:49:42 -0800 (PST)
Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) by rfc-editor.org (Postfix) with ESMTPS id 83A39B80FFA for <rfc-interest@rfc-editor.org>; Thu, 16 Feb 2017 14:49:42 -0800 (PST)
Received: by mail-ot0-x232.google.com with SMTP id t47so21335708ota.1 for <rfc-interest@rfc-editor.org>; Thu, 16 Feb 2017 14:49:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tereschau.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8bLunWFXD73YqjfXFwes3bN6AayJeR/UD9LRdQrjCkQ=; b=dRjFeyoid/ihytjEif4/KiCZnjcNInvXoR5FmsE6GO+katHvuM69ACw4PrU/IbWgHW Oab2AxXT6gKZrfyHL6yWeex8LoEnuBem/8nT9AkYOcej/2E0eBQb1uNBxZ8FrLmBwl9C 1N+BLKGCxMAgnbtqKkeffnbtwBih9Yit5F9MMzxI4AbOH5pUYA1yvCqklayyD54BElio V3ErzcJd9Ab9RXx+7UtrITx04PYEQx/GEt6pZ5kSxsD4WlNN0flE6Mv019e8c79uehfY fNFINxzguDbxzwfNGF6jrwLtg8xU7y1l2Ren/6N24C0QtVqDWr8cAoow2yM2wFS3tyyY WmZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8bLunWFXD73YqjfXFwes3bN6AayJeR/UD9LRdQrjCkQ=; b=UqW42wtYRPP1/zeKjZdquh3UYZea0cfLhQ8FILPo7XNINkt9AXmV1iYCEUQlIsRi++ oxQh04ZpeVQVep3QcY6/yqjAiL+PKD8xKN9ny3QmlLo67k6TiSQC88t4N8DB8CGMoLQb 6Q3Bda2xspFOUCkGPHcsVx2H3gY0DHbgZCOiiXXB1Jo7bZ/+oW02royjVzGgBALWdEwo B5slCKiNu7NTzpZP0k1SQE3ZRa1t1rkmwdmMBdIz4njXtFy9flOSeXicTMF08zkqsgjj 48mvLxvBjPsJ9ptHfzg+2FH9Hj0Gik73Wq1MfuPkmxmO/QcvWBYCRCpsXuEUo7cQl0a5 MINA==
X-Gm-Message-State: AMke39k7p3QMwMr2qF1m3cqLYk54GFDkNxYXniJ1j9NYU7JMFZwEo0/cWAz8sQQfZhbUcBg3iccTI7m/RedIKWlY
X-Received: by 10.157.48.134 with SMTP id s6mr833195otc.151.1487285381563; Thu, 16 Feb 2017 14:49:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.191.39 with HTTP; Thu, 16 Feb 2017 14:49:41 -0800 (PST)
In-Reply-To: <a3e4426e-893f-01d3-6477-18a57d08fc50@isi.edu>
References: <CAHQj4CdfLdkreGx8SFXwOJP62cZHQ4t3oU8uaN44PYgrTXKqhg@mail.gmail.com> <a3e4426e-893f-01d3-6477-18a57d08fc50@isi.edu>
From: Craig Partridge <craig@tereschau.net>
Date: Thu, 16 Feb 2017 17:49:41 -0500
Message-ID: <CAHQj4CdyX6bNr4tbCmssqGx0oeZiy5QvfxH6f6p62UcSPAnHUA@mail.gmail.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: [rfc-i] Paper as an archival format for RFCs
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfc-interest@rfc-editor.org
Content-Type: multipart/mixed; boundary="===============1235741252949442640=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
Hi Joe: Keep in mind that I do communicate occasionally with professional archivists. They remain torn between the need to try to find a way to save digital artifacts and a strong sense that their solutions are likely to fail. I agree that asking a professional librarian is a fine solution. But I would ask them the question in the form: would you prefer printed copies on archival paper or digital copy? (As opposed to the -- "can you archive digital material?" -- to which they feel obliged to try to say yes, but may prefer to say no). Craig On Thu, Feb 16, 2017 at 5:41 PM, Joe Touch <touch@isi.edu> wrote: > > > On 2/16/2017 2:12 PM, Craig Partridge wrote: > > I'm with John. There are many good reasons to use paper (such as > > we've successfully used it as > > an archival technology for roughly 2000 years -- show me a digital > > system with a similar track record). > > That's going to be hard to *prove* for another 2000 years. > > I see the point about full archival technology, but I don't think we > should be second-guessing professional librarians. A box of wood pulp, > even on acid-free paper, also has the potential for being destroyed by > fire, water, bugs, etc. > > IMO, the proposed approach of offloading this issue to professional > librarians seems more than sufficient. If THEY decide that printing out > reams of pulp and boxing it up is the way to go, then they can make that > decision. I don't think we need to second guess them. > > Joe > -- ***** Craig Partridge's email account for professional society activities and mailing lists. For Raytheon business, please email: craig. <craig@bbn.com> partridge@raytheon.com
_______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Paper as an archival format for RFCs Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] Paper as an archival format for RFCs John Levine
- Re: [rfc-i] Paper as an archival format for RFCs Craig Partridge
- Re: [rfc-i] Paper as an archival format for RFCs Joe Touch
- Re: [rfc-i] Paper as an archival format for RFCs Adam Roach
- Re: [rfc-i] Paper as an archival format for RFCs Andrew Sullivan
- Re: [rfc-i] Paper as an archival format for RFCs Craig Partridge
- Re: [rfc-i] Paper as an archival format for RFCs Joe Touch
- Re: [rfc-i] Paper as an archival format for RFCs Dave Crocker