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)
