Re: [ftpext] FWD: ftp/959 reboot

[Anthony Bryan <[e-mail]>]

On Sat, Aug 21, 2010 at 5:00 AM, Iljitsch van Beijnum
<[e-mail]> wrote:
> On 9 aug 2010, at 21:17, Anthony Bryan wrote:
>
>> the idea would be to have an updated, coherent, harmonious document of
>> RFCs concerning FTP along
>> with implementation and real world info like httpbis.
>
> I don't think simple reorganization and clarification will do it for FTP. There is a ton of stuff in the current specs that is no longer used at all (all the fancy file/record organization stuff), stuff that is technically legal but doesn't make sense (PASV+PORT), stuff that is technically legal but isn't used in practice and using it in practice would cause big problems (PASV with a different address in the 227 than the control channel address, EPSV with an argument), stuff that should work but has issues in practice (EPSV), stuff that should have been retired a decade ago but is still in wide use (PASV+PORT) and so on.
>
> I don't think revisiting the FTP spec without tightening the spec and deprecating some currently legal options makes much sense. Yes, it's annoying to have to read so many documents to create an FTP server or client, but the real problem isn't the number of documents, but that what's in those documents and what FTP servers and clients do in practice is so different from what's in those documents. In that sense an effort like RFC 1771 -> RFC 4271 where the focus was to document what's really out there seems to make sense.

yep that's what I'm proposing, but there doesn't seem to be enough
interested people.

I posted the httpbis charter here earlier, but I think it's worth reading
http://datatracker.ietf.org/wg/httpbis/charter/

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads