IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

"Scott O. Bradner" <sob@sobco.com> Tue, 10 November 2020 11:55 UTC

Return-Path: <sob@sobco.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 A0FB23A09B5; Tue, 10 Nov 2020 03:55:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 SAITt-QTDiOv; Tue, 10 Nov 2020 03:55:46 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id B46763A09A5; Tue, 10 Nov 2020 03:55:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 71769467638C; Tue, 10 Nov 2020 06:55:44 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U9ovfB89_gwG; Tue, 10 Nov 2020 06:55:36 -0500 (EST)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id C1069467637F; Tue, 10 Nov 2020 06:55:35 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <af6ab231024c478bbd28bbec0f9c69c9@cert.org>
Date: Tue, 10 Nov 2020 06:55:34 -0500
Cc: iesg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D07ED68-DBF8-4E9D-966A-D7688A384E69@sobco.com>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org>
To: "ietf@ietf.org" <ietf@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/62aSVFrAErl1ofSBhs6R5PND5mg>
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, 10 Nov 2020 11:55:48 -0000

is there a compelling reason to stop a service that some people are using

the pdf says : "The operational complexity of running this service "

just what complexity is there once the service was set up (years ago)?

i.e., just how much does this service cost to run?
	(seems to me that it is likely that the effort to develop this plan was much more than just letting the service run)

yes, I run one of the scripts that use ftp to access IETF resources and it would be a significant pain to rewrite it
since it is complicated script and I do not know how to do some of its functions in other non-ftp ways

I do seriously want to know how much it costs the IETF to run the ftp service

Scott



> 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)
>

v2.23.0 | Report a Bug | By Email