Last Call: <draft-sgtatham-secsh-iutf8-05.txt> (IUTF8 Terminal Mode in Secure Shell (SSH)) to Proposed Standard

The IESG <> Mon, 30 January 2017 16:31 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 34DC012948C; Mon, 30 Jan 2017 08:31:21 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-sgtatham-secsh-iutf8-05.txt> (IUTF8 Terminal Mode in Secure Shell (SSH)) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
Message-ID: <>
Date: Mon, 30 Jan 2017 08:31:21 -0800
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 30 Jan 2017 16:31:21 -0000

The IESG has received a request from an individual submitter to consider
the following document:
- 'IUTF8 Terminal Mode in Secure Shell (SSH)'
  <draft-sgtatham-secsh-iutf8-05.txt> 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 mailing lists by 2017-02-27. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   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

IESG discussion can be tracked via

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