Re: Reference for UTF8 in SSH UTF8 terminal mode
Mouse <mouse@Rodents-Montreal.ORG> Sun, 11 December 2016 06:49 UTC
Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42B4C12957F for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sat, 10 Dec 2016 22:49:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, 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 ZxR9AJ4CIQsH for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Sat, 10 Dec 2016 22:49:01 -0800 (PST)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:470:a085:999::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF30312956C for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Sat, 10 Dec 2016 22:49:01 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id F27F78556E; Sun, 11 Dec 2016 06:49:00 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: by mail.netbsd.org (Postfix, from userid 1347) id AE54984CEF; Sun, 11 Dec 2016 06:49:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 05D2F85590 for <ietf-ssh@NetBSD.org>; Sat, 10 Dec 2016 12:59:30 +0000 (UTC)
X-Virus-Scanned: amavisd-new at netbsd.org
Received: from mail.netbsd.org ([IPv6:::1]) by localhost (mail.netbsd.org [IPv6:::1]) (amavisd-new, port 10025) with ESMTP id UkAWltjkwoBk for <ietf-ssh@netbsd.org>; Sat, 10 Dec 2016 12:59:29 +0000 (UTC)
Received: from Stone.Rodents-Montreal.ORG (Stone.Rodents-Montreal.ORG [98.124.61.89]) by mail.netbsd.org (Postfix) with ESMTP id 0AFFA84CE5 for <ietf-ssh@NetBSD.org>; Sat, 10 Dec 2016 12:59:28 +0000 (UTC)
Received: (from mouse@localhost) by Stone.Rodents-Montreal.ORG (8.8.8/8.8.8) id HAA17917; Sat, 10 Dec 2016 07:59:28 -0500 (EST)
Date: Sat, 10 Dec 2016 07:59:28 -0500
From: Mouse <mouse@Rodents-Montreal.ORG>
Message-Id: <201612101259.HAA17917@Stone.Rodents-Montreal.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
X-Message-Flag: Microsoft: the company who gave us the botnet zombies.
X-Composition-Start-Date: Sat, 10 Dec 2016 07:43:22 -0500 (EST)
To: ietf-ssh@NetBSD.org
Subject: Re: Reference for UTF8 in SSH UTF8 terminal mode
In-Reply-To: <2DD56D786E600F45AC6BDE7DA4E8A8C117FE79EF@eusaamb107.ericsson.se>
References: <2DD56D786E600F45AC6BDE7DA4E8A8C117FE79EF@eusaamb107.ericsson.se>
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list
> We are looking at which reference to UTF8 we should mention into the > SSH UTF8 terminal mode. > [some Web URL] mentions that RFC3629 is slightly out of date and that > a reference to ISO/IEC 10646:2014 may also be useful. > Is anyone aware of any deficiencies in RFC3629 fixed in ISO/IEC > 10646:2014 ? > The question is whether we should have one reference or both in the > draft. Unless RFC 3629 has some deficiencies fixed in ISO/IEC > 10646:2014, I am incline to have only RFC3629. Is that something that > sounds reasonable to everyone ? My opinion - probably worth about what you paid for it - is that the RFC is a much better reference. This is for entirely non-technical reasons. The ISO believes pay-to-play is reasonable for standards, and, while 10646:2014 seems to be one they make an exception for, (a) getting it requires a _lot_ more hoop-jumping than an RFCs, (b) getting it requires agreeing to what for most of the world is foreign legal jurisdiction, (c) they say what you'd get is a "single-user, non-revisable Adobe Acrobat® PDF file", which means either it's DRMed or they're stupid enough to think no other PDF-handling software than Adobe's exists (I don't know which; between the jurisdictional issue, the difficulty of jumping through their hoops, and my lack of any real need for it, I haven't fetched it), and (d) their copyright terms are ridiculously onerous for something supposedly "freely available" - for example, you are prohibited from storing it on a filesystem that gets backed up, and you are permitted only one printed copy. > This Communication is Confidential. Then you might want to avoid sending it to a public, publicly archived, mailing list. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mouse@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
- Reference for UTF8 in SSH UTF8 terminal mode Daniel Migault
- Re: Reference for UTF8 in SSH UTF8 terminal mode Mark D. Baushke
- Re: Reference for UTF8 in SSH UTF8 terminal mode Mouse
- Re: Reference for UTF8 in SSH UTF8 terminal mode Ron Frederick
- RE: Reference for UTF8 in SSH UTF8 terminal mode Daniel Migault
- Re: Reference for UTF8 in SSH UTF8 terminal mode Ron Frederick
- RE: Reference for UTF8 in SSH UTF8 terminal mode Daniel Migault
- Re: Reference for UTF8 in SSH UTF8 terminal mode Mark Baushke
- Re: Reference for UTF8 in SSH UTF8 terminal mode Ron Frederick
- Re: Reference for UTF8 in SSH UTF8 terminal mode Daniel Migault