IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

John Levine <johnl@taugh.com> Fri, 13 November 2020 18:47 UTC

Return-Path: <johnl@iecc.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 6FC773A1036 for <ietf@ietfa.amsl.com>; Fri, 13 Nov 2020 10:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-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=iecc.com header.b=pI8ScO9T; dkim=pass (2048-bit key) header.d=taugh.com header.b=HasO6tlU
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 1X43JmOnPwFW for <ietf@ietfa.amsl.com>; Fri, 13 Nov 2020 10:47:17 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 174333A1031 for <ietf@ietf.org>; Fri, 13 Nov 2020 10:47:16 -0800 (PST)
Received: (qmail 7711 invoked from network); 13 Nov 2020 18:47:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1e1c.5faed4b4.k2011; bh=4ylN6d3MBeX/R0txsNnTilxs6KaX4i/KM+i6hDJ/yVA=; b=pI8ScO9TF3FcdvVTWtK0x/L7BD23xSlzRu5L4fVOeZkGFJhaSHD8uCOJ73j5CNlDx0IE1VkwRbkSa6GuwfFVcjCA08iJSd874blVg3M3Kfe3iAeY/u8gR0DIPr9DN+ph0KRD4saX9nAxIsCRJqD2P0FY9xoA9vh2Kj06BuHebJONbVIQF+1DYJKzqtPD5v4nPURHaCG6cyBUAj4E7rbqiRrhWXTvIQNirJ5uOi0f4K48ufDUgIZpY8OIMPYNzMSS2WSAlVuM61xuUDgf0h+yrXdNwrX3CNJ7xc09cqD98GVNE2/HuZMgtfhjTS+nWXX6SAkGTmJWtlJlzUg7hPHRIA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=1e1c.5faed4b4.k2011; bh=4ylN6d3MBeX/R0txsNnTilxs6KaX4i/KM+i6hDJ/yVA=; b=HasO6tlUHzukA8zXrF8G/3HQfEB33VnAeNlSwCPL/47vNAGBazhWamr972aAdpeWiPuJxzr1o5YpQYM8+tN6t792bg66JIXqnHy6wHG4jna3C88oVMAESUFUuNecEA+8dZjUI/OrUtK2urIkIG+4cLpCMx5Xr43KOc/EcxiTaFMZW0xug4O0NkWB768ry4VvkT/wfKrFp9oSWAwQPPInACfiQ74U3EenBE9Xfb8VLACWnrNFKPzJ551Oh/BjanFPNIntkpvzgysUg+UT/4340zVyFSh3vcdi5YLEL1v2t0GCjZ331WMQFSa3kVei2Tj0YCAUhNDo90LqsxgH6Oyn4g==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 13 Nov 2020 18:47:15 -0000
Received: by ary.qy (Postfix, from userid 501) id 3180627062A4; Fri, 13 Nov 2020 13:47:14 -0500 (EST)
Date: Fri, 13 Nov 2020 13:47:14 -0500
Message-Id: <20201113184715.3180627062A4@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Cc: moore@network-heretics.com
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
In-Reply-To: <a817bcca-2a4e-3808-2b48-9f1ea9cbe7d0@network-heretics.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iBgLG_rWFqFt3KuVCPj5DaAtVag>
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 18:47:19 -0000

In article <a817bcca-2a4e-3808-2b48-9f1ea9cbe7d0@network-heretics.com> you write:
>On 11/13/20 1:01 PM, John Levine wrote:
>>> 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.
>> This makes no sense. What computers do you believe that people use in
>> 2020 that support FTP but not rsync? And if that were true, why do we
>> see orders of magnitude more rsync traffic than FTP?
>
>1. rsync is not good for file access

I suppose there is a definition of file access for which that might
still be true. I use rsync every night to mirror the rfc and i-d
archives on my laptop. Works great. It is not 1995 any more and nobody
sensible mounts a remote directory for one at a time retrieval of
small files over a WAN.

>2. traffic volume is not an indicator of importance.

At some point of course it is. We're talking about 1/5000th of the
traffic here, with strong hints that a lot of that trickle could
easily switch to other paths.

R's,
John

v2.23.0 | Report a Bug | By Email