IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

Keith Moore <moore@network-heretics.com> Fri, 13 November 2020 17:07 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 A12AB3A0F4A for <ietf@ietfa.amsl.com>; Fri, 13 Nov 2020 09:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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.001, RCVD_IN_MSPIKE_WL=0.001, 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 uckRYvstcKRl for <ietf@ietfa.amsl.com>; Fri, 13 Nov 2020 09:07:06 -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 772BE3A0EF9 for <ietf@ietf.org>; Fri, 13 Nov 2020 09:07:05 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id B08775C013A for <ietf@ietf.org>; Fri, 13 Nov 2020 12:07:04 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Fri, 13 Nov 2020 12:07:04 -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=5hUrlXTD/NHjLzC8X9m7wLxv2YZDCWKzCaa9QYtOE ZE=; b=bN77ZEg0Jibg6HbAI+wUj9YOdDObET4Fdn3z1c8tUeO9W12sICiM0x3jC P46+iJrA4aMz5qZ958lcFY0VAmOEKcafmlvfFCg5rza2RZV8ZtyPCsf9xhZxys3i XeAQu5xEJbquGm0YyFUqAj2WJEGBHlesleLcpijl0Hpeq9Eb95er9ru97SXAtzNP tZ6UI5kGler0Ig/F6fj8BYtPVQbiEWK8u6nFsQBpMrGJuHXWZodvZWXiR6DPh772 +kKAKD8JpG5RKmdRHpUzl+V1SoNlPi6rkoibK5NS8wIWxWXwwkRpmScNS/MmuJPj c6K7PPRhHqaLfL6QOqCOP+XyIiiJg==
X-ME-Sender: <xms:OL2uX8lXZ642MP9hZV6nQUQahZNBFbt1uxiQBPk_CshODMsSVos_7g> <xme:OL2uX70SIZ5m9UkoaJGxgTt00jfXKBe1dmq8OsKjh1RFSk1rBgw4kVKyHTzFtyVHm HJD2td6p4FCzQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedruddvhedgleejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrghtthgvrhhnpeegffejhfegve etleeukedufedviedvkeeuhfdtieekvdekteejvdetvdfhieefkeenucffohhmrghinhep ihgvthhfrdhorhhgnecukfhppedutdekrddvvddurddukedtrdduheenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:OL2uX6oghy4Z7h3rcTv0vMsoLUjk6oL0Dffdzg_vNF-hymtnyw3PSw> <xmx:OL2uX4kQfQTgQbdxIjmmY0nRifBMS1Q-1Cui_hfH__G0G1xRUuUx8A> <xmx:OL2uX63kqo5X7BgeB7XcSTrC08eqZ8DqYOMaCCku1dGcHhc_vAh6Hg> <xmx:OL2uX92aKUfs8s1c3gCekmFuR_DagRRMAlEz_TT8i-DZ3jGcOXw79w>
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 EC3E93064AAA for <ietf@ietf.org>; Fri, 13 Nov 2020 12:07:03 -0500 (EST)
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: ietf@ietf.org
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <20201110225502.GA60333@faui48f.informatik.uni-erlangen.de> <d08945117193451596a4f3860113747e@cert.org>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <60648e0e-55d6-86a1-e40f-342133110f9d@network-heretics.com>
Date: Fri, 13 Nov 2020 12:07:02 -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: <d08945117193451596a4f3860113747e@cert.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_he4v6Gcyez0FAyx4wMqASoGrXE>
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: Fri, 13 Nov 2020 17:07:08 -0000

On 11/11/20 10:40 PM, Roman Danyliw wrote:

> As noted in the proposal, ALL data is available at least two other ways (https://www.ietf.org/ietf-ftp  or rsync).  By request volume, HTTPS is massively preferred (FTP is 0.2% of HTTPS document traffic, and this is undercounting HTTPS usage) by the vast majority of users.  If the bulk download semantics are desired, to include incremental updates with no code required, then rsync is the best choice.  Do you have a user community in mind that can use FTP, but not HTTPS or rsync that we need to consider?

rsync is not nearly as widely supported as FTP.   And while rsync works 
okay for mirroring, I've never seen it used for remote file access.

Really this proposal is a tremendously bad idea, and it should be withdrawn.

Keith

v2.23.0 | Report a Bug | By Email