RE: Call for Community Feedback: Retiring IETF FTP Service

[Roman Danyliw <[e-mail]>]

Hi George!

> -----Original Message-----
> From: George Michaelson <[e-mail]>
> Sent: Monday, November 9, 2020 9:38 PM
> To: Roman Danyliw <[e-mail]>
> Cc: [e-mail]
> Subject: Re: Call for Community Feedback: Retiring IETF FTP Service
> 
> What we have considered as part of our retirement option, is to ensure the
> FQDN ftp.x.y.z continues to be live, but serves HTTP(S)
> 
> This means that URLs of the form ftp://ftp.x.y.z/path/to/data map naturally to
> https://ftp.x.y.z/path/to/data

Indeed that's largely the thinking.  Additionally, the HTTP version of all of these mappings are already live (and have been for a number of years).  Currently, everything that was:

ftp://*.ietf.org is (and will continue to be) at http{s}://www.ietf.org/ietf-ftp/

Additionally,
ftp://*.ietf.org/rfc/* ==> http{s}://www.ietf.org/rfc/*
ftp://*.ietf.org/internet-drafts/ ==> http{s}://www.ietf.org/internet-drafts/*

Regards,
Roman

> We have found this was helpful to remove the hits on FTP the protocol, without
> massive impact to pURL burned into documents, or external references we
> don't control.
> 
> It also leaves a trail, to confirm who comes in (by IP) on ftp, and then who
> subsequently succeeds in fetching via HTTP(S). And, it provides for redirect-
> permanent outcome.
> 
> cheers
> 
> -George
> 
> On Tue, Nov 10, 2020 at 12:24 PM Roman Danyliw <[e-mail]> 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)
> >