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

[Patrik Fältström <[e-mail]>]

Thanks!

   Patrik - just bought ticket to Shinkansen, in a machine...first for me :-)

> On 15 Mar 2019, at 09:07, John C Klensin <[e-mail]> wrote:
> 
> FWIW, my view of this is identical to Martin's, i.e., the tables
> for Unicode 11.0 go to IANA now and we start working toward
> draft-faltstrom-unicode12-01, including both getting the
> document right and doing both sets of code point reviews (and,
> to the extent needed, sort out the "future updates" issues and
> others so that the text in draft-faltstrom-unicode12 can be both
> correct and clear.  That means we treat
> draft-faltstrom-unicode12-XX as superceding
> draft-faltstrom-unicode11-YY and just move forward.
> 
> And, please, let's not do any of that, other maybe than getting
> the Unicode 11.0-based table to IANA if you have time, until you
> have had time to get back to Sweden and recover and the rest of
> us have had time to catch our respective breaths.  I hope that
> everyone who has been observing the very significant
> improvements in document quality since
> draft-faltstrom-unicode11-07 understands that the pace several
> of us have had to keep to accomplish that is just not
> sustainable for anyone who has other significant commitments and
> will therefore cut us a bit of slack.
> 
> best,
>    john
> 
> 
> --On Thursday, March 14, 2019 23:26 +0000 "Martin J. Dürst"
> <[e-mail]> wrote:
> 
>> 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
>>>> <[e-mail]> 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 <[e-mail]>
>>>> To: [e-mail]
>>>> Cc: [e-mail], [e-mail]
>>>> 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
> 
> 
> 
>