Site Map  |  Site Index  |  Quick Links 

Select a link below: About ICANN Accountability and Transparency Address Supporting Organization (ASO) Affirmation of Commitments Affirmation of Commitments-Reviews Announcements Annual Report Articles of Incorporation At-Large Advisory Committee (ALAC) Blog Board Meeting Minutes and Resolutions Board of Directors Budget (see Financial Information) Bylaws Calendar of Events Careers Certificate Authority Code of Conduct Committees - Other Committees - Advisory Committees - Board Committees - Past Contact Information Continuity Contracts Contractual Compliance Newsletter Contractual Compliance Program Corporate Documents Correspondence Country Code TLD Managers - Information for Country-Code Names Supporting Organization (ccNSO) Country-Code Top-Level Domain Agreements Country-Code Top-Level Domain Board Materials Country-Code Top-Level Domain Listings DNSSEC Dashboard Dispute Resolution Options Documentary Information Disclosure Policy Documents Domain Name Dispute Resolution Policies E-Learning EPP Status Codes Expedited Registry Security Request Process Factsheets Fellowship Program Financial Information First-Time Visitors Former Directors Frequently Asked Questions GNSO Improvements General Documents Generic Names Supporting Organization (GNSO) Generic Top-Level Domain (gTLD) Program Generic Top-Level Domain (gTLDs) Life Cycle Generic Top-Level Domain Information (gTLDs) Global Partnerships Glossary Governance Documents Governmental Advisory Committee IANA Agreement IANA ccTLD Reports IANA ICANN Info ICANN Organizational Reviews IDN Glossary IDN ccTLD Fast Track Process IPv6 Policy In Focus Independent Review Proceeding Documents InterNIC Internal Procedure for Conflicts with Privacy Law Internationalized Domain Names Links Litigation Documents Major Agreements Meetings for the Next Decade Consultation Meetings Mission Monthly Registry Reports News Newsletters & News Alerts Newsletters Archive Nominating Committee Ombudsman Operating Plan (see Strategic and Operating Plan) Organizational Chart PGP Keys Participate in ICANN Partnership Memorandums of Understanding Payments to ICANN Photos Planning Process Policy Area Policy Issue Briefs Policy Update Presentations President and CEO President's Strategy Committee Press Resources Public Comment Publications RSS Feeds Reconsideration Requests Reconsideration and Independent Review Registrants Information Registrar Accreditation Agreement Amendments Registrar Accreditation Overview Registrar Advisories Registrar Agreements Registrar Complaints Registrar Data Escrow Program Registrar Information Registrar Problem - Get Help Registrars - Accredited Registry Agreements Registry Information Registry Listings Registry Monthly Reports Registry Services Evaluation Process Report Inaccurate Whois Information Requests for Proposals Resources Root Server System Advisory Committee (RSSAC) Security Team Security and Stability Advisory Committee (SSAC) Speeches Sponsored Top-Level Domains Staff Strategic and Operating Plan Supporting Organizations Transfers Travel Support Universal Acceptance of All Top-Level Domains Video Vint Cerf's Legacy Letter to ICANN Community Website Enhancement Whois Information Whois Search Wiki - Resolutions Project

        Search 

• Structure
•  

RSSAC has been asked for a statement on ICANN's proposed next steps for IDN deployment in the root zone.

Policy discussions are continuing and are clearly out of scope for RSSAC. RSSAC takes no position on what the contents of the strings used to instantiate IDNs in the root should be, or how many there should be within a factor of 2-5 times the current size of the root zone, or what the duration of the test should be, as long as DNS protocol is followed regarding length of labels, permitted characters, and so on.

With regards to technical and operational issues, RSSAC's consensus as discussed 18 March in the Praha meeting includes:

• There's no issue with adding standard delegations (NS records) to the root zone to instantiate IDN at the root.
• RSSAC urges ICANN to consult DNS experts on constraints such as appropriate TTL values for test IDNs. RSSAC itself represents a significant reserve of such expertise and its members would be happy to try to provide guidance on this subject. However, these details are immaterial to the job of serving a root zone that includes IDNs; the impact is on resolvers and applications.
• ICANN will be coordinating the test, collating test results, and making further decisions about how to go forward to production deployment. ICANN, particularly IANA as the party responsible for the root zone, are asked to provide notice to RSSAC as the test begins and ends and the findings that result from it.
• It's our understanding that several of ICANN's policy bodies are examining aliasing of domain names as one possible component of an IDN solution. Aliasing can be accomplished in a variety of ways. If aliasing of existing domain names is needed as part of the deployment of IDN, RSSAC would provide technical and operational input on how to accomplish it effectively. IANA would have to provide notification of changes to software, hardware, or procedures the root server operators would need to implement in advance of major changes in the capabilities required to serve root zone data; the best way to make sure this happens is to keep RSSAC advised as decisions are made regarding further tests and eventual production deployment so expectations are clear.
• ICANN may find that it will be useful to have specific data or measurements from the root server operators, as part of testing or production deployment of IDN, regarding any changes in traffic or other operational parameters IDN labels might cause. ICANN is encouraged to outline any specific measurements in which they are interested relating to the effects of the test deployment.