[Tools-discuss] missing RFC numbers: 404 vs. "was never issued"
Daniel Kahn Gillmor <dkg@fifthhorseman.net> Tue, 11 December 2018 20:12 UTC
Return-Path: <dkg@fifthhorseman.net>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0414130F55 for <tools-discuss@ietfa.amsl.com>; Tue, 11 Dec 2018 12:12:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Level:
X-Spam-Status: No, score=-4.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_SPF_PERMERROR=0.01] 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 SSmbChiDpdtM for <tools-discuss@ietfa.amsl.com>; Tue, 11 Dec 2018 12:12:31 -0800 (PST)
Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A24C0124D68 for <tools-discuss@ietf.org>; Tue, 11 Dec 2018 12:12:31 -0800 (PST)
Received: from fifthhorseman.net (unknown [38.109.115.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id BBF66F99A for <tools-discuss@ietf.org>; Tue, 11 Dec 2018 15:12:29 -0500 (EST)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 64E882043F; Tue, 11 Dec 2018 15:12:18 -0500 (EST)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: tools-discuss@ietf.org
Date: Tue, 11 Dec 2018 15:12:15 -0500
Message-ID: <87sgz3rffk.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Zg8C_VjAatz-KE2P73Ce93mLCzo>
Subject: [Tools-discuss] missing RFC numbers: 404 vs. "was never issued"
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2018 20:12:34 -0000
I notice that in the tools.ietf.org interface (and in the rsync'ed HTML data), some RFCs (like RFC 3889) say explicitly that they were never issued: https://tools.ietf.org/html/rfc3889 ("RFC 3889 was never issued.") However, other RFCs are simply missing (they return an HTTP 404). Some of the gaps in the RFC series are in the xx00 range -- i think these used to be reserved for "Internet Official Protocol Standards" summary documents, and some are numbered xx99, which used to be "RFC summary" documents, both of which are now retired. (see https://tools.ietf.org/html/rfc7100). However, there are a lot of other 404s that aren't numbered xx99 or xx00: rfc8 rfc9 rfc51 rfc418 rfc530 rfc598 rfc3333 rfc3350 rfc3907 rfc3908 rfc4232 rfc4658 rfc4751 rfc4921 rfc4922 rfc4989 rfc5108 rfc5312 rfc5313 rfc5314 rfc5315 rfc5319 rfc5809 rfc5821 rfc5822 rfc5823 rfc6019 rfc6102 rfc6103 rfc6523 rfc6524 rfc6634 rfc6966 rfc6995 rfc7327 rfc7907 rfc8389 For consistency, it'd be nice if either all of these missing RFCs would get the "RFC XX99 was never issued" treatment; or, they could all return a 404. Is there some semantic difference we should infer for one thing over another? --dkg
- [Tools-discuss] missing RFC numbers: 404 vs. "was… Daniel Kahn Gillmor
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Brian E Carpenter
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Sandy Ginoza
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Daniel Kahn Gillmor
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Bob Hinden
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Adam Roach
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Bob Hinden
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Sandy Ginoza
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Bob Hinden
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Heather Flanagan
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Bob Hinden
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Michael Richardson
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Adam Roach
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Bob Hinden
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … HANSEN, TONY L
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … HANSEN, TONY L
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Warren Kumari
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Sandy Ginoza
- Re: [Tools-discuss] missing RFC numbers: 404 vs. … Michael Richardson