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

> But there seems to be a bootstrap problem: SSH implementors will not
> implement the feature unless it is normalized (see <URL:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=337041 >),

Er, no.  One particular set of SSH implementors, perhaps.  moussh has
supported IUTF8 (as far as I can tell - I don't run anything that has
the bit, making it difficult for me to test) since shortly after I
first saw the issue mentioned.  (Supported it using the same extension
I use to support ECHOPRT and other bits not in the ssh RFCs, but
still.)

I don't know if any other implementations have.

> and the feature cannot be normalized until there is consensus on its
> implementation.  How does one break this deadlock?

Given what it is, in this case, I think the right way is to spec the
bit even in the absence of any ssh implementations actually using it.
(Not that I have any particular authority to do so.)  But, on the other
hand, if "tty drivers have this bit" were reason enough, they
wouldn't've left out the bits that prompted me to create the extension
I mentioned above.

/~\ 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