• The South Asian Eleven - Progress on Supporting IDNs in Scripts from the Region
    on February 16, 2018 at 8:00 am

    We recently traveled to South Asia to initiate and support community-driven efforts for developing the Internet's Root Zone Label Generation Rules (RZ-LGR), which will further enable a multilingual internet. This included meetings for Neo-Brahmi, Sinhala and Thaana Generation Panels. Thaana Script We started our series in the Maldives, where we were hosted by the Communications Authority of Maldives (CAM) for a two-day engagement on the domain name system and cybersecurity. Next on the agenda was a day of training on Internationalized Domain Names (IDNs), as well as the purpose and design of RZ-LGR. This training was attended by members of Computer Society of Maldives, the Dhivehi Academy and local experts working on Thaana – the Maldivian script -software. Participants explained how the Thaana script is fairly regular in its use of consonants and vowel marks to write Dhivehi [PDF, 154 KB] language in a right-to-left direction. Interestingly, we also learned that the community mixes scripts. For example, they use the Thaana and Arabic scripts to write the name Abdullah [PDF, 221 KB]. From our meetings, there is now interest from the community in forming a Generation Panel (GP) for Thaana script to develop its proposal for RZ-LGR. Sinhala Script The Maldives meetings were productive and proved to be a great warm-up or net-practice for the five-day engagement in Colombo, Sri Lanka, where we supported discussions on development and review of multiple script based proposals. Over the weekend, we prepared to bat with the Sinhala script team members, many of whom have long been involved with Sinhala Unicode standardization and second-level domain names. We were hosted by Theekshana, a non-profit company associated to University of Colombo School of Computing (UCSC), with our meeting room overlooking the beautiful cricket grounds on UCSC campus. The Sinhala (සිංහල) script used to be written on palm leaves and is drawn in curves because straight lines could tear the leaves. It is used to write Sanskrit and Pali texts. During the meetings, we explained the constraints imposed by the procedure to develop the RZ-LGR and discussed the implications on the Sinhala script. The panel was also briefed on label-level rules being developed for Devanagari script by the Neo-Brahmi Generation Panel (NBGP) to organize the Akshara constraints, as an example for organizing Sinhala characters. Finally, the panel reviewed other scripts and found possible cross-script variant character cases with Kannada, Malayalam, Myanmar and Telegu scripts, which it intends to investigate further. The meeting ended with a media briefing where the Sinhala GP chair, Sri Lanka's representative on the Governmental Advisory Committee (GAC), and ICANN org talked about the importance of IDNs and announced the formation of the Sinhala GP. Neo-Brahmi Scripts The Neo-Brahmi Generation Panel (NBGP) panel was also convening in Colombo for their face-to-face meeting. The Neo-Brahmi and Sinhala GP teams started with a joint session, with members from India, Nepal, and Sri Lanka (we hope Bangladesh will join soon), focused on matters of mutual interest. These included the consistent framework for label-level rules for South Asian scripts, cross-script variants between Sinhala script and the scripts covered by NBGP, and the proposal for the Tamil script being developed by the NBGP. The NBGP had set an aggressive goal to hit at its meeting. After discussing Tamil, the next meeting featured a formidable line-up of experts to deliberate on Gujarati, Gurmukhi, Kannada, Malayalam, and Telugu scripts. Work on these scripts has progressed significantly. The first complete drafts were reviewed by the panel, which identified challenges and possible ways forward. Experts working on the Kannada script identified characters which haven't been used in nearly 50 years and eventually excluded them from the RZ-LGR proposal. The panel had a detailed discussion on cross-script variant characters to determine an agreeable mechanism to identify them – should variant characters be strictly homoglyphs, or should they also include other confusing characters? The panel converged on a solution to tag each pair of candidate cross-script variant characters with one of the three colors , based on independent feedback from members from both relevant scripts, for indistinguishable, similar and distinct characters. The GP identified multiple script pairs including Devanagari-Gurmukhi (देवनागरी - ਗੁਰਮੁਖੀ), Kannada-Telugu (ಅಕ್ಷರಮಾಲೆ - తెలుగు లిపి) and Tamil-Malayalam (தமிழ் - മലയാളലിപി) for the cross-script variant analysis. Looking Back We concluded our trip with a visit to the Cricket Club Café, a popular eatery in Colombo. We were surrounded by nostalgic cricket memorabilia including a bat with signatures of the Sri Lankan eleven who won the 1996 Cricket World Cup. Although we were as tired as we would be after playing a five-day cricket match, we were also enthused by the immense energy the community members injected in the invigorating discussions. We were driven by their passion to speak up for their languages and scripts. As we perused the menu, we were silently mindful of the line-up of the eleven scripts covered by the three panels we had been supporting in this trip. These scripts also exhibited a glorious variety in their style, simultaneously arraying a unifying South Asian Abugida writing culture at a deeper level. […]

  • Supporting Standards that Ensure an Open and Interoperable Internet
    on February 14, 2018 at 8:00 am

    The Internet as we know it today owes its development and scalability to the meticulous work of thousands of volunteers who develop technical standards and specifications that ensure global interoperability. This work is mostly done by the Internet Engineering Task Force (IETF), both online and three times a year during face-to-face meetings around the world. This year, ICANN is cohost with Google of the 101st meeting of the IETF in London from 18–23 March. IETF meetings gather about a thousand volunteer technologists. For a week, they discuss to advance their work on new standards or specifications candidates, and ways to improve or evolve existing ones. Over the past few meetings, a pre-event Hackathon has gained significant momentum. During the Hackathons dozens of coders and engineers from around the world work for two days to develop and debug applications that implement specific Internet standards or specifications which often includes work on both current and future Domain Name System (DNS) standards. This pre-event showcases practical implementations of the IETF standards and specifications through actual "running code." For ICANN, supporting the IETF through sponsoring or cohosting allow us to express our continuous trust in the process and the thousands of volunteers who make it work. They contribute in the IETF to help build a robust set of standards and specifications that support the secure, stable, and resilient Internet that we all work for. ICANN's mission to help coordinate the smooth management of current unique Internet identifiers is a function that resulted from Internet Protocol (IP) specifications that the IETF defined. Supporting the IETF's work is also a way for ICANN to ensure that through our technical engagement we fulfill part of our own mission to support "One World, One Internet." Several members of the ICANN organization participate in and contribute to the IETF's work. Our team members are currently working as authors or coauthors of more than 15 Internet drafts, many of which are under discussion in different working groups. Many of them will be presented in London. IETF 101 in London will be another opportunity to engage with the IETF community and bring some emerging technical issues and solutions home for further review or implementation. Recent meetings have showcased topics related to encryption in protocol specifications, deliverability of the DNS, and IP version 6 (IPv6). Göran Marby, ICANN President and CEO, will give a short address during the plenary on Wednesday. We also expect the attendance of Cherine Chalabi, Chair, ICANN Board of Directors, who lives in London, and other members of the ICANN Board and community. If you are attending IETF 101 and want to learn more about ICANN, feel free to visit our team at the ICANN booth. ICANN also hosted the IETF 89 meeting in London in 2014 (at the same hotel!) and has sponsored a few recent meetings, including IETF 100, held in Singapore in November 2017. Read more about the IETF 101 meeting at https://www.ietf.org/how/meetings/101/. […]

  • Data Protection/Privacy Update: Latest Developments
    on February 14, 2018 at 8:00 am

    My last blog of 25 January focused on the input received on the three proposed interim models for collecting registration data and implementing registration directory services in preparation for the 25 May 2018 enforcement date for the European Union's General Data Protection Regulation (GDPR). As you'll recall, input on the models which, along with feedback requested from community discussions on this topic, are contributing to the assessment of each potential option. From those inputs, either variations or modifications to one of these models, each of which includes a tiered/layered access approach to WHOIS data, will be identified. As we shared during the webinar on 2 February, we are reviewing this input, and have shared a preliminary non-paper [XLSX, 14 KB] and graphic [PDF, 730 KB] representation of the models. The webinar, together with the community discussions, are providing very useful input to the evolving iteration of an interim compliance model. In parallel to our work with the community, we also exchange information with the Article 29 Working Party and respective Data Protection Authorities (DPAs) on a regular basis, in order to update each other on developments and progress. We sincerely appreciate the ongoing dialogue and help from the DPAs and are encouraged by the progress of these exchanges because ultimately, they will be judging the results of the proposed models. We will continue to engage with them on the recommended interim model and 'action plan', including process of compliance and implementation as we work towards finalizing these. As the community works toward a long-term solution, we encourage this continued dialogue. We may formally ask DPAs for their views concerning ICANN's approach to the compliance model, since this would usefully inform both improvements to the interim solution and the development of the long-term framework. In relation to the ICANN org's work with the stakeholders on solidifying views around an interim model, we welcome the ongoing community discussions and are working to share a next iteration of a model very soon. This single, common interim model that is informed by input from across the ICANN community would seek to obtain compliance with both the GDPR and ICANN's contractual requirements related to registration directory services. The final interim model will include a rationale and input received in relation to each component. But it is important to remember that ICANN's contracted parties need to make their own determination about GDPR and related legal obligations as they relate to their specific situations. This also holds true for other stakeholders such as registrants. Please continue to visit our data protection/privacy page for regular updates and of course send your questions to gdpr@icann.org. This is clearly an important topic for both the ICANN org and the community, and we are all striving towards the same May 2018 timeline. I also want to take this opportunity to thank everyone who has participated in this important process, whether it was submitting questions or models for consideration, or in discussions within the multistakeholder community. […]

  • Chair’s Blog: The Los Angeles Workshop Recap
    on February 8, 2018 at 8:00 am

    With about a month left before many of us gather in Puerto Rico, I wanted to share with you an overview of the most recent Board workshop. Washington, D.C. Visit On my way to Los Angeles for the Board workshop, I stopped in Washington, D.C. for a few days to meet with stakeholders from the region. I met with some representatives of civil society & think tanks at the Center for Democracy and Technology, and with business stakeholders at the U.S. Chamber of Commerce. Thank you to our hosts, and those who came and asked questions. I very much appreciated our productive conversations. With the ICANN org staff, I held introductory meetings with relevant U.S. House and Senate staffers and with the National Telecommunications and Information Administration to discuss ICANN and answer any questions people might have. I was also able to spend time with the ICANN org staff in Washington. Board-Only Day I was then on to Los Angeles, and as I mentioned in my last blog, we held this Board workshop a little differently then we have in the past. The Board met alone, without staff, for an additional day at the beginning of the workshop, where we took the time to hold deep dives and strategic discussions on topics like the picket fence and the trends in the China domain name registration market. We discussed the challenges facing the Board around deciding if something is in the global public interest, held a session on improving Board effectiveness and efficiency and agreed on the outline of a community consultation paper on the replenishment of the Reserve fund. It was a chance for us to take some time to think and discuss major issues and our priorities moving forward. Board Workshop We covered many important topics during the rest of the workshop, discussing the ongoing developments around General Data Protection Regulation (GDPR) compliance for ICANN contracts and the ICANN org, the work done by the Cross-Community Working Group on Workstream 2, and the strategic planning process. We know the long-term strategic plan is of great importance for everyone involved in ICANN, and we talked about how to best get involved and support the process. We heard an update regarding ICANN org’s ongoing efforts to identify and mitigate DNS infrastructure abuse (phishing, botnets, malware), and Ram Mohan led a topic on the security and resilience of the root server system. We also began a discussion around recommending, as a “best practice,” that the ICANN’s Supporting Organizations, Advisory Committees, and Cross Community Working Groups include an analysis on how policies, advice and recommendations submitted to the Board for consideration are aligned with ICANN’s mission. The Board intends on issuing a consultation paper on this topic. During the first open session of our workshop, Avri Doria summarized the path by which the community agreed to create a new Work Track 5 within the GNSO’s Policy Development Process for New gTLD Subsequent Procedures. The Board was briefed on the differences between a GNSO PDP and a cross community working group, and on how the agreed Terms of Reference for this work track allows for some adoption of the latter’s flexibility within the GNSO’s policy remit. The Board welcomes the community’s willingness to collaborate on its work relating to geographic names as top-level domains, steered by Work Track 5 co-chairs appointed by the ALAC, GAC, ccNSO and GNSO. The Board reviewed the Draft FY19 Budget currently out for public comment during another open session, and had a lively discussion focused on ensuring funding and expenses assumptions are conservative and that the budget process continues to allow broad community engagement and input. We also received an update on the current and projected financial situation for FY18 as part of exercising close oversight over the ICANN org on financial responsibility. In a session led by Becky Burr, on GAC Advice and curative rights protections, ICANN org briefed the Board on the current status of community work concerning protections at the second level of the domain name system for international governmental organizations. The Board, led by Maarten Botterman, then reviewed the resolution about the GAC’s advice from the Abu Dhabi Communique. During our official Board meeting, we passed several resolutions, on topics such as the SSAC Advisory on Registrant Protection, .MUSEUM, and Home/Corp/Mail applications. Read more here. Engagement with the Community in Los Angeles As the fifth Non-Contracted Parties House (NCPH) Intersessional Meeting was being held in Los Angeles at the same time, we were invited to join the NCPH delegates for lunch on the second day of the meeting. The Intersessional allows representatives from the various community groups making up the NCPH to come together, to collaborate on policy and other topics of mutual interest. The lunch was an excellent opportunity for Board members to meet with community leaders as well as new faces from each community group in an informal setting. Along with Avri, Becky, León Sanchez, Matthew Shears and Sarah Deutsch, I joined the GNSO Council for a discussion on the Council’s focus for the year ahead, including the need to ensure efficiency and effectiveness in managing the GNSO policy process. This was the Council’s first-ever strategic planning session, and it happened to be in Los Angeles while we were there. We were pleased to have had the chance to meet them in person for a very informative dialogue. Board Member Integrity Screening As you may recall from ICANN60 in Abu Dhabi, the Board has been considering the issue of Board Member Integrity Screening for some time. On 1 November 2017, I reported in a blog the steps that the Board agreed to take to ensure that Board Members hold themselves to the highest standards of integrity and to uphold the reputation and credibility of ICANN. These steps included conducting screenings for the current and incoming board members that had not gone through the due diligence screening process as a part of their selection. These integrity screenings were conducted through a professional third-party firm and the due diligence reports were delivered to the office of the General Counsel. In order to provide a mechanism for review of the due diligence reports, the Board Governance Committee (BGC) reconstituted a former Sub-Committee of the BGC on Ethics and Conflicts. The BGC selected George Sadowsky to Chair and also named Rafael Lito Ibarra and Sarah Deutsch as members of the Sub-Committee. On 3 and 4 February 2018, the Sub-Committee reviewed each of the seven due diligence reports for the following board members -- Becky Burr, Chris Disspain, Manal Ismail, Ram Mohan, Matthew Shears, Mike Silber and Jonne Soininen. Please read a report from the Sub-Committee, which has been sent to the BGC which indicated their unanimous finding that there was no reason to question the credibility or integrity of any of the board members who were the subject of these reports. I am pleased that integrity screenings for all Board Members have now been completed and I look forward to the next step in this process, regarding the communication with the community participants in board member selection and the development of a consultation paper that will be posted for public comment on a proposed path for continued integrity screenings to be considered as part of the board selection process. In summary, it was a very productive and full time in Los Angeles and Washington. As you are getting ready for the ICANN61, please keep in mind that we currently have four public comments open – so I’d like to take this blog as a reminder to you to please participate and share your comments here. […]

  • Progressing the IANA functions into 2018
    on February 8, 2018 at 8:00 am

    The last few years have been a period of intense focus on ICANN and the IANA functions — which are the management of key services including updating the DNS root zone, allocating global Internet Protocol address blocks to Regional Internet Registries, and assigning protocol parameters such as private enterprise numbers. With the U.S. government stepping away from its stewardship role over the IANA functions, and the Internet community coming together to form a replacement multistakeholder stewardship model, the priority within ICANN's team that performs these functions has stayed focused on stable and dependable service delivery. Now, a little over a year after the transition of the stewardship of the IANA functions, we have a number of data points to reflect upon how we've performed. Most tangible of these measurements is our just completed annual customer survey, which we conducted for the sixth year. This year's results have provided clear indications that the IANA functions continue to be dependably delivered to high satisfaction levels. The results show accuracy should be our number one focus in delivering our service, with timeliness and processing quality ranking after that. These survey outcomes echo the results we've seen in the comprehensive service level reporting we provide, with many community-defined metrics of performance reported either in real time, or through monthly reports. These metrics show consistent service delivery and a strong commitment to the community's defined service level targets. Several new oversight mechanisms and committees were also established as a result of the transition of the stewardship to the multistakeholder community. The operation of those groups is stable and we've established a regular rhythm and methods of working together. We're working productively with many of these new organizations, including the Customer Standing Committee and the Root Zone Evolution Review Committee, as well as existing accountability measures such as those with the IAB and IETF leadership. The community created a new ICANN legal affiliate called "Public Technical Identifiers" (PTI), which houses the IANA functions and the staff that deliver the services. PTI is now in its second year of operation. The PTI Board, including one new Director appointed through the ICANN Nominating Committee process, recently held a one-day workshop to discuss its oversight role. On a more personal note, I have been a part of the IANA team since 2005, initially responsible for our root zone services and later leading our technical services. Since the start of this year, I have been entrusted to lead the whole team in the role of VP, IANA Services. Our team's remit remains to provide the dependable IANA service the community has come to expect, as well as implement a vision for modernizing and improving how we deliver these services to raise the bar moving forward. I am looking forward to meeting with many of you in the community in my new capacity and hearing your thoughts on our priorities and focus. Our entire team is excited to continue to deliver reliable services to the whole Internet community, and we're looking forward to maintaining our productive partnerships with all of you in the Internet architectural and operations communities. If you'll be attending ICANN61, I hope to see you there! […]

ICANN Announcements

ICANN Announcements ICANN Announcements

  • ICANN Holds First Capacity Development Workshop for Asia GAC Members
    on February 15, 2018 at 8:00 am

    SINGAPORE – 15 February 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN), in cooperation with the ICANN Governmental Advisory Committee (GAC) Underserved Regions Working Group, announced today the first capacity-development workshop for Asia GAC members and representatives, to be held from 24–25 February 2018 in Kathmandu, Nepal, with the support of Nepal's Department of Information Technology. Sanjay Sharma, Secretary, Ministry of Science and Technology, Nepal, will give the opening remarks. Almost 20 government representatives from 11 economies in Asia will attend the workshop. In rapidly developing Asia, expected home to the next billion Internet users, challenges remain in ensuring adequate and secure Internet access. Barriers to participation in ICANN include a lack of human resources and knowledge about the Domain Name System (DNS). The workshop, which aims to address these challenges, will feature key ICANN policy topics and the relevant GAC and cross-community working groups. Topics will include: Understanding the ICANN ecosystem Understanding the Internet: names, numbers, protocol parameters Security, stability, and resiliency (SSR) of unique Internet identifiers ICANN policy development process Speakers from regional Internet organizations will introduce their ongoing work in the Asia Pacific region as part of the Internet ecosystem. Workshop participants will discuss effective ways to participate and contribute to ICANN discussions. Additionally, the workshop will seek feedback from Asia GAC representatives on how best to support their work and increase their presence in the region and in ICANN. The full workshop agenda can be found here [PDF, 415 KB]. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. […]

  • Draft Procedure for Community gTLD Change Requests
    on February 14, 2018 at 8:00 am

    Open Date: 14 February 2018 Close Date: 2 April 2018 Originating Organization: Global Domains Division Categories/Tags: Contracted Party Agreements Brief Overview: The ICANN organization is seeking comments on a draft procedure [PDF, 327 KB] for ICANN to consider changes to Specification 12 of Community generic Top Level Domain (gTLD) Registry Agreements. The guiding principles of the procedure would permit a community gTLD registry operator to seek modifications to Specification 12 without removing the Community Registration Policies, excessively broadening or narrowing registrant eligibility and/or name selection requirements or resulting in significant negative impact to the TLD Community. This draft procedure is the result of collaboration between the Community gTLD Change Request Process Working Group and the ICANN organization, with input provided by members of the Registries Stakeholder Group (RySG). This Public Comment proceeding follows the steps outlined in guidance [PDF, 245 KB] provided on this topic by the GNSO Council. Link: https://www.icann.org/public-comments/community-gtld-change-procedure-2018-02-14-en […]

  • View the Latest Quarterly Stakeholder Update and Register for the Q&A Call on 22 February
    on February 14, 2018 at 8:00 am

    LOS ANGELES – 14 February 2018 – Today, the Internet Corporation for Assigned Names and Numbers (ICANN) published its FY18 Q2 Stakeholder Update for the quarter ending 31 December 2017. Göran Marby, President and CEO, and Cherine Chalaby, Chairman of the Board have prepared an executive summary highlighting key updates from the report. Read the report and the executive summary here. You are invited to attend a question and answer (Q&A) call on 22 February at 17:00 Coordinated Universal Time (UTC) to ask any questions about this report. To join the call, please register here. If you are unable to access the form, please register by sending an email to icann.communications@icann.org with your full name and email address. The call will be recorded and open for all to attend, with simultaneous interpretation in Arabic, Chinese, English, French, Portuguese, Russian, and Spanish. Recordings in all languages will be posted on ICANN's Quarterly Reports page. This call is a great way for you to stay informed about the ICANN organization's efforts toward accountability and transparency, while complying with ICANN's mission of keeping the Internet secure, stable, and interoperable. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. […]

  • Register Now: Pre-ICANN61 Policy Open House – 1 March 2018
    on February 8, 2018 at 8:00 am

    The Policy Development Support Team is pleased to announce two sessions for an upcoming webinar: Pre-ICANN61 Policy Open House Thursday, 1 March 2018 10:00 and 19:00 Coordinated Universal Time (UTC) The webinar will run in English and will be conducted in Adobe Connect along with a dial-in conference bridge for audio. Recordings of the sessions will be made available here. Please register via this form by 26 February 2018! In this interactive 60-minute open house, the focus will be an active question and answer session with the Policy Development Support Team. To ensure that your questions about policy activities are addressed during the session, the Policy Team invites you to submit your questions through the registration form or email them to policyinfo@icann.org. To assist with your preparation for this webinar and for ICANN61, the "Pre-ICANN61 Policy Report" and "Generic Names Supporting Organization Policy Briefing: ICANN61 Edition" will be published by Monday, 26 February 2018. Please be sure to download and review these materials beforehand for helpful background on policy activities and topics that the Policy Development Support Team will discuss during the open house, such as: An overview of the cross-community discussions that will take place at ICANN61: General Data Protection Regulation (GDPR): WHOIS Compliance Models A Walk in the Shoes of a New Generic Top-Level Domain (gTLD) Registry Operator Name Collisions Open Data at ICANN Policy development processes underway in the Country Code Names Supporting Organization (ccNSO), the Generic Names Supporting Organization (GNSO) and the Address Supporting Organization (ASO): Retirement of Country Code Top-Level Domains (ccTLDs) Review of All Rights Protection Mechanisms in All gTLDs Next-Generation Registration Directory Service to Replace WHOIS International Governmental Organizations and International Non-Governmental Organizations Access to Curative Rights Dispute Resolution Mechanisms Protections for Red Cross National Society Names in the Domain Name System New gTLD Subsequent Procedures Regional Internet Registry policy development activities Advisory Committee activities within the At Large Advisory Committee (ALAC), Governmental Advisory Committee (GAC), Root Server System Advisory Committee (RSSAC) and Security & Stability Advisory Committee (SSAC): Organizational Review of the At-Large community At-Large Summit (ATLAS) III GAC discussion on the .amazon Independent Review Process GAC discussion on evolving relationships with ICANN Board and ICANN Org RSSAC statement on entries in DNS Root Sources RSSAC & SSAC Response to the GNSO's New gTLD Subsequent Procedures Working Group on Root Scaling SSAC Response to the ICANN Internationalized Domain Name Guidelines Working Group SSAC work concerning the use of emoji in domain names Other topics of note: Organizational Review of the ASO ccNSO Rejection Action Procedure as a Decisional Participant in the ICANN Empowered Community Impact of ICANN's Implementation of the General Data Protection Regulation (GDPR) on ccTLDs The Policy Development Support Team looks forward to helping the ICANN community prepare for ICANN61! Please register via this form by 26 February 2018! About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. […]

  • Call for Experts to Study the Application of Root Zone Label Generation Rules
    on February 8, 2018 at 8:00 am

    LOS ANGELES – 8 February 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) is forming a technical group to study how to apply the Root Zone Label Generation Rules (RZ-LGR) for the Internationalized Domain Names (IDN) country code top-level domains (ccTLDs) and IDN generic top-level domains (gTLDs). The study group will be composed of technical subject matter experts on IDNs and the RZ-LGR from the Supporting Organizations (SOs), the Advisory Committees (ACs) and the Internet Architecture Board (IAB). The ICANN Board will consider recommendations developed by this study group to determine next steps. Expert's nominations should be emailed to IDNProgram@icann.org by 28 February 2018 Background IDN TLDs have been a priority for the ICANN Board for several years, based on the input from the community. The variant labels for IDN TLDs have been an important component for some script communities. Therefore, in 2010, the ICANN Board asked the ICANN org and the community to investigate feasible approaches for variant labels of IDN TLDs, while putting the variant TLDs on hold until the work was completed. In 2012, the community examined various case studies for six scripts.The examination noted in the Integrated Issues Report [PDF, 2.15 MB], that there were two items to be addressed: (1) there was no universally acceptable definition of what may constitute a variant relationship between IDN TLD labels at the time; and (2) there was no variant management mechanism defined. Following this report, the ICANN org and the community developed the Procedure to Develop and Maintain the Label Generation Rules for the Root Zone in Respect of IDNA Labels [PDF, 1.39 MB] (RZ-LGR Procedure). This procedure defined what constitutes a variant relationship between IDN TLD labels. in 2013, the ICANN Board endorsed this procedure and asked the ICANN org and community to undertake it. To date Arabic, Armenian, Cyrillic, Ethiopic, Georgian, Khmer, Korean, Lao and Thai script GPs have completed and submitted their RZ-LGR proposals. From these, Arabic, Ethiopic, Georgian, Khmer, Lao and Thai scripts have already been integrated into the second version of the RZ-LGR. Many of the remaining script communities are now in the process of finalizing their work. With the availability of the RZ-LGR, the ICANN Board is now asking the ICANN community to recommend how to apply the RZ-LGR in a harmonized way to IDN TLDs in order to address the first item noted in the Integrated Issues Report [PDF, 2.15 MB], as a prerequisite to determine possible variant management mechanism. Study Group Expertise and Composition The study group members should have expertise in one or more of the following areas relevant for the IDN TLD labels. IDNA2008, RFC 6912 and RFC 7940 Procedure to Develop and Maintain Root Zone Label Generation Rules Script-based RZ-LGR proposal development Technical evaluation for IDN new gTLDs and IDN ccTLDs Unicode security considerations IDN TLD usability challenges The group will tentatively be composed of ten members: GNSO (2), ccNSO (2), SSAC (2), ALAC (2) and IAB (2). Tentative Scope of Work The study group will address the following topics focused on applying the RZ-LGR for existing and future IDN TLDs from a technical perspective. As appropriate, the study group may add more relevant topics. Validation of future TLDs using RZ-LGR Definition of variant TLDs and their disposition based on RZ-LGR and whether policy could further reduce allocatable variant TLDs Application of RZ-LGR on reserved IDN TLD labels Harmonized application of RZ-LGR across IDN TLDs, including IDN gTLDs and IDN ccTLDs Remaining requirements of security and stability evaluation of future IDN TLDs by the DNS Stability Panel after applying RZ-LGR *This study is not intended to review the RZ-LGR Procedure developed by the community and endorsed by the ICANN Board. Tentative Work Plan Tentative steps and timeline are listed below: Formation – March 2018 Analysis and identification of relevant issues – May 2018 Development of recommendations – August 2018 Finalization based on public comment – September 2018 Publication – October 2018 The group is anticipated to meet on a weekly basis and finalize the report in a period of six months. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. […]