[ftpext] draft-ietf-ftpext2-typeu is now draft-klensin-ftpext-typeu

[John C Klensin <[e-mail]>]

Hi,

Per Tony's "WG Status" note of about an hour ago, I've reissued
the "TYPE U" draft with the name draft-klensin-ftpext-typeu.

This is identical to draft-ietf-ftpext2-typeu except for
	* The file name
	* The date
	* A revised description of the mailing list on which the
	    draft is being discussed
	* Removal of the name of the FTPEXT2 Working Group
	* A new change log section that provides a backtrace.
	
Quid Pro Quo offer: I'll review yours if you will either review
or implement mine :-).

Note that a valid minimal implementation of this extension for
systems that use Unicode internally and already support
conversion of whatever encoding is used internally to and from
UTF-8 for on the wire use consists of:

	* Advertising the extension if one is a server and
	     receives a FEAT command.
	* Sending the extended TYPE request if one is a client
	* Ensuring that lines end with CRLF if one is a sender
	(note that the relevant code for this purpose is in any
	implementation that supports TYPE A).
	
One should also normalize to NFC, but that is not required (the
spec deliberately says "SHOULD...if at all possible", not MUST).

Note also that any data stream that is valid for TYPE A is also
value for TYPE U.

Systems that do not support Unicode natively would have to do
some potentially-significant conversions to support this
command; they are not candidates for a trivial implementation
unless appropriate tools already exist or are easily adapted.

  best,
    john