Re: Call for Community Feedback: Retiring IETF FTP Service

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 17 November 2020 21:08 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 0DBF83A0A2E for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 13:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 jh1xQdY_Q3TA for <ietf@ietfa.amsl.com>; Tue, 17 Nov 2020 13:08:56 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 415593A0A2B for <ietf@ietf.org>; Tue, 17 Nov 2020 13:08:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 8A4D5BE4C; Tue, 17 Nov 2020 21:08:53 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6ceFJe-5Hxt; Tue, 17 Nov 2020 21:08:52 +0000 (GMT)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C602ABE2E; Tue, 17 Nov 2020 21:08:51 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1605647331; bh=dujt9M65xdrZJCcTY+jju4cez4z+fhpXePzuvDTIBa4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=uyo/mOgWyAMre7K9PR4WplKR+mpVsmwsHScHbDG55d5sjRVQ+GpqxPpNbpe1u85b0 1O69NXcC3l0Dziv1LvBjOUBsXZAI+Io7/cjyTGX8AhhJ7KxUtSuH8JP7zBmkkHX/hH 0Q3xm6lRbc6BODrF0eLVFh/CIIOlN8ChrvYtAOEM=
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: Rich Kulawiec <rsk@gsp.org>, ietf@ietf.org
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <d12d2e09-6840-0500-c14c-73d862f85c8e@network-heretics.com> <20201117203038.GA30358@gsp.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <4ddae8d0-866d-9e16-a304-ac78099f725d@cs.tcd.ie>
Date: Tue, 17 Nov 2020 21:08:49 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2
MIME-Version: 1.0
In-Reply-To: <20201117203038.GA30358@gsp.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="g6bb58WQpapmtCyRuJ0lzXbPyvLJRjwX5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DW71uz4YNqF0ZjR2MO4yqDpk4O8>
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 21:08:59 -0000

I'm generally ok with us turning off FTP and don't onsider
it that big a deal either way.

However, I have to say most of the arguments for and against
doing that I've seen in this thread are weak to very weak
and some I'd consider just bogus or exaggerated. That said,
this cost/benefit argument for maintaining the service seems
worth considering:

On 17/11/2020 20:30, Rich Kulawiec wrote:
> is that having a second
> or third way to access information is extremely useful when things go
> very wrong.  If that happens even once over the next 20 years then the
> tiny cost of keeping FTP running will be repaid in full very quickly.

I guess a lot would have to go wrong for a sustained period
for FTP to save the day, but I could just about imagine it
happening. It's not quite movie-plot time but fracturing in
the root stores causing HTTPS to not work everywhere, plus
some SSH bugginess that affected most clients and broke
rsync/SSH might do it. And as we've seen this year, now
and then stuff does hit the fan.

I don't know if it's a sufficiently strong argument but it
is one I'd not considered.

Cheers,
S.