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

[John C Klensin <[e-mail]>]

--On Saturday, June 22, 2019 03:28 +0200 Patrik Fältström
<[e-mail]> wrote:

> 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.

In case it wasn't clear, we are in complete agreement.

Thanks,
   john