IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

Stewart Bryant <stewart.bryant@gmail.com> Tue, 10 November 2020 12:38 UTC

Return-Path: <stewart.bryant@gmail.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 891B63A0D37; Tue, 10 Nov 2020 04:38:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=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 (2048-bit key) header.d=gmail.com
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 XZNo0pph7tzL; Tue, 10 Nov 2020 04:38:47 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A85413A0D2B; Tue, 10 Nov 2020 04:38:46 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id 19so1307131wmf.1; Tue, 10 Nov 2020 04:38:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4ZWaBoQTFIHRu1XwltOCrHf7OpzdvO6vXQeVCmSo4dU=; b=lzYLJqystKloWNfeQccOKYha+I7d1t7GziC/WWjXjgZcJPfvHkZlv+NRDQYYBN/Alj uq99iJEzBgZXN+4HaQvXYS3OL7WGVCCgxs3VdAa5RaeKKVljD3SBddtFlxkxlwObcfW6 d1VrgerBDNDRcCGk0T7WjKM6CJUMwshZHjABYR6ozpSbuqiYGOq9il5Z5aMDcrj7LaH9 JwlobhaKHMHA8PjKc+MtGHtp9PJjS/HQbxjVIfaiX5CPt7dBKV23DBp8Qe6Bln9bQxM9 EUtX2u0zAsQhPyYVNXnwt5SOnt436CjgBrhZiqApEqE+GzuSXnw6GkDAQ8iM/guQs2hG Z5LQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4ZWaBoQTFIHRu1XwltOCrHf7OpzdvO6vXQeVCmSo4dU=; b=d3g4Gl8YZYXK4zNBvp/oE6vp5BIypHTDzR6YRdpksPDrgxXDjlXV43ZpaWRlZXZgCb EyqqHmfiuqDpnpwKmkEATCQTxO2oTNxx4WN0OPC1A/K5Clh0Q1+0gnT+DY7v1IjXlNho 5Gi80Z+9b8sWADxF6lJ2ZLudtTmjER3mjM5rJ6JgOD0Q6BWvc4y3xMrvOrPE+PAAzdfF JnIfji2EAVu1HPmG3wVfvd4BrDwgmwPKEWfBligCMr5m2uNtv5TeN860PZ/1DZaHc+J2 yYSCUOu+hnNeGQjEZ6CqZ92MDjQ/am+n49WA1sxRh6GO1kX6SI+W5cOsYhEqs6z+YTCI 3e6Q==
X-Gm-Message-State: AOAM531aTCCASthpegn3yKVLUBKHt3sZLY9Dw4+l5p3fN8YH+VoYD54C y8beNaSf3ILhOJFSweh+MJc=
X-Google-Smtp-Source: ABdhPJxerWAfc4qETEXoR+nb4BReAROXoQ3SUuhYkjQsUi4isUW+cglyPBflJ3ukFYRvIH5U2shWgw==
X-Received: by 2002:a1c:7213:: with SMTP id n19mr4473210wmc.36.1605011925071; Tue, 10 Nov 2020 04:38:45 -0800 (PST)
Received: from broadband.bt.com ([2a00:23c5:3395:c901:5d:4ef6:5a48:470]) by smtp.gmail.com with ESMTPSA id t5sm2835810wmg.19.2020.11.10.04.38.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Nov 2020 04:38:44 -0800 (PST)
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: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <9D07ED68-DBF8-4E9D-966A-D7688A384E69@sobco.com>
Date: Tue, 10 Nov 2020 12:38:43 +0000
Cc: Stewart Bryant <stewart.bryant@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, iesg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <43850995-9E9A-42E4-837B-12B1EB7AF95F@gmail.com>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <9D07ED68-DBF8-4E9D-966A-D7688A384E69@sobco.com>
To: "Scott O. Bradner" <sob@sobco.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QryR4cQbSCooGL4TDMUp86bUcIM>
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 12:38:49 -0000

+1

Stewart

> On 10 Nov 2020, at 11:55, Scott O. Bradner <sob@sobco.com> 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)
>> 
>

v2.23.0 | Report a Bug | By Email