IETF Logo Mail Archive

Re: [Last-Call] Last Call: Moving RFC911 to Historic

Nick Hilliard <nick@foobar.org> Fri, 21 January 2022 17:23 UTC

Return-Path: <nick@foobar.org>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98F223A0E92; Fri, 21 Jan 2022 09:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.614
X-Spam-Level:
X-Spam-Status: No, score=-2.614 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, 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 FBOx8aVVhvwB; Fri, 21 Jan 2022 09:23:06 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B0253A0EAF; Fri, 21 Jan 2022 09:23:05 -0800 (PST)
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) by mail.netability.ie (Postfix) with ESMTPSA id BA2979CE80; Fri, 21 Jan 2022 17:23:02 +0000 (GMT)
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: last-call@ietf.org, IESG <iesg@ietf.org>
References: <164271803816.5455.7128644306829727169@ietfa.amsl.com> <69AE07DD-FCBD-471A-886A-57283504E42C@eggert.org> <CAMMESsxqtU6_eESoO353_bAa_k3Z69erA6744_ixDPYRaBCgmA@mail.gmail.com> <74B3331408B367B0FBB9A50E@PSB> <383635E3-E682-496A-AF10-8C9683445C94@akamai.com> <76ABA366533E237CC4E219FD@PSB> <C1F96261-C284-4785-AAED-7A50336C7E20@vpnc.org>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <e2bcc243-a85d-83ef-a328-5c6feb5d20dc@foobar.org>
Date: Fri, 21 Jan 2022 17:23:01 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.54
MIME-Version: 1.0
In-Reply-To: <C1F96261-C284-4785-AAED-7A50336C7E20@vpnc.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/4kFzvDsDfr7DX_h1Dw9uVVYJpfs>
Subject: Re: [Last-Call] Last Call: Moving RFC911 to Historic
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2022 17:23:12 -0000

Paul Hoffman wrote on 21/01/2022 16:38:
> This seems like a lot of effort for no defined (or discernible) value to 
> the RFC-reading community.

what's the long term plan with rfc garbage collection at the ietf?  To 
leave obsolete documents accrete indefinitely, or to implement some form 
of pruning, either ad-hoc or more systematic?

Nick

v2.46.0 | Report a Bug | By Email | System Status