Bug#337041: IUTF8 pseudo-terminal mode
On Mon, 2013-02-04 at 16:02 +0100, Vincent Lefevre wrote:
> On 2005-12-31 16:05:59 +0000, Colin Watson wrote:
> > Recent versions of the Linux kernel support an IUTF8 flag (see
> > http://www.cl.cam.ac.uk/~mgk25/unicode.html#mod) which allows the
> > character-erase function in cooked mode to handle UTF-8 characters
> > correctly. I would like to allow this mode to be preserved by SSH, but
> > there is no assignment for it at present.
> >
> > Could this line be added to the appropriate place in
> > draft-ietf-secsh-connect and draft-ietf-secsh-assignednumbers to create
> > this assignment? 42 seems like a reasonable place for it.
> >
> > 42 IUTF8 Assume input characters are UTF-8 encoded.
> >
> > Thanks,
>
> The problem is still there in the Debian packages from openssh 6.0p1-3.
Yes, I'm sure it is. The requested number was not added to the draft,
because it was too late to do so before publication. A few days later,
Bill Sommerfeld, who was WG chair at the time, posted the following:
> So what needs to happen to get this standardized is for someone to write
> an internet-draft documenting this extension and advance it as either a
> working group item or as an individual submission.
That remains the case today. The registration policy for that registry
is "IETF Consensus", which means that getting a new number assigned
requires publishing an RFC. For this sort of thing, that could happen
relatively quickly, once someone writes an internet-draft.
-- Jeff
Reply to: