Re: Call for Community Feedback: Retiring IETF FTP Service

[Martin Duke <[e-mail]>]

 So I'm hearing that the people actually running the FTP service believe it
to be a significant nuisance, and some subset of the community think that
it is obviously trivial. Would it be too much to ask one of the FTP
enthusiasts to volunteer to maintain it, so that those who have tired of it
can move to other things?

I'm sure we can migrate it to a URL that makes it clear it is
volunteer-driven.

On Wed, Nov 11, 2020 at 11:09 PM Loa Andersson <[e-mail]> wrote:

> All,
>
> That was my thought also, if we claim "operational complexity" we should
> maybe try to be explicit.
>
> /Loa
>
> On 10/11/2020 19:55, Scott O. Bradner wrote:
> > is there a compelling reason to stop a service that some people are using
> >
> > the pdf says : "The operational complexity of running this service "
> >
> > just what complexity is there once the service was set up (years ago)?
> >
> > i.e., just how much does this service cost to run?
> >       (seems to me that it is likely that the effort to develop this
> plan was much more than just letting the service run)
> >
> > yes, I run one of the scripts that use ftp to access IETF resources and
> it would be a significant pain to rewrite it
> > since it is complicated script and I do not know how to do some of its
> functions in other non-ftp ways
> >
> > I do seriously want to know how much it costs the IETF to run the ftp
> service
> >
> > Scott
> >
> >
> >
> >> On Nov 9, 2020, at 9:23 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)
> >>
> >
>
> --
>
> Loa Andersson                        email: [e-mail]
> Senior MPLS Expert                          [e-mail]
> Bronze Dragon Consulting             phone: [phone]
>
>