Re: [I18nrp] Last Call: <draft-faltstrom-unicode11-05.txt> (IDNA2008 and Unicode 11.0.0) to Informational RFC

"Patrik Fältström " <paf@frobbit.se> Tue, 04 December 2018 10:40 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5EC130EA1 for <i18nrp@ietfa.amsl.com>; Tue, 4 Dec 2018 02:40:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.722
X-Spam-Level:
X-Spam-Status: No, score=-1.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se
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 CzKTJz7E10fL for <i18nrp@ietfa.amsl.com>; Tue, 4 Dec 2018 02:40:47 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A74D512785F for <i18nrp@ietf.org>; Tue, 4 Dec 2018 02:40:47 -0800 (PST)
Received: from [169.254.86.6] (unknown [IPv6:2a01:3f0:1:0:29da:870d:c8f1:83f4]) by mail.frobbit.se (Postfix) with ESMTPSA id 0024E20334; Tue, 4 Dec 2018 11:40:44 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1543920045; bh=tjHWLbJy/xQOJ5tD+NO9dUQPp2EXaGdKS0WTnmaBg5g=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=B3owkEjcX3j7PdmBB2dLrRg1tk8bLehbsuC2uOrlrAdjVlyI1P22+lEB2Btb8j9Aq tpxuQInuzLuAqGK7mZjvi9esZFBwkmRXCx7DRmBmdvibcr0NLS0T0zh1wXHxRNJwG8 3tA8r02qLCUws8QnkHPFJMO/TWp59nW49pSC6T7Y=
From: Patrik Fältström <paf@frobbit.se>
To: John C Klensin <john-ietf@jck.com>
Cc: i18nrp@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
Date: Tue, 04 Dec 2018 11:40:44 +0100
X-Mailer: MailMate (1.12.2r5568)
Message-ID: <57166C65-8AE8-4231-9830-5FBF6C43E8F9@frobbit.se>
In-Reply-To: <95EB3D3321F6E91A22C9FE3B@PSB>
References: <154385119878.18333.5085298134102919486.idtracker@ietfa.amsl.com> <FF6F9EB9-C73B-4EC0-AC4F-3E3BFBABA0AB@vpnc.org> <8E20D432-01B0-4B52-80BB-3348C5FE73AF@vpnc.org> <A5B69D318689A6515CCB4883@PSB> <E5A7B829-FE59-4649-AE36-2918E910A667@frobbit.se> <95EB3D3321F6E91A22C9FE3B@PSB>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_72B4B1AA-E71C-4B58-BD02-D961863462EC_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/rboyJ9Rg5MdtXRfnrF-IgUTMa-A>
Subject: Re: [I18nrp] Last Call: <draft-faltstrom-unicode11-05.txt> (IDNA2008 and Unicode 11.0.0) to Informational RFC
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2018 10:40:50 -0000

On 4 Dec 2018, at 11:33, John C Klensin wrote:

 I think these are the right steps.  As far as they go, they are certainly consistent with what the specs require.
> There are, IMO, two weaknesses which might interact with Paul's concerns (or not):
>
> (a) You are talking about a relatively mechanical process.

Yes, indeed.

What I did not mention is that I also keep track of, to my best ability, comments on various unicode mailinglists, the main IETF mailing list and others where I feel Unicode and IDNA issues might come up. And also of course I collect comments sent to me directly. This as my responsibility as a liaison (etc).

Yes, this is ad-hoc, but as far as I know the best we can do at the moment.

Now when (if? ;-) ) we get this i18nrp group going it will make this ad-hoc process easier and a bit less ad-hoc, but trust me, I will not stop doing what I am already doing regarding this ad-hoc thing. It will just make my life easier (even though it might be more work) and definitely easier for others to track what I am doing as I will know exactly where to report things (and where to catch things).

So, even if it is ad-hoc, we should not ignore this, and I should have had it in my list.

And no, it does not replace anything you and/or Paul ask for, but at least >0.

   Patrik