Skip to main content
Resources

Compliance Outreach Activities | 2016

2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010

(Listed most recent first)

2016 Events

ICANN's 57th International Meeting in Hyderabad, 2 – 9 November 2016

The Contractual Compliance team attended ICANN's 57th International Meeting in Hyderabad, 2 – 9 November 2016.

On Friday, the team held two closed sessions; one focused on the Registrars [PDF, 1.75 MB] and the other one on the Registry Operators [PDF, 1.61 MB]. The sessions gave participants the opportunity to ask questions and collaborate directly with the Contractual Compliance team.

On Saturday, the team provided a Contractual Compliance Program Update [PDF, 2.10 MB] to the community with a focus on addressing the questions and discussions from the attendees. The team also joined the Update on WHOIS-Related Initiatives [PDF, 432 KB] to share an update on the Contractual Compliance related activities.

On Sunday, the team joined the Intellectual Property Constituency (IPC) Stakeholder Group [PDF, 493 KB] to share an update on the compliance activities and address their questions.

In addition, the team held meetings throughout the week with different ICANN members and contracted parties based on their request.

Please refer to the Hyderabad ICANN meeting schedule page for access to meeting objective and material by meeting.

Korea Outreach - 31 August 2016 and 1 September 2016

Contractual Compliance, together with Registrar Services, conducted an outreach in Seoul, Korea. Approximately 20 Korean contracted parties met with ICANN's Seoul representative and the Asia Pacific ICANN organization team. It was an opportunity for the contracted parties to collaborate and gain a better understanding on Whois Accuracy Specification Program (WAPS), Whois Format, UDRP and to learn more about Contractual Compliance Approach and process. The sessions were conducted in English and Korean languages.

Registrar Audit Program Outreach Sessions – May 2016

The Contractual Compliance team conducted two outreach sessions about the RAA Compliance Audit Program [PDF, 430 KB] on 24 May 2016 to present an overview of the registrar audit program and to address questions from registrars selected for this round of audit.

China Outreach – 19 to 25 March 2016

Contractual Compliance completed a China outreach visit in partnership with the Global Domains Division team. The team visited Beijing, Shanghai, Chengdu and Guangzhou. The outreach was targeted at China registries and registrars, and Contractual Compliance Update for January - March 2016 5 approximately 160 representatives attended. It was an opportunity for the contracted parties to collaborate with ICANN on the compliance process, responses to notices and the audit program. Topics presented include abuse, WHOIS inaccuracy, WHOIS format, transfers, Uniform Dispute Resolution Policy (UDRP), and how to communicate with ICANN Contractual Compliance. The sessions were conducted in Chinese. The registrars and registries were appreciative of this outreach and of the ability to interact in their local language.

ICANN's 55th International Meeting in Marrakech, 5 – 10 March 2016

The Contractual Compliance team attended ICANN's 55th International Meeting in Marrakech, 5 – 10 March 2016.

On Tuesday, the team joined the Intellectual Property Constituency (IPC) Stakeholder Group [PDF, 838 KB] to share an update on the compliance activities and address their questions. In addition, the team met with the At Large Advisory Committee to address their questions.

On Wednesday, the team provided ICANN community a Contractual Compliance Program Update [PDF, 3.41 MB] with a focus on addressing the questions and discussions from the attendees. The team also met with the Brand Registry Group [PDF, 709 KB] to share an update on the audit program and activities.

On Thursday, the team held two closed sessions; one focused on the Registrars [PDF, 1.95 MB] and the other one on the Registry Operators [PDF, 2.71 MB]. The sessions gave participants the opportunity to ask questions and collaborate directly with the Contractual Compliance team.

In addition, the team held meetings throughout the week with different ICANN members and contracted parties based on their request.

Please refer to the Marrakech ICANN meeting schedule page for access to meeting objective and material by meeting.

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."