IETF Logo Mail Archive

RE: Call for Community Feedback: Retiring IETF FTP Service

Roman Danyliw <rdd@cert.org> Fri, 20 November 2020 11:32 UTC

Return-Path: <rdd@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 1741C3A1C45 for <ietf@ietfa.amsl.com>; Fri, 20 Nov 2020 03:32:09 -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 gcBtiBKcR7mK for <ietf@ietfa.amsl.com>; Fri, 20 Nov 2020 03:32:07 -0800 (PST)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (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 53ED83A1C46 for <ietf@ietf.org>; Fri, 20 Nov 2020 03:32:06 -0800 (PST)
Received: from delp.sei.cmu.edu (delp.sei.cmu.edu [10.64.21.31]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AKBW5eE029178 for <ietf@ietf.org>; Fri, 20 Nov 2020 06:32:05 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 0AKBW5eE029178
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1605871925; bh=i4I9527tDXCI6iyB3eLQwnCg/XWoqUUhjqK8SznciKI=; h=From:To:Subject:Date:References:In-Reply-To:From; b=C8673kR154WXJMzNUqqvvsr1NXaJzB0mdZ0Zm8POH691vh6Blfg4wMFplJcsMPT7F pWyiw9sA2c+vH7hBW3NxEDWP7QHQHIqULR1/zrpJGCAwcY7MqBTBQE099PeeTiXklR 8yfkpGFQDd5HaTWOXsSJFZQf0uBuYynLmywHNJ9g=
Received: from MURIEL.ad.sei.cmu.edu (muriel.ad.sei.cmu.edu [147.72.252.47]) by delp.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AKBVxEt029185 for <ietf@ietf.org>; Fri, 20 Nov 2020 06:32:00 -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 06:31:59 -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 06:31:59 -0500
From: Roman Danyliw <rdd@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: Ada3CD1BnAYFDyoMT8WUdvX4VBiWMQIJ4c7A
Date: Fri, 20 Nov 2020 11:31:58 +0000
Message-ID: <b993def4eb0140698042781e0b790af0@cert.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org>
In-Reply-To: <af6ab231024c478bbd28bbec0f9c69c9@cert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.202.48]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QjZYk5Yu_sDcZWthNNgv1F5qICI>
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 11:32:09 -0000

Hi!

We are about half through the feedback period and helpful discussion has already occurred.  Thank you for the input.  

To help focus further discussion and to help onboard those that have not weighed in yet, a summary of the thread to date can be found at https://github.com/ietf/ftp-retirement-consult-2020/blob/main/status.md

Regards,
Roman

> -----Original Message-----
> From: Roman Danyliw
> Sent: Monday, November 9, 2020 9:24 PM
> To: 'ietf@ietf.org' <ietf@ietf.org>
> Subject: Call for Community Feedback: Retiring IETF FTP Service
> 
> 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