Re: Clarifying the state of and the transition plan for tools.ietf.org
Florian Weimer <fw@deneb.enyo.de> Sat, 05 June 2021 15:57 UTC
Return-Path: <fw@deneb.enyo.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id C12B43A26F3;
Sat, 5 Jun 2021 08:57:26 -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 hrPwiMG_Cwlz; Sat, 5 Jun 2021 08:57:22 -0700 (PDT)
Received: from albireo.enyo.de (albireo.enyo.de [37.24.231.21])
(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 3E0003A1649;
Sat, 5 Jun 2021 08:57:21 -0700 (PDT)
Received: from [172.17.203.2] (port=37003 helo=deneb.enyo.de)
by albireo.enyo.de ([172.17.140.2]) with esmtps
(TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
id 1lpYfm-0008Hv-07; Sat, 05 Jun 2021 15:57:18 +0000
Received: from fw by deneb.enyo.de with local (Exim 4.92)
(envelope-from <fw@deneb.enyo.de>)
id 1lpYfl-0006PW-Ta; Sat, 05 Jun 2021 17:57:17 +0200
From: Florian Weimer <fw@deneb.enyo.de>
To: Robert Sparks <rjsparks@nostrum.com>
Cc: ietf@ietf.org, tools-discuss <tools-discuss@ietf.org>
Subject: Re: Clarifying the state of and the transition plan for tools.ietf.org
References: <e446a64e-0cfa-d97f-a604-50776242c8f0@nostrum.com>
Date: Sat, 05 Jun 2021 17:57:17 +0200
In-Reply-To: <e446a64e-0cfa-d97f-a604-50776242c8f0@nostrum.com> (Robert
Sparks's message of "Tue, 9 Mar 2021 12:16:01 -0600")
Message-ID: <87im2s9uea.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/758WhIBgLtvUE3rRi1w6dBdjAd4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>,
<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
<mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jun 2021 15:57:27 -0000
* Robert Sparks: > As you identify issues with tools.ietf.org, please email Henrik or > let me know, and I will bring them to Henrik's attention. In > general, neither the IETF Secretariat nor the tools team can address > issues at tools.ietf.org directly. Our focus will be on moving > functionality to platforms like the Datatracker. The old redirector accepted URLs without an RFC prefix (e.g., <https://tools.ietf.org/html/2822>). The new service apparently does not.
- Clarifying the state of and the transition plan f… Robert Sparks
- Re: Clarifying the state of and the transition pl… Keith Moore
- Re: Clarifying the state of and the transition pl… Julian Reschke
- Re: Clarifying the state of and the transition pl… Keith Moore
- Re: Clarifying the state of and the transition pl… John Levine
- Re: Clarifying the state of and the transition pl… Florian Weimer