Re: [GROW] [Technical Errata Reported] RFC7948 (5366)

Nick Hilliard <nick@foobar.org> Thu, 24 May 2018 12:49 UTC

Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B82D012DA4D for <grow@ietfa.amsl.com>; Thu, 24 May 2018 05:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 lnJ_PNoU_qEb for <grow@ietfa.amsl.com>; Thu, 24 May 2018 05:49:22 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE54A126D05 for <grow@ietf.org>; Thu, 24 May 2018 05:49:21 -0700 (PDT)
X-Envelope-To: grow@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id w4OCnIL7014710 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 May 2018 13:49:19 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
To: Sandra Murphy <sandy@tislabs.com>
Cc: grow@ietf.org, Warren Kumari <warren@kumari.net>
References: <20180523170439.5C2E3B80F01@rfc-editor.org> <dea7ac10-8682-f17d-4bc3-21d38d557bca@inex.ie> <F4FC51B2-16C1-464A-B06A-AC474016A481@tislabs.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <e2e63e88-18a9-2f7b-b2ec-69a969bfcf87@foobar.org>
Date: Thu, 24 May 2018 13:49:17 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 PostboxApp/6.0.8
MIME-Version: 1.0
In-Reply-To: <F4FC51B2-16C1-464A-B06A-AC474016A481@tislabs.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/KpE2RoDHcFFaIa7UUSwdhdoxcn0>
Subject: Re: [GROW] [Technical Errata Reported] RFC7948 (5366)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 12:49:24 -0000

Sandra Murphy wrote:
> A university abandoning publication of its research and, at least
> right now, not even sustaining the archive of its former
> publications.  Ugh.

Long term document storage is hard.

Has the IETF looked at how to work around this problem?  If so, who is 
dealing with it?  If not, who should be dealing with it?  Should we take 
this up with the RFC Editor team?

Nick