Ftp-WG: mlst-16 will correctly say *( %x20-7E )?

Despite time & study, I'm not sure I'm correctly
understanding the English posted here 17-22 July ...
so I'll post these guesses, and hope for correction?

> From: Gregory A Lundberg [[email protected]]
> you cannot send ( %x00-1F / %x7F ) on ANY FTP
> command or reply and expect correct interoperation.

Yes.

>
http://www.ietf.org/internet-drafts/draft-ietf-ftpext-utf-8-option-00.txt
> ...
> The ABNF for pathnames presented in [RFC2640] is
> incorrect.  When UTF-8 encoding is not present,
> the correct syntax is PATHNAME = *( %x20-7E )...

Yes, except where we say "when UTF-8 encoding is not
present" we mean to say "unless some other syntax has
been negotiated", whether that be by OPTS UTF-8 NLST
of the draft FEAT UTF-8 or the OPTS ENCODING URL of
Marc Huber or whatever.

> From: Robert Elz [[email protected]]
> I'd hate it to fall back into the "Oh, that one"
> state that it has been in for the past year or so.

Our intent is to close out the MLST effort __without__
taking the time to teach MLST to handle the path names
over which NLST LIST etc. choke.

>
http://www.ietf.org/internet-drafts/draft-ietf-ftpext-mlst-15.txt
> pathname = utf-8-name / raw

Accordingly we can hope to see this error corrected
before the final draft.

Here when we say utf-8-name's we mean only those which
do not contain ( %x00-1F / %x7F ).  Or maybe we mean
only those which do not contain ( %x00-1F / %x7F /
%x80-FF), formerly known as locally printable Ascii
names.

> > From: Pat LaVarre [[email protected]]
> > As a server, in a folder, I have a local
> > filename that includes a local Eol.
> >
> > How should that filename appear in my NLST data,
> > supposing the client asked for FEAT UTF-8 NLST?
...
> From: Gregory A Lundberg [[email protected]] ...
> It cannot appear on ANY FTP command or response.
> Sorry.

Aye, not yet, ouch.

Pat LaVarre

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com