Having a service online that no-one uses becomes a liability in terms of
security, even it it´s one of those things that 'just works' without
anyone even looking at it.
Don't say you haven't seen things like servers with multi-year uptimes
and whose sysadmin no one knows, I won't believe you :-)
So yes, I agree with the position that FTP support should be phased out.
Cheers!
-Carlos
On 4/6/15 1:14 PM, Michael StJohns wrote:
At 01:31 PM 4/3/2015, IETF Administrative Director wrote:
All;
The Technology Management Committee of the IAOC is considering
recommending to the IAOC ending support for FTP to retrieve files
from the IETF servers and would like to hear from the community
before the IAOC taking its decision. This does not include
rfc-editor.org.
The use of FTP to retrieve files from the IETF servers has been
declining steadily.
Hi Ray -
What is the cost of leaving FTP service in place? I would expect that the
cost was more in setting up FTP in the first place (e.g. adding it to
template emails, configuring the servers) than any real day to day cost, but
I could be wrong.
What is the cost of removing it? (e.g. besides simply shutting off the
servers, what else has to be done, who has to do it and what will it cost?).
Is there an impact on the IETF budget either way short term? Long term?
Thanks - Mike
The files made available with that protocol are also available using
http and rsync. (See the modules exposed at rsync.ietf.org using
"rsync rsync.ietf.org::")
The majority of the current FTP traffic appears to be from mirror
sites that would be better served using rsync.
Input received by 20 April will inform the decision.
Thanks
Ray