2
Principles Global uniqueness and interoperability of the DNS –unique and unambiguous domain names with same functionality regardless of geographic placement of access Promote “Future-Proof” solutions –define characters that are allowed and an ability for adding new ones Not all characters used in the worlds languages will be available for use in domain names Diminish user confusion as much as possible, via –technical development and implementation requirements, registry policies, and user education IDNA protocol standard in implementation Promote multi-stakeholder involvement Roles of ICANN Supporting Organizations and Advisory Committees –ICANN staff does not create policy

3
Internationalized Top level Technical Test Laboratory test of Root-zone and resolver software successfully finalized Various suggestions from community: –Application testing –UI testing –Registry/registrar interface testing across to the end-user –Testing of sets of strings for user preference –DNAME testing and production –None of the above –More… Staff is consulting with ICANN Board Liaison’s for their technical expertise and recommendation on how to reach the goal –Create an overview of what happens from UI to DNS resolution –SSAC IDN Study –RSSAC participation Decision of whether internationalized top level labels can be inserted in the root-zone in a technically secure and stable manner

4
IDNA Revision - IETF IDNA is the protocol for IDNs The revision of IDNA is based on RFC4690, intends to: –Make it easier to understand how the protocol is working and should be implemented –Clearer terminology definitions –Make the protocol non-dependant on versions of Unicode –Inclusion based model instead of exclusion based –Stringprep changes to eliminate R-to-L script errors Follows the IETF process for RFCs – open participation Latest Internet draft version is available at: issues-01.txt

5
IDN Policies No formal policy development process has been started in the ccNSO and the GNSO Many IDN policy focused working groups and numerous meetings on the issues reports that was generated by these groups IDN Policy workshop: –Perhaps not possible to separate internationalized top level domains into ccTLD, gTLD or other categories –ccNSO, GNSO, GAC IDN working groups have a large amount of overlapping issues that need to be solved together –Staff will discuss with SO/AC Chairs for next steps More transparent, efficient and faster process to finalize

6
Thank You - to all those who work hard and proactively to make internationalized top level domains a reality Apologies - to all who need internationalized top level labels because we are not able to provide that service today