Re: Call for Community Feedback: Retiring IETF FTP Service

John Levine <johnl@taugh.com> Fri, 13 November 2020 18:01 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 726E63A1001 for <ietf@ietfa.amsl.com>; Fri, 13 Nov 2020 10:01:57 -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=aU1Miyax; dkim=pass (2048-bit key) header.d=taugh.com header.b=kEgL8cT/
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 09Omyhn7qOIO for <ietf@ietfa.amsl.com>; Fri, 13 Nov 2020 10:01:55 -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 6260F3A0FFB for <ietf@ietf.org>; Fri, 13 Nov 2020 10:01:54 -0800 (PST)
Received: (qmail 91939 invoked from network); 13 Nov 2020 18:01:52 -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=16721.5faeca10.k2011; bh=n5GfmAojk+/mHaMn17pKDWo6Rl6UwgXqPx3xO3Z9zzY=; b=aU1MiyaxWL2kgHoWqy9qf8diZNpXroIP2KNA14RZ9RsKw/1K91t+j0c/5eFx/sBRBbA7boqidmwytj/wUcmVPuZx+RB4ZokiwRDXbgY05+C3w5wA+2C/dC09sIhxmZr96ZqxDbfpayvS7jPnDC5r1fC0vPYaY+bl1tWZCprSq0unwE8zsU8CFIoJ1K/Q2V746CguX3dAdEvTD3ah6JZsLjj8tNAxbwMNc+GqRWog3X4VVsEZ3pypdFfmBHVhCOSWainwQZ055CfVL7St/0iAWjlMrQGtr1+YOceG2yOMtP/8e80QixXwWSkD5Ylpp0Bf5C+A8ovSFS60HU2gKeecow==
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=16721.5faeca10.k2011; bh=n5GfmAojk+/mHaMn17pKDWo6Rl6UwgXqPx3xO3Z9zzY=; b=kEgL8cT/SDKw6yvf0aNnq5XKbQLnpLvYjeWKL6zL0unGtM8fGOUDjfaqzTMZ5vXQBAGbUZIXNoYyzp6t1OpSCWr2mU6AdDhdNisJ0c3ltyDPbLtzj/+VBSZMgkl57cQdcsxXn3WVUyfwUaGvBNEMZAviCFFk5mwmZozaGEO2Gr7Q+2tsZ6YzdmILMhrs7rsPpq7FpokmjtXpp5DIK7JSHZU7PDe3ID9P7mic5/LcT4tgpl8XJKE5G9F5IaPtSYmqXBrdJHrquApkfNoosHbslWuuONZSg/xpmosWNAldY1/8fUsGeO2VRWUVEau6Vyy6mC2xtiA/fc/MVjJvUqVnzg==
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:01:52 -0000
Received: by ary.qy (Postfix, from userid 501) id AF0EE26FB007; Fri, 13 Nov 2020 13:01:50 -0500 (EST)
Date: 13 Nov 2020 13:01:50 -0500
Message-Id: <20201113180151.AF0EE26FB007@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: <60648e0e-55d6-86a1-e40f-342133110f9d@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/CxhHhd1jWNFSIdV50bmJKMiZfPw>
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:01:57 -0000

In article <60648e0e-55d6-86a1-e40f-342133110f9d@network-heretics.com> 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 (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.

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.

R's,
John