Re: [Tools-discuss] missing RFC numbers: 404 vs. "was never issued"

Bob Hinden <bob.hinden@gmail.com> Wed, 12 December 2018 15:28 UTC

Return-Path: <bob.hinden@gmail.com>
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 40DC4130E13 for <tools-discuss@ietfa.amsl.com>; Wed, 12 Dec 2018 07:28:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TN5_CYMbRj19 for <tools-discuss@ietfa.amsl.com>; Wed, 12 Dec 2018 07:28:02 -0800 (PST)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0CE6127333 for <tools-discuss@ietf.org>; Wed, 12 Dec 2018 07:28:01 -0800 (PST)
Received: by mail-wm1-x333.google.com with SMTP id a18so6429619wmj.1 for <tools-discuss@ietf.org>; Wed, 12 Dec 2018 07:28:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=MWLHiWxwM0QH/u50FKj5diW6+0R/qU0Sk9/pZoK7bIA=; b=FKQoHyRyOWNnXFsfHzUarmMuSlvB9J0xACAPNQLSOOfChiWuNIq0geoplbGvKLdXHI OTGY82QdBQPLUO4/IXhNZDQCU/Ow/Ad/+Mn1gfFGfERk4JILBUudcLjMHd8lfgiX+i3Y 9HsjZimjv/MThZz2TWeKtgSl1XpyAtT7h5IkNxq6A0CzUCNTtjhb7KEyJyg/O+n15gqp NOCK5ahluOHb9mMXbMeKGItFrEswITta9SfFKEidMytLzAc2IUTLA8o82vNDLLhe4L3O c1/45MMTpVgakPOwSBg/Bqi8kvaz60caaw1R2Cb2atA/W7o9v4g7tYEJvv4gWgIEf/cr gK/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=MWLHiWxwM0QH/u50FKj5diW6+0R/qU0Sk9/pZoK7bIA=; b=LUn93ws9LE+OJP93ztqYCINbFtk77GhGb7ss3EU9YEOzoMeIv9M1wSvzM7eyXiCBwZ ToR+udBA92/cd+GNrBeCx8/1WXxmTqhC9oQZ0gafTWjCWEK6Dxhl9lFYObjFwfWPVg4g fShcVZD1EIK3TotBgbi2CX9coSIUOzHN5Q89okqgwNi+yrfTuiFOY9dnJ26qbHHvg3zX YvoXrfL5m9TVagYQEag1cB1B+8MKuHGAo2VbaLHidffvqdYpALRsho80oQ05qV4HZEC4 kMnVIUrdQiKWtf2Y3Shdso3+jXUw3slix8ZDgwemihh/H+H7TcbqJwKNKpgqjdGl/YyY MF+Q==
X-Gm-Message-State: AA+aEWZkHzC7s+asz0lQUeyreAiR9MF4C+6d9RQhQr2SXUvDlCmJJChy ci5U0DzUvDeO8IkbsobpehM=
X-Google-Smtp-Source: AFSGD/VR077cO7Yksm+5OsVoYMbQHME2DFWN3ZioD/3Zdl+RceKi0EIckd8X0tg4Az36DHRNLc0xng==
X-Received: by 2002:a1c:e913:: with SMTP id q19mr6911641wmc.55.1544628480121; Wed, 12 Dec 2018 07:28:00 -0800 (PST)
Received: from [10.0.0.50] (c-76-21-112-100.hsd1.ca.comcast.net. [76.21.112.100]) by smtp.gmail.com with ESMTPSA id y13sm16116539wme.2.2018.12.12.07.27.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Dec 2018 07:27:59 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <5836962E-17D1-4D63-94FD-5A4534F8001C@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D873A867-F901-4162-900E-22E04444F13B"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 12 Dec 2018 07:27:55 -0800
In-Reply-To: <3542348f-195f-c2e7-0c64-66d561e4f0aa@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Tools Team Discussion <tools-discuss@ietf.org>, Sandy Ginoza <sginoza@amsl.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
References: <87sgz3rffk.fsf@fifthhorseman.net> <3542348f-195f-c2e7-0c64-66d561e4f0aa@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/DAbSpQCLWmZjSsN9jhLOTP728eU>
Subject: Re: [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: Wed, 12 Dec 2018 15:28:13 -0000

Brian,

> On Dec 11, 2018, at 2:28 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> There are a few RFCs in your list that were issued in PDF only:
> 8, 9, 51, 418, 500, 598. So a 404 for the .txt files is no surprise,
> but I suppose a redirect to the PDF would be possible.

I had thought that we had text versions of everything by now, wasn’t there a project to do this?

What happened to that?   I am willing to help, I had done a few in the past.

Bob



> 
> Regards
>   Brian Carpenter
> 
> On 2018-12-12 09:12, Daniel Kahn Gillmor wrote:
>> 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 mailing list
>> Tools-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-discuss
>> 
>> Please report datatracker.ietf.org and mailarchive.ietf.org
>> bugs at http://tools.ietf.org/tools/ietfdb
>> or send email to datatracker-project@ietf.org
>> 
>> Please report tools.ietf.org bugs at
>> http://tools.ietf.org/tools/issues
>> or send email to webmaster@tools.ietf.org
>> 
> <rfc-not.txt>___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
> 
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
> 
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org