Re: Call for Community Feedback: Retiring IETF FTP Service

John C Klensin <john@jck.com> Thu, 03 December 2020 06:22 UTC

Return-Path: <john@jck.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 2AA423A03F4; Wed, 2 Dec 2020 22:22:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 kCGHXbuEA20T; Wed, 2 Dec 2020 22:22:03 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18A2C3A03F1; Wed, 2 Dec 2020 22:22:03 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1kki06-0001w8-W7; Thu, 03 Dec 2020 01:21:58 -0500
Date: Thu, 03 Dec 2020 01:21:53 -0500
From: John C Klensin <john@jck.com>
To: Martin Duke <martin.h.duke@gmail.com>, Loa Andersson <loa@pi.nu>
cc: ietf@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
Message-ID: <A21A7AE01D9D7FF35E88EA0B@PSB>
In-Reply-To: <CAM4esxQNTM25n5Og9V8R1nyDE8GQdit2XsQhrC5_cMHdZTu4iQ@mail.gmail.com>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <9D07ED68-DBF8-4E9D-966A-D7688A384E69@sobco.com> <b67218b9-665e-981a-28d9-49137a4d65cc@pi.nu> <CAM4esxQNTM25n5Og9V8R1nyDE8GQdit2XsQhrC5_cMHdZTu4iQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zWDnGHwP5ChjErM1rEcnxqDLG64>
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: Thu, 03 Dec 2020 06:22:04 -0000


--On Wednesday, December 2, 2020 18:31 -0800 Martin Duke
<martin.h.duke@gmail.com> wrote:

>  So I'm hearing that the people actually running the FTP
> service believe it to be a significant nuisance, and some
> subset of the community think that it is obviously trivial.
> Would it be too much to ask one of the FTP enthusiasts to
> volunteer to maintain it, so that those who have tired of it
> can move to other things?

Unfortunately, at least as I understood it, the claim/belief was
not [only] about its being a significant nuisance to maintain
but that it was also consuming other resources that the powers
that be didn't want to pay for any more.   Unless the latter has
changed --i.e., that the LLC would be happy to maintain the
service if someone volunteered to maintain the software and
tools -- having such volunteers would be of no help at all.

> I'm sure we can migrate it to a URL that makes it clear it is
> volunteer-driven.

There is also the question or whether the IETF tells people this
is an available option or whether it is a little secret among
the relevant volunteer and a few hundred or her closest friends.
If the former, the IETF and/or the IETF Administration LLC take
on some responsibility for keeping it available or providing
appropriate notice before it is shout down.

So, overall, I don't see that suggestion as helpful... much as I
would like to see this discussion end and stop consuming time
and bandwidth.

  john