Re: Call for Community Feedback: Retiring IETF FTP Service

Donald Eastlake <> Fri, 13 November 2020 18:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B2FEB3A0E68 for <>; Fri, 13 Nov 2020 10:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Status: No, score=-1.848 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MNcnEvigUw5D for <>; Fri, 13 Nov 2020 10:09:17 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6810B3A09C0 for <>; Fri, 13 Nov 2020 10:09:17 -0800 (PST)
Received: by with SMTP id q1so9259120ilt.6 for <>; Fri, 13 Nov 2020 10:09:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rXxytkMTo6H9gSDMzwImALA/Cug+a5aXLzHT8UMRuIA=; b=LrvK5D5DKg40q8N5pqOkCsXB1VZT0/tV+hJ0ISsGz7IK+thHaC8bANcG2DyX5SytB0 Fpg/lE4CG+/NeqUjQ8GdtMD1toMtYILBioNbZKlyMe0UuBSHUbHCJBsfGUdy+fiuddal M7/URQFrwbkQX62xPA30hLYnXWWlMRNrEhJ//7tQfK9yU4r7b1Or4PDwj/6WIKny6jRq 9g8Jm3jPiswFHQbSafzWs2g+V8S9QodN63azIkR7/AGhv2cyMXvlSX5j7kRkJ6G4WhYE WvzOqVWH5wmmg3Gja1+jsxZVcBKOgL0qeoo4BcTJUVuxyT8yixK2QBSSxHPQazVPDQ0n oU2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rXxytkMTo6H9gSDMzwImALA/Cug+a5aXLzHT8UMRuIA=; b=VmYX3S2svbhS8sHsE23mxEoP0ypIV6peEGTc+OiJRGtCyNOiNdY/RSDvhIM060HoFA 7qkAJtZmvittf7BtpwPSdLVyCUDVnrVDjDD6+Z1MQXTFWLYgFwIBC3c89u2NTrfQjVMq RSgGFrY7W2iJ0xPz9fZX9k3X1kDwje7dUDsn+YxJEDasiF/it/Rw99IUvPgoGB9pdV8E sJpD7O/ndjSPniBPpPcDmmycowznWhKLINftxVgnwJvl256P3jAGu8MH4VoL+cPQtKfK 1hIgtYxAFkplxdpGD5v0G8hszYY6Y6VsMNu/bhnPymUQb8CDhaAF/Vq/hEt4fN3i5pm1 1vWA==
X-Gm-Message-State: AOAM531NaQXEhHEUH5eJ8xMpSPwK37e7+sJ8+BiKqwjr5S4/FSAVEJOr vJ7npdBvTX3wIzzUSW8rpRJ1MdQDPD2+xluVQ2Y4e5+Aj1iDog==
X-Google-Smtp-Source: ABdhPJyC0ixotzlsGCaPIHHFz5B6zSJPpjtYj7TGjXw7ZKbcNpLUHxbsnO79aVxtPf938wxCk0Y74mhHkzhFmbaNEl0=
X-Received: by 2002:a05:6e02:1094:: with SMTP id r20mr879772ilj.40.1605290956029; Fri, 13 Nov 2020 10:09:16 -0800 (PST)
MIME-Version: 1.0
References: <> <20201113180151.AF0EE26FB007@ary.qy>
In-Reply-To: <20201113180151.AF0EE26FB007@ary.qy>
From: Donald Eastlake <>
Date: Fri, 13 Nov 2020 13:09:04 -0500
Message-ID: <>
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: John Levine <>
Cc: IETF Discussion <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 13 Nov 2020 18:09:19 -0000


On Fri, Nov 13, 2020 at 1:02 PM John Levine <> wrote:
> In article <> you write:
> >On 11/11/20 10:40 PM, Roman Danyliw wrote:
> >
> >> As noted in the proposal, ALL data is available at least two other ways (  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.
> 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?
> I use a Mac laptop which, based on what I've seen at IETF meetings, is
> a fairly popular choice.  It has rsync as part of the base system, and
> no FTP client other than as part of curl, which of course also supports
> http and https.

It does have sftp :-)

 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA

> R's,
> John