Re: adding IUTF8 to encoded terminal modes in SSH Protocol Assigned Numbers

>> I've seen (relatively) numerous embedded devices that claim to speak
>> ssh, including using port 22, but actually speak a closely related
>> protocol in which the private-part@domain extensibility mechanism
>> does not work the way it does in ssh.  [...]
> <sigh>  What's supposed to happen here is that you match on the
> server version, turn off the features that cause it to break, and
> then stop buying from that vendor until they fix their stuff.  :-)

Yeah.  And, if I had control over the relevant buying decisions, that
might actually happen.

> Unfortunately, for that to be effective, you usually have to be large
> and/or numerous.

That too. :(  Name-and-shame occasionally works, too; if I could recall
which devices they were, I'd name them here.

>> The IETF, IANA, [etc] have no ability [] to prevent you, me, or
>> anyone else from running not-quite-ssh software such as [...]
> True, and this is as it should be.

Agreed.

>> [...] ssh as specified is basically unimplementable on many [...]
> Perhaps you'd care to elaborate (maybe in a new thread) ?

Absolutely.  I'll reply to just this part and change the Subject:.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		[email protected]
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B