Re: [I18ndir] draft-faltstrom-unicode12 (was: Re: Getting restarted and triage)

"Patrik Fältström " <patrik@frobbit.se> Sat, 22 June 2019 01:28 UTC

Return-Path: <patrik@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 B9DB8120299; Fri, 21 Jun 2019 18:28:32 -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_HELO_NONE=0.001, 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 ZZcCB4ehGevK; Fri, 21 Jun 2019 18:28:30 -0700 (PDT)
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 BFEAE120282; Fri, 21 Jun 2019 18:28:30 -0700 (PDT)
Received: from [192.165.72.241] (unknown [IPv6:2a02:80:3ffc:0:70f4:2279:b2e0:d16e]) by mail.frobbit.se (Postfix) with ESMTPSA id 65FF023A13; Sat, 22 Jun 2019 03:28:24 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1561166904; bh=i5f+4pleq3cIuW4xBkpmS6UzR7hABETSlCPfpT1Wc68=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=m7VYlzMTlputJ58AOAac2IN0ro8bfYrDpdGDaM3Hdtq0Ghm22o4IvUGkTttO41ne5 iN/wbhSTUGUfhbGXenT61nASpwDZPcHuMf7HxvwTfXHEbzHibUbk5XJuItkI/UTBHF +S4ivV7C9OlUvABOMqvbfHB5QMoDk0+cRNDZtLZE=
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <patrik@frobbit.se>
To: "John C Klensin" <john-ietf@jck.com>
Cc: "Pete Resnick" <resnick@episteme.net>, "Alexey Melnikov" <alexey.melnikov@isode.com>, art-ads@ietf.org, "Peter Saint-Andre" <stpeter@mozilla.com>, i18ndir@ietf.org
Date: Sat, 22 Jun 2019 03:28:23 +0200
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <1DEA4BFE-A8BF-4CF2-BB95-B7B52877FED4@frobbit.se>
In-Reply-To: <FE907EC05D207D554919CBBE@PSB>
References: <F2B84580-7E5A-4B86-BF9C-0205D4E6121D@episteme.net> <843EAB4535391A494DA216CC@PSB> <774C5663-F336-4F5E-B4D6-2CD7C85FAD8E@episteme.net> <FE907EC05D207D554919CBBE@PSB>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_C8A92C1E-5FE8-49B8-B5B5-B22AD3E1FC3D_="; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/MeGyupnRBShquY15R7usbzCtbc0>
Subject: Re: [I18ndir] draft-faltstrom-unicode12 (was: Re: Getting restarted and triage)
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: Sat, 22 Jun 2019 01:28:33 -0000

On 22 Jun 2019, at 2:39, John C Klensin wrote:

> So, while we can sit on that until Alexey finishes his writeup if you (Pete, Peter, Alexey, directorate participants) like, it will come back to get us sooner or later.  And this is another reason why these documents are fairly seriously intertwined.

1. draft-faltstrom-unicode12 have two main issues:

1.1. It does not address Unicode 12.1 (easy fix)

1.2. It suggests a resolution to the divergence between Unicode and IETF due to incompatible changes in Unicode that makes IETF follow the Unicode Standard by allowing derived property values to change (better to let 5892 rules be fixed).

2. draft-klensin-idna-unicode-review do suggest the derived property value stay fixed, which implies 5892 algorithm must be updated in the case Unicode do changes in the future like has happened before as described in draft-faltstrom-unicode12.

Because [1.2] and [2] above are incompatible with each other, text in them should and I would say MUST match each other.

What we have as a fact is that IETF have already accepted actions based on draft-faltstrom-unicode12 until Unicode 12.0 at least so applying draft-klensin-idna-unicode-review to the review process can not happen for earlier versions.

   Patrik