Re: Call for Community Feedback: Retiring IETF FTP Service

Robert Moskowitz <rgm-ietf@htt-consult.com> Tue, 17 November 2020 04:40 UTC

Return-Path: <rgm-ietf@htt-consult.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 C7EEA3A0C97 for <ietf@ietfa.amsl.com>; Mon, 16 Nov 2020 20:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 GCBQ4-lBHfTl for <ietf@ietfa.amsl.com>; Mon, 16 Nov 2020 20:40:49 -0800 (PST)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 DDC213A0C8E for <ietf@ietf.org>; Mon, 16 Nov 2020 20:40:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 1806B62653; Mon, 16 Nov 2020 23:40:48 -0500 (EST)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZTWbi1EWaTjj; Mon, 16 Nov 2020 23:40:41 -0500 (EST)
Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 885B2625F7; Mon, 16 Nov 2020 23:40:39 -0500 (EST)
Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
To: Roman Danyliw <rdd@cert.org>, "ietf@ietf.org" <ietf@ietf.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org>
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Message-ID: <b3d00d59-6bc9-dad1-dda1-4ba4b7bfcb02@htt-consult.com>
Date: Mon, 16 Nov 2020 23:40:23 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <af6ab231024c478bbd28bbec0f9c69c9@cert.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rtB8VINZpT8M94pUFjVjKgaDegY>
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, 17 Nov 2020 04:40:52 -0000

I use rsync to replicate rfcs and internet drafts locally.  These are 
run via crontab every night:

1 3 * * * rsync -tvz ftp.rfc-editor.org::rfcs/*.txt /home/common/ietf/rfcs
1 4 * * * rsync -tvz rsync.tools.ietf.org::tools.id/*.txt 
/home/common/ietf/drafts

Note that for drafts, I found the rsync.tools.ieft.org fqdn, but for 
rfcs I am still? using ftp.rfc-editor.org.

perhaps something like:

1 3 * * * rsync -tvz rsync.tools.ietf.org::tools.rfcs/rfc*.txt 
/home/common/ietf/rfcs

should work?

I would be happy to shift to whatever makes best sense for the 
maintainers of the repositories.

BTW, I like the local copies.  Many times on airplanes (not so common 
right now!), I needed something and there it was...



On 11/9/20 9:23 PM, Roman Danyliw 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)
>