Re: Call for Community Feedback: Retiring IETF FTP Service

Chris Inacio <inacio@cert.org> Fri, 20 November 2020 16:38 UTC

Return-Path: <inacio@cert.org>
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 99EF73A0E50 for <ietf@ietfa.amsl.com>; Fri, 20 Nov 2020 08:38:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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=cert.org
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 WYHRjtCcKfOT for <ietf@ietfa.amsl.com>; Fri, 20 Nov 2020 08:38:42 -0800 (PST)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (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 325343A0E4B for <ietf@ietf.org>; Fri, 20 Nov 2020 08:38:41 -0800 (PST)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AKGcfox018899 for <ietf@ietf.org>; Fri, 20 Nov 2020 11:38:41 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu 0AKGcfox018899
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1605890321; bh=IOtkOH729oJzdgj8ZBSc8fO8Qk3ejdI2L5vHOUINDIA=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=cX1FOAA8al+L/ndWRphXSa28WRWS+E+nnQW5q2xoaTF1/5vSgGm/28MhCyj0/SZNO ML8nNR97tiNUQB6k+sqh3KQgMvKuI/Q8oUWh2xmq3adv4LSBplIjvSYdgz3kdquU2r pk329MT2K4qZVD8fHqClhRTXm4stLBHEuvqcuUhc=
Received: from MURIEL.ad.sei.cmu.edu (muriel.ad.sei.cmu.edu [147.72.252.47]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AKGca9R025790 for <ietf@ietf.org>; Fri, 20 Nov 2020 11:38:36 -0500
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MURIEL.ad.sei.cmu.edu (147.72.252.47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 20 Nov 2020 11:38:36 -0500
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.2106.002; Fri, 20 Nov 2020 11:38:36 -0500
From: Chris Inacio <inacio@cert.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
Thread-Topic: Call for Community Feedback: Retiring IETF FTP Service
Thread-Index: Ada3CD1BnAYFDyoMT8WUdvX4VBiWMQFJu10AANWVIAA=
Date: Fri, 20 Nov 2020 16:38:34 +0000
Message-ID: <138B3221-5A32-4DB0-AA1C-1D8D09D93B89@cert.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <0D41F3FD-BA1F-4716-A165-4FE7529431A9@vigilsec.com>
In-Reply-To: <0D41F3FD-BA1F-4716-A165-4FE7529431A9@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3608.120.23.2.4)
x-originating-ip: [10.64.203.42]
Content-Type: text/plain; charset="utf-8"
Content-ID: <AC1F617D58E69340A18C1799B42488A1@sei.cmu.edu>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nLV6GVOYBVCsEYC4fHO1OWkosHw>
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, 20 Nov 2020 16:38:44 -0000

+1.

FTP was great in its day.  I also really liked gopher.  Maybe more than the current web.  But let’s be real - that’s just not practical at this point, IMHO.  The Internet (at large) has moved on, possible even enabled by IETF, we should keep to that reality.

Chris


> On Nov 16, 2020, at 5:43 AM, Russ Housley <housley@vigilsec.com> wrote:
> 
> I support turning off the FTP service at ietf.org. The FTP daemon places frustrating constraints on the file system structure.  HTTPS offers much greater security, and it does not impose constraints on the file system structure.
> 
> Russ
> 
>> On Nov 9, 2020, at 9:23 PM, Roman Danyliw <rdd@cert.org> wrote:
>> 
>> Hi!
>> 
>> The Internet Engineering Steering Group (IESG) is seeking community input on retiring the IETF FTP service (ftp://ftp.ietf.org, ftp://ops.ietf.org, ftp://ietf.org).  A review of this service has found that FTP appears to serve a very small community and HTTP has become the access mechanism of choice.  Given this shift in community usage, reducing the operational complexity of the overall IETF infrastructure seems to outweigh the very limited community served with FTP.  
>> 
>> In reviewing the additional impacts of such a service retirement, the dependencies on FTP have been assessed.  Additionally, it has been confirmed that all information currently reachable through FTP will continue to be available through other services (HTTP, RSYNC, IMAP).
>> 
>> In consultation with the Tools team (Robert, Glen, Henrik, Russ, and Alexey), Communications team (Greg), affected SDO liaisons, IAB Chair, and LLC ED, a proposed retirement plan was developed and is available at:
>> 
>> https://www.ietf.org/media/documents/Retiring_IETF_FTP_Service.pdf
>> 
>> The IESG appreciates any input from the community on this proposal and will consider all input received by December 4, 2020 (to account for the upcoming IETF 109 and holidays).
>> 
>> Regards,
>> Roman
>> (as the IESG Tools Liaison)
>> 
>