IETF Logo Mail Archive

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

Martin J. Dürst <duerst@it.aoyama.ac.jp> Thu, 14 March 2019 23:26 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 F36CA12796C; Thu, 14 Mar 2019 16:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.922
X-Spam-Level:
X-Spam-Status: No, score=-0.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.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 DU5T5ZkEKwqa; Thu, 14 Mar 2019 16:26:36 -0700 (PDT)
Received: from JPN01-OS2-obe.outbound.protection.outlook.com (mail-eopbgr1410138.outbound.protection.outlook.com [40.107.141.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE6FA126CFF; Thu, 14 Mar 2019 16:26:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Z5e5LoCx39DEFpMk06MVakgssHkZAkp8RkOkYfslVOc=; b=HteX0XRmZh6CnHsWYJVFVVzphIo4a7Dmh5vfVykmX55XVcygsYEkvzXZz95m1UUZeCim8CnXeIFuEVnusOsod6sKYirjLOZ+rJ+aZeiHruRqxS0VHnQgAvH2MgBk/XGR3mj/5X5iOZ6vXYtD/lnTzDw+o18Gb6/NA1EVIKO5WsU=
Received: from TYAPR01MB5149.jpnprd01.prod.outlook.com (20.179.187.18) by TYAPR01MB4608.jpnprd01.prod.outlook.com (20.179.174.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.13; Thu, 14 Mar 2019 23:26:32 +0000
Received: from TYAPR01MB5149.jpnprd01.prod.outlook.com ([fe80::98b6:d90e:9ae7:302]) by TYAPR01MB5149.jpnprd01.prod.outlook.com ([fe80::98b6:d90e:9ae7:302%3]) with mapi id 15.20.1709.011; Thu, 14 Mar 2019 23:26:32 +0000
From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
To: Patrik Fältström <paf=40frobbit.se@dmarc.ietf.org>, Alexey Melnikov <aamelnikov@fastmail.fm>
CC: The IESG <iesg@ietf.org>, IETF I18N Directorate <i18ndir@ietf.org>
Thread-Topic: [I18ndir] Update to IDNA parameters registry of derived property values
Thread-Index: AQHU2roXf6xAXCacDkCrkLnBuuZ6WaYLxUGA
Date: Thu, 14 Mar 2019 23:26:32 +0000
Message-ID: <0a3d678c-77fd-c94b-67a7-a3c89170e7bd@it.aoyama.ac.jp>
References: <155259884518.2625.11834392787966991080.idtracker@ietfa.amsl.com> <553EF1B9-9ACF-4EBB-ACCF-965BB467755C@frobbit.se> <F62C34EF-4F2C-4452-BCE6-CF4409415BF5@frobbit.se>
In-Reply-To: <F62C34EF-4F2C-4452-BCE6-CF4409415BF5@frobbit.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: TYAPR01CA0165.jpnprd01.prod.outlook.com (2603:1096:404:7e::33) To TYAPR01MB5149.jpnprd01.prod.outlook.com (2603:1096:404:12e::18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [223.218.133.122]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 678a9864-f8ed-43f5-2c80-08d6a8d47e4a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7025125)(7027125)(7023125)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:TYAPR01MB4608;
x-ms-traffictypediagnostic: TYAPR01MB4608:
x-microsoft-antispam-prvs: <TYAPR01MB46086D0BB31D3A89A721815FCA4B0@TYAPR01MB4608.jpnprd01.prod.outlook.com>
x-forefront-prvs: 09760A0505
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(39840400004)(366004)(346002)(136003)(199004)(189003)(81156014)(85182001)(5660300002)(66066001)(6116002)(486006)(11346002)(446003)(3846002)(4326008)(25786009)(305945005)(15650500001)(52116002)(8676002)(99286004)(54906003)(85202003)(110136005)(106356001)(786003)(7736002)(31686004)(105586002)(53936002)(316002)(6512007)(66574012)(6246003)(81166006)(2616005)(476003)(2906002)(8936002)(68736007)(74482002)(14444005)(256004)(76176011)(102836004)(6486002)(14454004)(6436002)(386003)(6506007)(53546011)(229853002)(508600001)(71190400001)(186003)(86362001)(71200400001)(26005)(97736004)(31696002); DIR:OUT; SFP:1102; SCL:1; SRVR:TYAPR01MB4608; H:TYAPR01MB5149.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: vzShcP2w7KLOPXKaIq8wuoTNBQ/dfVEc8rgV+FRuD2d66qZBu8bEQ0ceURt7dY5hdaq9nh7dkSLkHP1cUTBhKYTG2AyByMK17wQZq9aNL6/ZYR3VLK4y0lj+qw5F5I+s2V/Cg6sQ6P4jctcKwtg+DVJnn0x9OhLttFyYd6z/njftVN+Cxih0LwbewIDNlqcEF74IB7OVOHSeBis8XELI/OxH+iBFI2VSCLzg2wYsyerUVK3V9xZtxgGburp7Ba/ldXXbz+9qX2j8hmrXFQIwk6lkDDmIW1JRyjwqM4Adq7gcQ4gRNwPJDToc/iNs65DPiR9OAZdtvKI27wxRATODlbcGK3/gvrPgpa+f2Cma2G5n9zxp0BtC2itTnTQJbxzDdYspds/XOsJVNjdLekXmYO7yZPoS0xXJ0bJZnD4VEzk=
Content-Type: text/plain; charset="utf-8"
Content-ID: <4E6A3298E032B742A3AAB97AA0DFF4E2@jpnprd01.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: 678a9864-f8ed-43f5-2c80-08d6a8d47e4a
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Mar 2019 23:26:32.6888 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TYAPR01MB4608
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/W3fN2G855b1pmXddNn1-Z1TsPZM>
Subject: Re: [I18ndir] 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, 14 Mar 2019 23:26:38 -0000

Hello Patrik,

My understanding from all the mail I read and the datatracker was that 
IANA would update to 11.0.0 now.

But we would work on draft-faltstrom-unicode12, and when that was done, 
IANA would then update to 12.0.0.

That way, we wouldn't loose time on getting the word out that we are 
getting unstuck, while also giving us a little bit more time to have 
another close look at the new characters in 12.0.0, and getting your 
document into even better shape (and through another last call). So 
please send an updated draft to Alexey.

And please make sure you get enough rest.

Regards,   Martin.


On 2019/03/15 08:02, Patrik Fältström wrote:
> I was asked to work on unicode12:
> 
>> Hi Patrick,
>>
>> On 13 Mar 2019, at 21:47, Patrik Fältström <paf@frobbit.se> wrote:
>>
>> So replace with -12 is what I should do?
>>
>> After my exchange with John yesterday, I think updating unicode12-00 would be better.
>>
>> Thank you,
>> Alexey
> 
> Now IANA is asked to follow unicode11:
> 
>> From: IESG Secretary <iesg-secretary@ietf.org>
>> To: iana@iana.org
>> Cc: iesg@ietf.org, paf@frobbit.se
>> Subject: Update to IDNA parameters registry of derived property values
>> Date: Thu, 14 Mar 2019 14:27:25 -0700
>>
>> IANA,
>>
>> The IESG asks that IANA update the IDNA Parameters registry of derived property values to align with what is described in draft-faltstrom-
>> unicode11, after the expert reviewer validates that the derived property values are calculated correctly.
>>
>> Best regards,
>> IESG Secretary
> 
> Alexey, I need some clarity on what I should do.
> 
> My preference would be that this note from IESG was a typo, and that IESG in reality have the same view as Alexey, that IANA should follow draft-faltstrom-unicode12, that you approve posting of draft-faltstrom-unicode12 (I can send you a current version, or however the posting works) that reviews things up to and including Unicode 12.0.0 and we move on.
> 
>     Patrik

v2.23.0 | Report a Bug | By Email