Ftp-WG: Re: UTF-8 pathnames: pathname nature & length

Why don't you read the rationale in the BCP-form I-D?

Or are you suggesting that I need to copy into the UTF-8 I-D the five or six
pages it takes over there to present the rationale?

You seem to be stuck on the wrong side of the server-Telnet implementation.

The command-line editing we're talking about isn't the Telnet editing.
Those are also allowed (and, actually, cannot be disallowed by the FTP), but
they're IAC-escaped so they're not an issue for the FTP language.  The
server-FTP will never see them, and never know they occurred.

The problem is the server-FTP .. specifically the server-PI .. is what RFC
959 is allowing to do command-line editing (remember, RFC 959 was written
before RFC 2640 so it does not know about the security-enhancement layer
which lies between the PI and the Telnet).

The ASCII DEL example I use is because that is a common implementation of
that character's special function on hosts.  I like it because it is common.
I also like it because it makes such a nice bump in the road from %x20 to
%xFF.