IETF Logo Mail Archive

Re: Reference for UTF8 in SSH UTF8 terminal mode

Daniel Migault <daniel.migault@ericsson.com> Tue, 13 December 2016 20:13 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 1649D1295B9 for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue, 13 Dec 2016 12:13:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.985
X-Spam-Level:
X-Spam-Status: No, score=-6.985 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com
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 YcjbltIoeMCY for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Tue, 13 Dec 2016 12:13:14 -0800 (PST)
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200]) (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 136CF129574 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Tue, 13 Dec 2016 12:13:14 -0800 (PST)
Received: by mail.netbsd.org (Postfix, from userid 605) id B5D2485574; Tue, 13 Dec 2016 20:13:11 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: by mail.netbsd.org (Postfix, from userid 1347) id 5BE6B8556E; Tue, 13 Dec 2016 20:13:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id C5AB985586 for <ietf-ssh@netbsd.org>; Tue, 13 Dec 2016 17:30:06 +0000 (UTC)
X-Virus-Scanned: amavisd-new at netbsd.org
Authentication-Results: mail.netbsd.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.netbsd.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 33_D0STCb-sp for <ietf-ssh@netbsd.org>; Tue, 13 Dec 2016 17:30:06 +0000 (UTC)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 103C285574 for <ietf-ssh@netbsd.org>; Tue, 13 Dec 2016 17:30:06 +0000 (UTC)
Received: by mail-io0-x234.google.com with SMTP id d9so235440170ioe.0 for <ietf-ssh@netbsd.org>; Tue, 13 Dec 2016 09:30:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=MIg1RS/NYy89oMZZEUUfy6IeHbvXCjIcnYjiXzUYHdc=; b=tk80y1aEU2IQu+/0ueLoBgP04XEk25MC63UfRyIWlwjHUQbWuiKR0O0lKd8ZnUWbMj DWjTxGm4CRf0PDO1+VdUyc5owDORFYYXh59QRDe0z1MVhNlVzFzEPSl2iZ/vyWfdwALf 1AAfdf90ify/KeBB6Vzl1qYXr9mi0PyPLs5ZHLr6USIdf34WB1kuEz/SenPOAatx28mm SEMDVDrSiL2so+miYS3qUXTQ/Yuecws4u/EhoJq4D7kvmQgJEGRpkTt53KlnaW4vqqVY uuu+HD6Ub3Fwfj6p2sE6QMzrTstd/Dsubhz0H+/3os9auoxlvi/SleVEjaOeJ47NUmeX Jbxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=MIg1RS/NYy89oMZZEUUfy6IeHbvXCjIcnYjiXzUYHdc=; b=RL4/UmIbS4xgYK8UmUAvsru/vDHUqxhr1sANmNVWczTu6SREs77s1a7P2ZO/xrxUa5 mqgrjuP+svBxIgBDPAiL85F6dlnJz4b7kupiigISjeewHzCYZV9V6rwdWHRbJ546l84H odTa4FGll7kiq6Ty1LfM0GXl+7WUhAR481v9riNjL4hoX8/oKwZxWghgOb37jFXEGWiX AsOhYR2rshVe/Y+79RRZ5WMCCRp3RvzqbWHAQSgsRIjvpQiWBV5pIoDQt/Q/PaBf+do+ FXLIUL08vzjB/2DKSfC08b1wx6z9Qi6J9ikkhZ1hPcZ8Or7quXJvHaEs006mAX+Ng4gc 58KQ==
X-Gm-Message-State: AKaTC02yNzcr76nIQS49on7gFUSsQd+8vWOXS6ow1Zdh2T1Xuy6LStDfg0xP5dEpEaAsNcyyonEypBUAH29I+w==
X-Received: by 10.36.29.19 with SMTP id 19mr3346148itj.101.1481650204679; Tue, 13 Dec 2016 09:30:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.59.214 with HTTP; Tue, 13 Dec 2016 09:30:04 -0800 (PST)
In-Reply-To: <E5C97FAA-EBA4-48B3-BCFB-C87C132F9345@timeheart.net>
References: <2DD56D786E600F45AC6BDE7DA4E8A8C117FE79EF@eusaamb107.ericsson.se> <201612101259.HAA17917@Stone.Rodents-Montreal.ORG> <2DD56D786E600F45AC6BDE7DA4E8A8C117FF2172@eusaamb107.ericsson.se> <6353B598-245B-4D12-80E1-69323700C862@timeheart.net> <2DD56D786E600F45AC6BDE7DA4E8A8C117FF21A4@eusaamb107.ericsson.se> <D1F0ECE1-C012-4443-9E86-2E3D25C34AA9@juniper.net> <E5C97FAA-EBA4-48B3-BCFB-C87C132F9345@timeheart.net>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Tue, 13 Dec 2016 18:30:04 +0100
X-Google-Sender-Auth: PvIJDgeAHtyOHp5WOSRZPErAr8k
Message-ID: <CADZyTkmAUVDekj6FE+C3QY41SPK7Z8VPmGNRcoaaR9CeAQ2kmg@mail.gmail.com>
Subject: Re: Reference for UTF8 in SSH UTF8 terminal mode
To: Ron Frederick <ronf@timeheart.net>
Cc: Mark Baushke <mdb@juniper.net>, "ietf-ssh@NetBSD.org" <ietf-ssh@netbsd.org>
Content-Type: multipart/alternative; boundary="001a1143e54621a1e605438d921c"
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

Hi,

Thanks for the feed backs, I believe we are now ready for a (last) version
before moving the draft forward.

Yours,
Daniel



On Tue, Dec 13, 2016 at 4:18 PM, Ron Frederick <ronf@timeheart.net> wrote:

> On Dec 12, 2016, at 10:24 PM, Mark Baushke <mdb@juniper.net> wrote:
> >> On Dec 12, 2016, at 11:58 AM, Daniel Migault <
> daniel.migault@ericsson.com> wrote:
> >>
> >> Hi,
> >>
> >> Apology for the confusion. So my understanding of the problem is that
> using RFC3629 as a reference for the UTF-8 is not convenient as its two
> normative references need to be updated. The two references in question
> are: ISO/IEC 10646:2014 and Unicode. However from this thread, I am hearing
> that the major concern is about providing a updated reference for Unicode,
> not so much ISO/IEC 10646. As a result,
> >>
> >> I propose to have the following references:
> >>
> >> RFC3629 as normative
> >> [UNICODE]  The Unicode Consortium. The Unicode Standard.
> >>              <http://www.unicode.org/versions/latest/> as
> informational.
> >>
> >
> > I like it.
> >
> >> A more recent version of ISO/IEC 10646 will be done by refreshing
> RFC3629.
> >
> > Yes.
> >
> >> Am I correct ?
> >
> > It seems like a good plan to me.
>
>
> Sounds good here as well. Thanks!
> --
> Ron Frederick
> ronf@timeheart.net
>
>
>
>

v2.23.0 | Report a Bug | By Email