IETF Logo Mail Archive

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

Keith Moore <moore@network-heretics.com> Thu, 11 March 2021 02:21 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 EEF443A0CC0 for <ietf@ietfa.amsl.com>; Wed, 10 Mar 2021 18:21:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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 63V3QlYCHNkM for <ietf@ietfa.amsl.com>; Wed, 10 Mar 2021 18:21:47 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E02A3A0CBE for <ietf@ietf.org>; Wed, 10 Mar 2021 18:21:47 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 5319E5C00D8 for <ietf@ietf.org>; Wed, 10 Mar 2021 21:21:45 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 10 Mar 2021 21:21:45 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=ql7tZ5 CRM61iKuQJMw//xJfwMZbWjCE4rYm87pHU6FY=; b=hkYx81Kf3m7bxEeNw+F1u3 BukIU1XKehqw1tGhXd6YwKnYT+VPGgrHuYWXA0kV498G21UZN71xPzzzT4YNa0Vk bsD2hkv00/r6eyEVVAnWWg8IKPqAcW/+Lk7yMFMVzec7k1wSc+TVoNtermbJ/wUv XZGuV2nuRIRukiBGHZL/7fwMa0Oex8ECnUDpFVajzyMsfvc2bhXDAuT+GyTCV+zI Dz/3/5MIMcKnxGmNls+iF9Nqz301g7Bm/fvKf/GvsfHjE0LUHQH96HRiQD3IHvX/ H1Mke5gaL3FQQWgrh2frRlh1T8GYL9cSTzTqYttG2kDRJDXtx1P+saIelWwVmoIA ==
X-ME-Sender: <xms:uH5JYFbNNYpTQM5ILw7IfsdvQXbyGU0QMi1zExarF6AI9NRgxfVM6Q> <xme:uH5JYMbNoVYRCk9diOFkWfmQz9RThSuG_DkQeqncDpIfIJ6akO8NO9Y9ZbvcP72aH zxLugp7BxtxVg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudduledggeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgesrgdtre ertdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepudetfeekveevfe eltdekffeigeelkefgudevgedtvdehjefggffglefhvdeuudeinecuffhomhgrihhnpehi vghtfhdrohhrghenucfkphepuddtkedrvddvuddrudektddrudehnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhr khdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:uH5JYH_ZrJ8M95H3vBsF9oVmP3pBioHN_Z6ALJVuU_2XOQT9uQiTtA> <xmx:uH5JYDoh-C-Oy9QEZcWJESwwcWlEB2O09m-Ob4Of2JMaj9mvlFqyJA> <xmx:uH5JYAoGPITRV8iG7cwsLCi9svbO4OigRSoOYZWRJmXP5DMHQQu8BQ> <xmx:uX5JYJ5l8_qmfpk8ITHOZ5rvGi1YqJ8cwbaqtdC1PwertjMALnRl9Q>
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 6CBE61080063 for <ietf@ietf.org>; Wed, 10 Mar 2021 21:21:44 -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> <d354b692-4a4c-6bc2-48e0-5be29952e5dd@network-heretics.com> <2b074f07-215f-7373-ce66-20594bc74715@gmx.de>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <1352da25-f4a5-c158-5139-489d015fd7c0@network-heretics.com>
Date: Wed, 10 Mar 2021 21:21:43 -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: <2b074f07-215f-7373-ce66-20594bc74715@gmx.de>
Content-Type: multipart/alternative; boundary="------------46A4EB73A4F8D59E0F28AF25"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LGHb2Ja-klG_s4pwQ4l2eCOPPEI>
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: Thu, 11 Mar 2021 02:21:49 -0000

On 3/10/21 2:17 AM, Julian Reschke wrote:

>> Reading your note I find myself wondering: Is IETF deliberately trying
>> to discourage its participants from building tools to help them do IETF
>> work?
>
> What precisely in Robert's mail makes you ask that? 
Never ask an intuitive to explain precisely what makes them ask a 
question ...

Of course it's not only that email that makes me ask, but other signs 
I've seen for awhile.

It's a simple question, which I hope has a simple answer.

Keith

v2.8.7 | Report a Bug | By Email