Re: Clarifying the state of and the transition plan for tools.ietf.org

Keith Moore <moore@network-heretics.com> Wed, 10 March 2021 05:47 UTC

Return-Path: <moore@network-heretics.com>
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 22F2B3A1A99 for <ietf@ietfa.amsl.com>; Tue, 9 Mar 2021 21:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=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=messagingengine.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 Hvl8OeSRSq9Y for <ietf@ietfa.amsl.com>; Tue, 9 Mar 2021 21:47:34 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F09DF3A1A97 for <ietf@ietf.org>; Tue, 9 Mar 2021 21:47:32 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id CD6F65C00E7 for <ietf@ietf.org>; Wed, 10 Mar 2021 00:47:30 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 10 Mar 2021 00:47:30 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=4P3oLrOHJDa2VOWSPATz5uqVr51LzK5BzBhJN0fqu s0=; b=apo9H79ewjBmr+P+hIHAZ5l4PDz6ChmFkD6Y32kKslQUR9n5Kqkc4GwkE OgAvjAu/4FmEb6Z+BaT90CEVNA94V6LNEcmEMxg5Z7lXUZT4VB8HtVox4bsq4Nh/ ik7DOAgepyifyDAJUnv+o7AvoKiiJflH3kXrnngyL8cqJ4dniPTK+DTgVBdLOIlX d/PaBJfI81ZXC4guOOALqY/PLivk739eEn8O5yJBtzE6AjeI8kS8X7zUnItKRMjc 5WTZuTgjmRMdqMjG86xerBcIMfzPcZz8Ym+gje/b7ajPAnhGOgxvF07hQg+jO2+1 Epx7Q5OztB2fBnSh1jNVwSMq9QBUQ==
X-ME-Sender: <xms:cl1IYDCektgGGwZWTiV0VGpdS7CDCoFRNMSFZsmoRGEib1NeImXgdg> <xme:cl1IYJiWwqwCsZ1kmNClCCiFZoyRWks3JEQjHpw91wKkC-LmaPcBfM6LzZnJOMVLe dp6ROAeb5KIcQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddujedgjeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtje ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrghtthgvrhhnpeekheelgfelvd ehudeuffeutdehtdetieekudekvddtueellefgffeuvdevhfehueenucffohhmrghinhep ihgvthhfrdhorhhgnecukfhppedutdekrddvvddurddukedtrdduheenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:cl1IYOkGp_3Buag-qHTai4iIcKOdxHygY5YVXjcseJrrtSJdmnBHew> <xmx:cl1IYFyzAsIYrh2TZTgkyiv34ZBJvmpYRgGD9HmtKGlkxCCsW0wrGw> <xmx:cl1IYITKXmXiCACbwvJA0N1vpa_iWQBi3m9wP9P75h1jS3ZCcq8hlw> <xmx:cl1IYOC3uYUax8BYZo0dzD2AaLOdaXjMwgQb0WKpZuNED5OCtMQK7A>
Received: from [192.168.1.90] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 5F0C3108005C for <ietf@ietf.org>; Wed, 10 Mar 2021 00:47:30 -0500 (EST)
Subject: Re: Clarifying the state of and the transition plan for tools.ietf.org
To: ietf@ietf.org
References: <e446a64e-0cfa-d97f-a604-50776242c8f0@nostrum.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <d354b692-4a4c-6bc2-48e0-5be29952e5dd@network-heretics.com>
Date: Wed, 10 Mar 2021 00:47:29 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <e446a64e-0cfa-d97f-a604-50776242c8f0@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5GjW18Qsqi36LkjHynaEaR5G-rQ>
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: Wed, 10 Mar 2021 05:47:35 -0000

Robert,

Reading your note I find myself wondering: Is IETF deliberately trying 
to discourage its participants from building tools to help them do IETF 
work?

thanks,

Keith

On 3/9/21 1:16 PM, Robert Sparks wrote:
> The services at tools.ietf.org are undergoing a transition.

[etc]