Skip to main content
Resources

Compliance Outreach Activities | 2017

2021 | 2020 | 2019 | 2018 | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010

(Listed most recent first)

2017 Events

ICANN's 60th International Meeting in Abu Dhabi, 28 October – 3 November 2017

The Contractual Compliance team attended ICANN's 60th International Meeting in Abu Dhabi, United Arab Emirates, 28 October – 3 November 2017.

On Monday, the team provided a Contractual Compliance Program Update [PDF, 2.51 MB] to the community with a focus on addressing the questions and discussions from the attendees. The team held one closed session with the Registrars for discussion on compliance related matters. The team also joined the Registry Stakeholder Group on Tuesday to address their questions on compliance related matters.

In addition, the team joined the following sessions: The Generic Name Supporting Organization(GNSO) sessions, the Government Advisory Committee sessions, the board meetings with the stakeholders and the different working group and review team sessions. The team held meetings throughout the week with different ICANN members and contracted parties based on their request.

The information is also available at the Abu Dhabi ICANN meeting schedule.

Korea Outreach – 29 – 30 August 2017

Contractual Compliance completed an outreach visit in Seoul, South Korea in partnership with the Global Domains Division team. This visit was organized by Korea Internet & Security Agency (KISA), and approximately 28 representatives from 10 different registrars attended. It was an opportunity for the contracted parties to collaborate with ICANN on the compliance process, responses to notices and ask questions. Topics presented include Web Posting Obligations, Registrar Information Specification, Uniform Domain-Name Dispute-Resolution Policy, and how to communicate with ICANN Contractual Compliance. After the outreach presentations [PDF, 2.17 MB], Contractual Compliance staff conducted 1 on 1 sessions with 3 contracted parties who had more specific questions. All presentations and 1 on 1 sessions were conducted in English, with a Korean translator present to provide translations. The registrars provided positive feedback on having a translator who helped them understand the presentations better and have more constructive discussions during the 1 on 1 sessions.

Turkey Outreach – 15 August 2017

Contractual Compliance, in partnership with the Global Domains Division team, conducted a roundtable outreach session with Turkish Registrars and Registries in Istanbul, Turkey. Eighteen representatives from 8 ICANN accredited registrars and 2 Registry Operators attended the event. The outreach was conducted mostly in Turkish. It was an opportunity for the contracted parties to collaborate with ICANN and ask questions. Some of the topics of discussion were: Clarification of ICANN's Contractual Compliance process, how to communicate with ICANN Contractual Compliance, Whois Accuracy Program Specification (WAPS) requirements, Thick WHOIS services, Uniform Domain Dispute Resolution Policy (UDRP) and Registrar Data Escrow Program (RDE). Additionally, the compliance team conducted individual meetings with some of the Registrars and Registry Operator representatives to discuss specific compliance matters and provide further clarifications. The attendees appreciated ICANN's effort to host the Turkish focused roundtable outreach.

China Outreach – 10 - 11 July 2017

Contractual Compliance completed a China outreach visit in partnership with the Global Domains Division team in Xiamen, China. The outreach was targeted at newly accredited China registrars, and approximately 42 representatives from 32 different registrars attended. It was an opportunity for the contracted parties to collaborate with ICANN on the compliance process, responses to notices and ask questions. Topics presented include Abuse, WHOIS Inaccuracy, Web Posting Obligations, Registrar Information Specification, and how to communicate with ICANN Contractual Compliance. After the outreach presentations, Contractual Compliance staff conducted 1 on 1 sessions with 6 contracted parties who had more specific questions. All presentations and 1 on 1 sessions were conducted in Chinese. The registrars and registries were appreciative of this outreach and of the ability to interact in their local language.

Global Domains Division Summit in Madrid, Spain – 9-11 May 2017 and ICANN Identifier Technology Health Indicator Workshop 12 May 2017

In May, the Contractual Compliance team participated in the Global Domains Division (GDD) Summit in Madrid. The team held a round-table discussion as requested by the contracted parties. In addition, several 1-1 sessions were conducted with contracted parties to address specific compliance topics related to them. For more information about the summit, please refer to the GDD Industry Summit page at this link https://www.icann.org/gddsummit.

On Friday 12th May, Contractual Compliance joined the Identifier Technology Health Indicator workshop to present compliance information related to Whois Inaccuracy [PDF, 833 KB] processing and reviews and to support the ITHI initiative. This initiative is run by the ICANN Office of the CTO (OCTO) to develop metrics to quantify and measure the state of the unique Internet identifiers that ICANN helps coordinate. Please refer to this link https://www.icann.org/ithi-faqs for more information about the initiative.

ICANN's 58th International Meeting in Copenhagen, 11 – 16 March 2017

The Contractual Compliance team attended ICANN's 58th International Meeting in Copenhagen, Denmark, 11 – 16 March 2017.

On Sunday, the team held two closed sessions; one focused on the Registrars [PDF, 1.04 MB] and the other one on the Registry Operators [PDF, 1.16 MB]. The sessions gave the contracted parties and ICANN the opportunity to ask questions and collaborate on compliance related matters. On Monday, the team provided a Contractual Compliance Program Update [PDF, 5.16 MB] to the community with a focus on addressing the questions and discussions from the attendees.

In addition, the team participated in the following sessions: the At-Large Advisory Committee (ALAC) and Regional Leadership Working Group [PDF, 728 KB], the Government Advisory Committee (GAC) Public Safety Working Group [PDF, 3.33 MB], the Registry Stakeholder Group, the Registrar Stakeholder Group, provided a Briefing to the GAC [PDF, 532 KB] and attended the Generic Name Supporting Organization (GNSO) sessions, the GAC sessions, the board meetings with the stakeholders and the different working group and review team sessions. The team also held meetings throughout the week with different ICANN members and contracted parties based on their request.

The information is also available at the Copenhagen ICANN meeting schedule.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."