RFC 8160 on IUTF8 Terminal Mode in Secure Shell (SSH)

rfc-editor@rfc-editor.org Thu, 20 April 2017 05:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B02B712EAFC for <ietf-announce@ietfa.amsl.com>; Wed, 19 Apr 2017 22:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1EgqjHkX5WXF for <ietf-announce@ietfa.amsl.com>; Wed, 19 Apr 2017 22:56:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C5B9128DF3 for <ietf-announce@ietf.org>; Wed, 19 Apr 2017 22:56:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 52FFFB81126; Wed, 19 Apr 2017 22:56:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8160 on IUTF8 Terminal Mode in Secure Shell (SSH)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170420055639.52FFFB81126@rfc-editor.org>
Date: Wed, 19 Apr 2017 22:56:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/gK4zh73yhvspV9l1vPqsWCd3EQc>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 05:56:56 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8160

        Title:      IUTF8 Terminal Mode in Secure 
                    Shell (SSH) 
        Author:     S. Tatham, 
                    D. Tucker
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2017
        Mailbox:    anakin@pobox.com, 
                    dtucker@openssh.com
        Pages:      4
        Characters: 6961
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-sgtatham-secsh-iutf8-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8160

        DOI:        10.17487/RFC8160

This document specifies 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 UTF-8
character encoding.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC