RE: Call for Community Feedback: Retiring IETF FTP Service

Roman Danyliw <rdd@cert.org> Tue, 17 November 2020 06:41 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 7ABFD3A1034 for <ietf@ietfa.amsl.com>; Mon, 16 Nov 2020 22:41:08 -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 PFNWe5mZmCLH for <ietf@ietfa.amsl.com>; Mon, 16 Nov 2020 22:41:06 -0800 (PST)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (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 6904F3A1033 for <ietf@ietf.org>; Mon, 16 Nov 2020 22:41:06 -0800 (PST)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AH6evVX048436; Tue, 17 Nov 2020 01:40:58 -0500
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu 0AH6evVX048436
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1605595258; bh=VKzSqBV13bFYas8XrJyYtwOzNzP3eowflm4xH0s7EY8=; h=From:To:Subject:Date:References:In-Reply-To:From; b=FI1ntmvadAwKYRv0pVvI0F4wn/D/Gy8JsjwWCrHcRWM5e9ReaIsffaZEnEk5l6ujV y25/9Ss7sqSzRSq/Kd4LwxMOWVbRrRu3+QLBTJMggFk445d1uCEG1/AHnrF5EOOQpD YtRBnZcyPUUugDd25BCRnwHBMdCq9n+aozAtONhQ=
Received: from MURIEL.ad.sei.cmu.edu (muriel.ad.sei.cmu.edu [147.72.252.47]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 0AH6euv2021992; Tue, 17 Nov 2020 01:40:56 -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; Tue, 17 Nov 2020 01:40:56 -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; Tue, 17 Nov 2020 01:40:56 -0500
From: Roman Danyliw <rdd@cert.org>
To: Robert Moskowitz <rgm-ietf@htt-consult.com>, "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: Ada3CD1BnAYFDyoMT8WUdvX4VBiWMQFvW5+AAAkw2RA=
Date: Tue, 17 Nov 2020 06:40:55 +0000
Message-ID: <baf17955f3924c1bb361e07adef2c499@cert.org>
References: <af6ab231024c478bbd28bbec0f9c69c9@cert.org> <b3d00d59-6bc9-dad1-dda1-4ba4b7bfcb02@htt-consult.com>
In-Reply-To: <b3d00d59-6bc9-dad1-dda1-4ba4b7bfcb02@htt-consult.com>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SA0IK0dPPujWMOMFvOquwstGb34>
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 06:41:09 -0000

Hi Bob!

> -----Original Message-----
> From: Robert Moskowitz <rgm-ietf@htt-consult.com>
> Sent: Monday, November 16, 2020 11:40 PM
> To: Roman Danyliw <rdd@cert.org>rg>; ietf@ietf.org
> Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
> 
> 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.

Thanks for sharing the exactly config you are using with rsync.  I see no issue with how you are syncing your files.  It's worth mentioning that there are three possible rsync servers serving different subsets of the data.  You're gets RFCs from ftp.rfc-editor.org and IDs from rsync.tools.ietf.org.  You could also get both from a single source (say rsync.ietf.org).  For those trying to find  a server closest to the ftp directory layout, the best choice is rsync.ietf.org (which also has everything-ftp, which is the entire ftp server layout).

As a PSA, this is what is found on all three servers:

$ rsync rsync.ietf.org::
everything-ftp 	- The entire IETF FTP Archive
internet-drafts	- The Internet Draft Repository (currently active drafts)
id-archive     	- The Internet Draft Archive (both active and expired drafts)
iesg-minutes   	- IESG Minutes
proceedings    	- Repository of Proceedings
xml2rfc.bibxml 	The xml2rfc citation libraries
charter        	- Repository of WG Charters
concluded-wg-ietf-mail-archive	- Older list text archives
conflict-reviews	- Repository of Conflict Review documents
iana           	- IANA assignments
iana-timezone  	- IANA Time Zone Datatbase (see also http://www.iana.org/time-zones)
legacy-files   	- Legacy material supporting long-lived URLs
mailman-archive	- Repository of Mailing List Text Archives
rfc            	- Repository of RFCs
slides         	- Repository of Slide Documents
status-changes 	- Repository of Status Change Documents

$ rsync rsync.tools.ietf.org::
tools          	The (almost) complete tools.ietf.org site.
tools.tools    	The tools collection at tools.ietf.org.
tools.html     	Currently available htmlized drafts and RFCs.
tools.html.rfc 	Currently available htmlized RFCs.
tools.pdf      	Currently available pdf conversions of drafts and RFCs.
tools.pdf.rfc  	Currently available pdf conversions of RFCs.
tools.id       	Unpurged IETF drafts repository.
tools.meeting  	Meeting materials from IETF 59 and forward
doc.history    	Document history files (html-attribute-like lines)
doc.state.attr 	Current document status in a html-attribute-like format
doc.state.822  	Current document status in a RFC822-like format
doc.state.xml  	Current document status in an xml format
doc.versions   	Document version list files
doc.meta       	All document status files
svn.group      	Group SVN repositories
xml2rfc.bibxml 	The xml2rfc citation libraries

$ rsync ftp.rfc-editor.org::
everything-ftp 	Everything FTP
refs           	XML references for RFCs (for use with xml2rfc)
rfcs           	Contents of in-notes including subdirectories std, bcp, fyi, and ien
rfcs-text-only 	Only the text files from the directories in [rfcs]
rfc-ed-all     	Entire repository (excluding internet-drafts)
internet-drafts	Internet Drafts
ids-text-only  	Only text files from the Internet Drafts mirror
rfcs-pdf-only  	PDF versions of ASCII RFCs to ensure correct page breaks, etc

Regards,
Roman


> 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)
> >