Re: Secure Shell WG: what's left?

[der Mouse <mouse%Rodents.Montreal.QC.CA@localhost>]

>> draft-ietf-secsh-filexfer-09
>> 	what can I say but *sigh*.
>> 	the complexity of this draft seems to be increasing,
>> 	due largely to differences in philosophy between posix/unix and
>> 	not-posix/unix filesystems.
> I prefer to think of this as adding functionality needed for
> interoperability that was ignored in earlier versions of this draft.

...but in the process making it impossible for a moderately large class
of systems to support more than ASCII under the protocol as specified
at all.  (Strictly, they can't support even that much, but can probably
get away with pretending.)

Not that this is unique to filexfer-09; the core drafts suffer from the
same problem.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse%rodents.montreal.qc.ca@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B