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

Note: This ballot was opened for revision 05 and is now closed.

(Kathleen Moriarty; former steering group member) Yes

Yes ( for -05)
No email
send info

(Stephen Farrell; former steering group member) Yes

Yes ( for -05)
No email
send info

(Alexey Melnikov; former steering group member) No Objection

No Objection (2017-02-26 for -05)
No email
send info
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.

(Alia Atlas; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Alissa Cooper; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Ben Campbell; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Deborah Brungard; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Jari Arkko; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Joel Jaeggli; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Mirja K├╝hlewind; former steering group member) No Objection

No Objection (2017-02-27 for -05)
No email
send info
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.

(Spencer Dawkins; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Suresh Krishnan; former steering group member) No Objection

No Objection ( for -05)
No email
send info

(Terry Manderson; former steering group member) No Objection

No Objection ( for -05)
No email
send info