Re: Call for Community Feedback: Retiring IETF FTP Service

ned+ietf@mauve.mrochek.com Tue, 17 November 2020 14:15 UTC

Return-Path: <ned+ietf@mauve.mrochek.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 C77413A135E for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 06:15:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Cv0INKGGDRFu for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 06:15:46 -0800 (PST)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (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 E38903A1368 for <ietf@ietf.org>; Tue, 17 Nov 2020 06:15:45 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RS3W7GVSOG009CQM@mauve.mrochek.com> for ietf@ietf.org; Tue, 17 Nov 2020 06:10:42 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RS3VULAJ5S005PTU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 17 Nov 2020 06:10:39 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Cc: Keith Moore <moore@network-heretics.com>
Message-id: <01RS3W7DNPHA005PTU@mauve.mrochek.com>
Date: Tue, 17 Nov 2020 06:01:49 -0800
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
In-reply-to: "Your message dated Tue, 17 Nov 2020 05:49:05 -0500" <6ff3c8a8-57c9-a278-51ce-ce24fd2dfc0e@network-heretics.com>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <0D41F3FD-BA1F-4716-A165-4FE7529431A9@vigilsec.com> <D26DCBB6-3997-4A73-BB46-867B4FD79BD2@eggert.org> <27b80ed2-76fb-aee7-f22d-de56019e9aa9@nostrum.com> <a8bdd67a-13ea-4433-aa38-9cfd48ea28da@network-heretics.com> <0e875497-9986-a0d9-8354-3eac26b7f882@nostrum.com> <a02e15f2-34fb-4124-7ba0-c0ee0070b39f@network-heretics.com> <6a29096e-c76e-9bde-388c-bf411b235346@nostrum.com> <6ff3c8a8-57c9-a278-51ce-ce24fd2dfc0e@network-heretics.com>
To: ietf@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RXzbxmpS0kTlbv0iDZNt9vvMMbs>
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: Tue, 17 Nov 2020 14:15:47 -0000

The discussion of FTP service retirement has actually been surprisinginly
informative. Things I've learned include:

(1) The IETF no longer provides HTTP access, leaving FTP as the only
    access mechanism that doesn't require a crypto layer. With FTP gone,
    crypto becomes a requirement for access.

(2) Some people believe implementation of an FTP client is difficult,
    more difficult than implementing HTTPS.

(3) There is concern over the attack surface of an FTP server, but in
    practically the same breath (message) people are considering getting
    back some functionality by deploying WebDAV.

I mention (2) and (3) because I always find it interesting how people weigh
various tradeoffs.

For me the decider is (1). I don't like FTP all that much, but if it's
the only remaining access mechanism that doesn't call for crypto, I like
losing it a whole lot less.

Let's please keep the FTP servers going.

				Ned