IETF Logo Mail Archive

Re: Call for Community Feedback: Retiring IETF FTP Service

Tim Chown <tjc.ietf@gmail.com> Wed, 02 December 2020 13:55 UTC

Return-Path: <tjc.ietf@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 527363A1403; Wed, 2 Dec 2020 05:55:53 -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 CYFAVW5TX06i; Wed, 2 Dec 2020 05:55:49 -0800 (PST)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (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 CAA5A3A13FF; Wed, 2 Dec 2020 05:55:48 -0800 (PST)
Received: by mail-wr1-x430.google.com with SMTP id 23so4023596wrc.8; Wed, 02 Dec 2020 05:55:48 -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=D2Zav72vYEZWg66X8XfZithnuKG+UjwmDTwDIjIjYN0=; b=IUTyqO/bCQDvKYM34dPrDMoPQX4Vt2ABNfge2XCs2/fk7ECQuPvoWKlJTZNReOkxhM 4k/IKlQoamB4xUUYQ1xkCryclmXIjOtucURCJADyxVtFXCpB2RJdasEIUHzwHd5aTCHr G11K4tP+cQvkGhSIR42ea4zGIU3J231XV7K+OZH+qV5+2QvcxpBV1sEEDLFw+GEmSdBL C9EopW3N8VtBo8rwwyLGDurKhMB/5z4i5zBKqq6iok7U50N/3JyEr9BGySp0XgJUk0wy q9dCFN2BYO0zZTljQFcXXIY5Xki3FJ/i6wfB/SMX+iNKqw1zkEC1nXnPl1JtuwdUALDw PhUA==
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=D2Zav72vYEZWg66X8XfZithnuKG+UjwmDTwDIjIjYN0=; b=H5mZpN8xvGhlO1Z5gdlvJ3bscajWiUUI2paWIQ4pVWOth0KtTD7sbFEx5FiGl1xhfi kASIwyVXEk9LulAyaACxYIgXIBETwBn8JFV4ZDzCpvZV57p7reOMhMdz3yCHGZv/IHrO 3qD0eBTi8K1Hi/Ywa/Frwu4SXZoqPnur43m/3v9rtu+UnoAeqyJVDiMTyVNcnMjTswaF lEfK0UO/9UX5tENqCQFfYuZd4aOdk1Z2VCvOlGA8oX/4C4DfvHSAgfmfS2FEz7V4F3jD zIjPE3XKpen/oCQkufzd+LJ8rwV82vlt5R6PoMIP5Pz8lzDu6LQaIe5KaN3ePTLufB2m 922Q==
X-Gm-Message-State: AOAM532E1aOtd2uEmyS/82dwXtQNFIK89KFPOIamQ9sMA+tdjkiRz+jK Dn1M5v0b6wR3I13p9zhm88Q=
X-Google-Smtp-Source: ABdhPJxG4sItJVm/kYNzwkRYl/ggk7Eo0xK5h1BvIV+Z+HMMEbUosRJqYceQVcBMXGiYpgOuKF6hCw==
X-Received: by 2002:a5d:56cb:: with SMTP id m11mr3657639wrw.346.1606917347332; Wed, 02 Dec 2020 05:55:47 -0800 (PST)
Received: from [192.168.0.21] (tchowndsl.claranet.co.uk. [212.188.254.49]) by smtp.gmail.com with ESMTPSA id h20sm2124946wmb.29.2020.12.02.05.55.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 Dec 2020 05:55:46 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
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: Tim Chown <tjc.ietf@gmail.com>
In-Reply-To: <43850995-9E9A-42E4-837B-12B1EB7AF95F@gmail.com>
Date: Wed, 02 Dec 2020 13:55:45 +0000
Cc: "Scott O. Bradner" <sob@sobco.com>, "ietf@ietf.org" <ietf@ietf.org>, iesg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <92BC9726-7635-424D-AA31-467AAB330EC6@gmail.com>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <9D07ED68-DBF8-4E9D-966A-D7688A384E69@sobco.com> <43850995-9E9A-42E4-837B-12B1EB7AF95F@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vCEYbgqCQdpE0tPYTmn8JkXuJw0>
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: Wed, 02 Dec 2020 13:55:53 -0000

And for what it’s worth, another +1.

Tim 

> On 10 Nov 2020, at 12:38, Stewart Bryant <stewart.bryant@gmail.com> wrote:
> 
> +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