Consensus Call Tranche 8 (Character Adjustments)

[Vint Cerf]

Consensus Call Tranche 8 (character adjustments)

Place your reply here: [YES or NO]

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)

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
vint at google.com




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/idna-update/attachments/20081012/95960da6/attachment.htm