Consensus Call Tranche 8 (Character Adjustments)

[Martin Duerst]

At 18:25 08/10/12, Vint Cerf wrote:
>Consensus Call Tranche 8 (character adjustments)
>
>Place your reply here: [YES or NO]

[Vint, if you need to count this only one way,
just count it as a NO to be on the safe side.]


YES for 8.a and 8.b. Despite the transition issues
mentioned by Mark, the long discussion on this list has
shown that these are the right things to do in the long term.
While I'm not aware of any concrete examples of similar
cases, I think it would be worthwhile to check with other
potentially affected script/language communities.
What, for example, about the few final letters in Hebrew?


NO for 8.c, for the reasons explained by Mark.
KRNIC is free (or better, strongly recommended) to exclude
conjoining Hangul from what they allow to register,
but that should not influence our discussion too much.

[Just as a hopefully far-fetched example, assume that
one day in North Korea, a few Hangul syllables containing some
historic Jamos gains crucial importance.]

Regards,   Martin.


>COMMENTS:
>
>
>Procedure:
>
>
>There are several decisions that the working group will need to make to confirm consensus.  I will send a series of proposals over the next two weeks requesting YES or NO positions on each within a 4 day window. If NO is the response, a reason for that position needs to be stated. If there is a clear consensus based on responses or in the absence of a consensus against each proposal, it will be assumed that the proposal is acceptable to the Working Group.
>
>
>Parenthesized symbols (e.g., "(R.1)") after the items are references to the issues lists where additional explanations can be found, as sent by John Klensin as body parts "idnabis-protocol-issues-rev3" and "idnabis-rationale-issues-03" on a message titled 'Issues lists and the "preprocessing" topic'  to the working group on 18 August (<http://www.alvestrand.no/pipermail/idna-update/2008-August/002537.html>http://www.alvestrand.no/pipermail/idna-update/2008-August/002537.html)
>
>This group needs to get its documents out; it is behind its original schedule. It should be noted that the IDN ccTLD and gTLD selection initiatives at ICANN have already begun so that delay may weaken the IETF's ability to assist in a rational deployment of IDNA.
>
>
>
>(8) Specific character adjustments for IDNA2003 -> IDNA2008
>differences.
>
>(8.a) Make Eszett Protocol-Valid per list discussion.
>
>(8.b) Make Greek final sigma Protocol-Valid per list
>discussion.
>
>(8.c) Disallow conjoining Hangul jamo per recommendation from
>KRNIC and others, permitting only precomposed syllables.
>
>
>
>
>NOTE NEW BUSINESS ADDRESS AND PHONE
>Vint Cerf
>Google
>1818 Library Street, Suite 400
>Reston, VA 20190
>202-370-5637
><mailto:vint at google.com>vint at google.com
>
>
>
>
>_______________________________________________
>Idna-update mailing list
>Idna-update at alvestrand.no
>http://www.alvestrand.no/mailman/listinfo/idna-update


#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst at it.aoyama.ac.jp