Re: [Tools-discuss] Unicode decode error for RFCs

Paul Hoffman <paul.hoffman@vpnc.org> Sun, 04 April 2021 16:14 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 BA9FC3A0B69 for <tools-discuss@ietfa.amsl.com>; Sun, 4 Apr 2021 09:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.188
X-Spam-Level:
X-Spam-Status: No, score=-0.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RCVD_IN_VALIDITY_RPBL=1.31, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 63YNED0cNMho for <tools-discuss@ietfa.amsl.com>; Sun, 4 Apr 2021 09:14:36 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 399C93A0B63 for <tools-discuss@ietf.org>; Sun, 4 Apr 2021 09:14:36 -0700 (PDT)
Received: from [10.10.10.227] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id 134GF5Ce046138 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 4 Apr 2021 09:15:05 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] claimed to be [10.10.10.227]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
Cc: tools-discuss <tools-discuss@ietf.org>
Date: Sun, 04 Apr 2021 09:14:28 -0700
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <D0B2EBC2-41CE-44A4-877A-3F943DD33739@vpnc.org>
In-Reply-To: <4790f6a6-5893-e8e6-7361-74657a6735d7@gmail.com>
References: <3C729A10-5F70-465F-AD97-0A1338836C82@vpnc.org> <4790f6a6-5893-e8e6-7361-74657a6735d7@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/J-EA4k_lzwHjY0thalIV7nJi_Co>
Subject: Re: [Tools-discuss] Unicode decode error for RFCs
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: Sun, 04 Apr 2021 16:14:41 -0000

On 3 Apr 2021, at 20:41, Brian E Carpenter wrote:

> https://datatracker.ietf.org/doc/html/rfc9007 is OK.

Of course. If it didn't, I would have reported that as well.

> And the tools repository is going away anyway.

"going to" does not help current programs that generate URLs to the site 
that has worked for a very long time.

> Maybe the Twitterland needs to be told.

That will be as useful as telling them that they should all be using 
IPv6 addressing. I'm not saying you shouldn't try, but I am saying that 
us doing so absolves us from the responsibility to maintain the current 
infrastructure.

> https://www.rfc-editor.org/rfc/rfc9007.html is even more OK. I mean, 
> who cares about the htmlized versions of HTML RFCs?

Everyone with tools that generates URLs to them.

--Paul Hoffman