Re: [I18ndir] [IANA #1137949] Update to IDNA parameters registry of derived property values

"Patrik Fältström " <paf@frobbit.se> Thu, 21 March 2019 20:52 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5BF1315A9; Thu, 21 Mar 2019 13:52:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.721
X-Spam-Level:
X-Spam-Status: No, score=-1.721 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, URIBL_BLOCKED=0.001] autolearn=unavailable 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 4Z6f_VSxWdIm; Thu, 21 Mar 2019 13:51:59 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3CE01310A0; Thu, 21 Mar 2019 13:51:58 -0700 (PDT)
Received: from [192.165.72.241] (unknown [192.165.72.241]) by mail.frobbit.se (Postfix) with ESMTPSA id D7D2A26CB3; Thu, 21 Mar 2019 21:51:49 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1553201510; bh=dShWa/o4pyFBZ2rBzRbhsOi+OB9PgUeaxlXjXuy857k=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=vbmpme3JBRDm0D/6ZjjUe6dIql3q2zroifVRCj/etIoFr8eFtykBGaGmAT5o3COzF jFE9JA2w8SWDRosS63oOOiA92tfUzjkFItxnHBaKFtE9H8WNlveRdHrMfatKVNqB8y SavwWH6ju5Mxp6+DoFhW37+5yxz5v7TVzdbGtZuI=
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Amanda Baber via RT" <iana-matrix-comment@iana.org>
Cc: alissa@cooperw.in, aamelnikov@fastmail.fm, michelle.cotton@iana.org, "The IESG" <iesg@ietf.org>, "IETF I18N Directorate" <i18ndir@ietf.org>, iab@iab.org
Date: Thu, 21 Mar 2019 21:51:54 +0100
X-Mailer: MailMate (1.12.4r5597)
Message-ID: <6728BF4B-02D1-4BF2-B600-7563DA7D9680@frobbit.se>
In-Reply-To: <rt-4.4.3-24412-1553189234-147.1137949-9-0@icann.org>
References: <RT-Ticket-1137949@icann.org> <155259884518.2625.11834392787966991080.idtracker@ietfa.amsl.com> <rt-4.4.3-24412-1553180624-1613.1137949-9-0@icann.org> <182C5997-5937-4EB1-86A8-3F4FAF521C76@frobbit.se> <F7674AEE-7976-4AF6-A346-029C87A01E7F@frobbit.se> <rt-4.4.3-24412-1553184185-1758.1137949-9-0@icann.org> <rt-4.4.3-24412-1553189234-147.1137949-9-0@icann.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_B0976403-4F90-4A53-ADDD-C93DBA447954_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/r_G6HHnQeh2g7rV5EgrO0YaPrKk>
Subject: Re: [I18ndir] [IANA #1137949] Update to IDNA parameters registry of derived property values
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2019 20:52:01 -0000

Hi,

I have checked the files you did send me and compared the XML files with the same files I have produced.

As I do not see any differences, I hereby say I do not see any problems with having IANA making the tables with the derived property values available.

The review is based on the normative algorithm defined by IDNA2008, and based on RFC6452 and draft-faltstrom-unicode11-08.txt no backward compatible changes are to be made in the cases when changes in the Unicode Standard have lead to non-backward compatible changes in the derived property values when Unicode 6.0.0 and 11.0.0 was introduced.

   Patrik

On 21 Mar 2019, at 18:27, Amanda Baber via RT wrote:

> Hi Patrik,
>
> When we were discussing these in June (subject line [IANA #1113325]), we sent drafts of the registries for 7.0.0, 8.0.0, 9.0.0, 10.0.0, and 11.0.0, and you said that you would be OK with posting those after the situation with the I-D was resolved. Would you be able to check these again and confirm that they're still OK to use, provided that we update the date at the top of each registry?
>
> thanks,
> Amanda
>
> On Thu Mar 21 16:03:05 2019, paf@frobbit.se wrote:
>> On 21 Mar 2019, at 16:20, Patrik Fältström wrote:
>>
>>> 2. I do the same (I have done so), which I have done, and I send you
>>> a pointer to my result
>>
>> Here is my data in the format you earlier wanted. If you want a
>> different format, let me know.
>>
>> <https://stupid.domain.name/stuff/iana-11.0.0.csv>
>>
>> Patrik