IUTF8 Terminal Mode in Secure Shell (SSH)
draft-sgtatham-secsh-iutf8-06

[Ballot comment]
I'm not sure if you really need to update RFC4254, given that you basically only want to add a value to a registry. Having a registry seems like an indication that you don't need to update.

[Ballot comment]
This is a fine document, but I have a small suggestion for your consideration:

Security considerations of RFC 3629 seem relevant, so it would be good to see a reference to them.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-sgtatham-secsh-iutf8-05.txt. If any part of this review is inaccurate, please let us know.

The IANA Services Operator understands that, upon approval of this document, there is a single action which we must complete.

In the Pseudo-Terminal Encoded Terminal Modes subregistry of the Secure Shell (SSH) Protocol Parameters registry located at:

https://www.iana.org/assignments/ssh-parameters/

a single new terminal mode will be registered as follows:

Opcode: [ TBD-at-registration ]
Argument: IUTF8
Description: Terminal input and output is assumed to be encoded in UTF-8.
Reference: [ RFC-to-be ]
Note:

The IANA Services Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

Thank you,

Sabrina Tanamal
IANA Services Specialist
PTI

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: draft-sgtatham-secsh-iutf8@ietf.org, Kathleen.Moriarty.ietf@gmail.com, daniel.migault@ericsson.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (IUTF8 Terminal Mode in Secure Shell (SSH)) to Proposed Standard


The IESG has received a request from an individual submitter to consider
the following document:
- 'IUTF8 Terminal Mode in Secure Shell (SSH)'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-02-27. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document updates RFC 4254 by specifying a new opcode in the
  Secure Shell terminal modes encoding.  The new opcode describes the
  widely used IUTF8 terminal mode bit, which indicates that terminal I/
  O uses the UTF-8 character encoding.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-sgtatham-secsh-iutf8/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-sgtatham-secsh-iutf8/ballot/


No IPR declarations have been submitted directly on this I-D.