IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 04 April 2021 22:15 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 EF3353A1C9F for <tools-discuss@ietfa.amsl.com>; Sun, 4 Apr 2021 15:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 zieeICtMP0aw for <tools-discuss@ietfa.amsl.com>; Sun, 4 Apr 2021 15:15:43 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21C7A3A1C9E for <tools-discuss@ietf.org>; Sun, 4 Apr 2021 15:15:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id E67BC38C54 for <tools-discuss@ietf.org>; Sun, 4 Apr 2021 18:22:19 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id uQUXxO3ogMsD for <tools-discuss@ietf.org>; Sun, 4 Apr 2021 18:22:19 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0F0BA38C53 for <tools-discuss@ietf.org>; Sun, 4 Apr 2021 18:22:19 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A6F8294B for <tools-discuss@ietf.org>; Sun, 4 Apr 2021 18:15:39 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: tools-discuss@ietf.org
In-Reply-To: <F18134E0-48CF-487E-B62B-15EEFB9EC9D8@vpnc.org>
References: <3C729A10-5F70-465F-AD97-0A1338836C82@vpnc.org> <4790f6a6-5893-e8e6-7361-74657a6735d7@gmail.com> <D0B2EBC2-41CE-44A4-877A-3F943DD33739@vpnc.org> <75441513-8DBB-4A0E-A943-E0CF22CDCD16@tzi.org> <7f98e83b-505e-325d-6795-8fff85517112@gmx.de> <F18134E0-48CF-487E-B62B-15EEFB9EC9D8@vpnc.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 04 Apr 2021 18:15:39 -0400
Message-ID: <7972.1617574539@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/j36uYT_-eqspdK_ruPBQomhRzj4>
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 22:15:48 -0000

Paul Hoffman <paul.hoffman@vpnc.org> wrote:
    >> Am 04.04.2021 um 18:19 schrieb Carsten Bormann:
    >>> On 2021-04-04, at 18:14, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
    >>>>
    >>>> Everyone with tools that generates URLs to them.
    >>>
    >>> Cool URIs are stable [1].  Those URIs are not going away.  Google
    >>> still prioritizes them.  Thousands of RFC, I-Ds, papers, articles,
    >>> blog entries reference them.  (And the above tools still generate
    >>> them.)
    >>>
    >>> I genuinely hate to say this, but at some point we’ll need to find a
    >>> way to take control of what is behind these URIs.  ...
    >>
    >> True. Maybe just redirect?

    > That would be the easiest solution to implement and, at the same time,
    > the most flexible for the future.

I wonder if putting a robots.txt on tools.ietf.org would also be helpful to
direct search engines away from it.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email