Keith Moore wrote:
As far as I know, there are now precisely
zero supported browsers that handle the ftp: schema.
So, the proper response of IETF was to let browser developping
community maybe including W3C not to obsolete ftp:.
Given evidences initiated this thread, I think IETF still should
do so as a (former) operator of the FTP service.
The real problem, IMO, is that the environment expected by web pages has
been allowed to become so complex, that producing a completely
independent general-purpose web browser is now cost-prohibitive for all
but the largest tech giants, and the number of truly independent
implementations is increasingly close to 1. And that has allowed a
> very small number of companies to effectively control what people can
> do with their computers "for their own good".
Given that IETF was, and still is at or below transport layer, the
only entity to develop standard internet protocols, that is not
a problem.
IETF should not force implementers to or not to deploy some
standards.
Similarly, browser developers or the browser developer should
not force operators or end users to deploy or not to deploy
some standards.
Arguably this is partially a failure on IETF's part. But IETF never
has controlled HTML, JavaScript, and other aspects of the browser
environment, so the fault isn't totally ours.
We are talking about FTP.
Of course the problem is far worse than the refusal of modern browsers
to support FTP.
I'm afraid the arrogant refusal by browser developers is too bad.
Masataka Ohta
