Re: Call for Community Feedback: Retiring IETF FTP Service

[Joseph Salowey <[e-mail]>]

While I too have many fond memories of FTP, I agree that it is best not to
continue to support a service that is little used where there are viable
and widely available alternatives.  The time and resources used to support
this service are better used somewhere else.

Cheers,

Joe

On Tue, Nov 24, 2020 at 5:12 PM Peter Yee <[e-mail]> wrote:

> I'm in favor of turning off the FTP service. It's time has come and gone.
> As
> someone who has worked on an FTP RFC, I appreciate the protocol's place in
> history. That does not mean the IETF needs to continue to support a service
> that is both redundant and little used. It should be relegated to
> retirement
> and many fond (and not so fond) memories.
>
>                 -Peter
>
> -----Original Message-----
> From: ietf [mailto:[e-mail]] On Behalf Of Roman Danyliw
> Sent: Friday, November 20, 2020 3:32 AM
> To: [e-mail]
> Subject: RE: Call for Community Feedback: Retiring IETF FTP Service
>
> 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: '[e-mail]' <[e-mail]>
> > 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)
>
>
>