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

Mouse <mouse@Rodents-Montreal.ORG> Fri, 29 March 2013 13:31 UTC

Date: Fri, 29 Mar 2013 09:31:37 -0400
From: Mouse <mouse@Rodents-Montreal.ORG>
Message-Id: <201303291331.JAA24710@Sparkle.Rodents-Montreal.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
To: ietf-ssh@NetBSD.org
Subject: Re: adding IUTF8 to encoded terminal modes in SSH Protocol Assigned Numbers
In-Reply-To: <20130329125734.GA24915@achernar.madore.org>
References: <20130329125734.GA24915@achernar.madore.org>
Sender: ietf-ssh-owner@NetBSD.org
Precedence: list

> 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		mouse@rodents-montreal.org
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

adding IUTF8 to encoded terminal modes in SSH Pro… David Madore
Re: adding IUTF8 to encoded terminal modes in SSH… Mouse
Re: adding IUTF8 to encoded terminal modes in SSH… Niels Möller
Re: adding IUTF8 to encoded terminal modes in SSH… David Madore
Re: adding IUTF8 to encoded terminal modes in SSH… Chris Lonvick
Re: adding IUTF8 to encoded terminal modes in SSH… Mouse
Re: adding IUTF8 to encoded terminal modes in SSH… Stephen Farrell
Re: adding IUTF8 to encoded terminal modes in SSH… Jeffrey Hutzelman
Re: adding IUTF8 to encoded terminal modes in SSH… Mouse
Re: adding IUTF8 to encoded terminal modes in SSH… Jeffrey Hutzelman
Re: adding IUTF8 to encoded terminal modes in SSH… Mouse
Unimplementability [was Re: adding IUTF8 to encod… Mouse
Re: Unimplementability [was Re: adding IUTF8 to e… Niels Möller
Re: Unimplementability [was Re: adding IUTF8 to e… Mouse
Re: Unimplementability [was Re: adding IUTF8 to e… Albert Lunde
Re: Unimplementability [was Re: adding IUTF8 to e… Niels Möller
Re: Unimplementability [was Re: adding IUTF8 to e… Mouse
Re: adding IUTF8 to encoded terminal modes in SSH… Darren Tucker
Re: adding IUTF8 to encoded terminal modes in SSH… David Madore
Re: adding IUTF8 to encoded terminal modes in SSH… Mouse