IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

Keith Moore <moore@network-heretics.com> Thu, 03 December 2020 17:53 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 B8B9B3A0E68 for <ietf@ietfa.amsl.com>; Thu, 3 Dec 2020 09:53:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001, T_SPF_HELO_TEMPERROR=0.01, 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 8vSTZHwBNsHX for <ietf@ietfa.amsl.com>; Thu, 3 Dec 2020 09:53:33 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66CD63A0C6C for <ietf@ietf.org>; Thu, 3 Dec 2020 09:52:46 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6DBF15C0093 for <ietf@ietf.org>; Thu, 3 Dec 2020 12:52:45 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 03 Dec 2020 12:52:45 -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=fm1; bh=3qhFmtp21kUtMzHEQusO0nLvVUch6P65y/oaFAlPj jQ=; b=Ktn48ZU6k3uBYUSD1aL8hG8UuHah6Io3C1EBR3bQtX+LYkhHp5lcaqwh6 8PIdNGSr6vJl/XszZpzOb/oc/SsUDZw0veUqlZZoCIbg+0CZlBdmMAQ2zbF/k12R +hdv6HAJ8TRmyomUtgUCNS38qDI7QTZ+4PBgoKiZsG7O9v0jGvoOL1DcHYNzlavV ksxu5kDQuuhUZKW+32vZghpn6H7Ci/pS35pRFh7aWkFOXsHE8Ltpu1NoI+FYSrXI zGu5ncf+hFL4gw8pfQS6WYDHiAQu7doAqfzj47/AWAIQvpqEfgu87ILjLOSpBtiY m/+gdcPzJWNy3TJvITgIg772X0uFA==
X-ME-Sender: <xms:7SXJXzxvjijOwwNkd-UaTQqZMkohiOYMJxtR5BwTP403TxK2dsrK5g> <xme:7SXJX7Rg2xeN4-tnk1qFoFK5PJWZh22bLwjzFHW_EAI8w-HyKMX_-dB0TW8B7DN52 Ha7lm8Z7bHn9g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeiiedguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ejredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepkedvgefgle euleekuefhffehgefhhfekuedvudduiefhhedufefftdfgtdekfffgnecukfhppedutdek rddvvddurddukedtrdduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:7SXJX9U8mnbdzCO_QVMWvmxnhm5BV3qMiwxcc77DRT9zqOFBlltPxQ> <xmx:7SXJX9iwkiE22rrQHz-wZNgbQugClcOHHWFlU7lt0Rx4C5Psv9xkeQ> <xmx:7SXJX1Agu6lVn_6iyLhT3a1tpuSTRBqGQgjacM569Cqio9y7gPzVug> <xmx:7SXJXxyRqoI6rQtyARmdJA3oAyTyeYz_T5lfzc_w5qg36F1ZA_foHQ>
Received: from [192.168.1.85] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 05D53108005F for <ietf@ietf.org>; Thu, 3 Dec 2020 12:52:44 -0500 (EST)
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: ietf@ietf.org
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <9D07ED68-DBF8-4E9D-966A-D7688A384E69@sobco.com> <b67218b9-665e-981a-28d9-49137a4d65cc@pi.nu> <CAM4esxQNTM25n5Og9V8R1nyDE8GQdit2XsQhrC5_cMHdZTu4iQ@mail.gmail.com> <A21A7AE01D9D7FF35E88EA0B@PSB> <24b37da4-d40b-0507-59fa-4e9419cd22ce@nostrum.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <f5029998-8805-2c53-2e3c-36fe7d92b1a9@network-heretics.com>
Date: Thu, 03 Dec 2020 12:52:43 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <24b37da4-d40b-0507-59fa-4e9419cd22ce@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/ClczpgKVR4w-PTWoz0LZSkv3fK8>
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, 03 Dec 2020 17:53:47 -0000

On 12/3/20 12:49 PM, Adam Roach wrote:

> For what it's worth, I think we're already in the second of these 
> scenarios. I went looking for publicly visible information about the 
> FTP server on the IETF web site, and cannot find it (aside from a 
> single mention that the server *exists* without actually giving its 
> name or address).

In general, the IETF web site is appallingly bad at helping people find 
the information they need, so there's nothing exceptional about the lack 
of FTP server information.

Keith

v2.23.0 | Report a Bug | By Email