IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

Loa Andersson <loa@pi.nu> Thu, 12 November 2020 07:09 UTC

Return-Path: <loa@pi.nu>
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 69ECC3A14B3; Wed, 11 Nov 2020 23:09:03 -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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 Q4RUknOUlJr1; Wed, 11 Nov 2020 23:09:01 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD7933A14B2; Wed, 11 Nov 2020 23:08:59 -0800 (PST)
Received: from [172.20.156.104] (unknown [185.147.213.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id B7AA731EE70; Thu, 12 Nov 2020 08:08:56 +0100 (CET)
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: "Scott O. Bradner" <sob@sobco.com>, "ietf@ietf.org" <ietf@ietf.org>
Cc: iesg@ietf.org
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <9D07ED68-DBF8-4E9D-966A-D7688A384E69@sobco.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <b67218b9-665e-981a-28d9-49137a4d65cc@pi.nu>
Date: Thu, 12 Nov 2020 15:08:54 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.2
MIME-Version: 1.0
In-Reply-To: <9D07ED68-DBF8-4E9D-966A-D7688A384E69@sobco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KlM5s0qVWhN9vTdcIYj28g9r99A>
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, 12 Nov 2020 07:09:03 -0000

All,

That was my thought also, if we claim "operational complexity" we should 
maybe try to be explicit.

/Loa

On 10/11/2020 19:55, Scott O. Bradner wrote:
> 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)
>>
> 

-- 

Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting             phone: +46 739 81 21 64

v2.23.0 | Report a Bug | By Email