Skip to main content

Compliance Outreach Activities | 2019

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

(Listed most recent first)

2019 Events

Outreach activities in Eastern Europe October 2019

Compliance team attended the 4th Eastern European DNS Forum held in Yerevan, Armenia, on 11-12 October 2019. The team delivered a session dedicated to the issues and challenges impacting domain name holders. The goal of the session was to raise awareness among domain holders and share the ways to protect domain name. The session was held in Russian language and allowed the participants (including, among others, Registrars, Resellers, Domain Name holders, country code top-level domain (ccTLD) operators, and trademark lawyers) to freely interact, ask questions, and share their comments and best practices in dealing with issues concerning domain names.

ICANN 66 Prep Week Webinar – 15 October 2019

Contractual Compliance participated in the ICANN 66 Prep Week by hosting a webinar and presenting a general update on 15 October 2019 regarding its activities since ICANN 64. You can find additional details regarding the ICANN 66 Prep Week here.

June-July 2019 Outreach Activities in Europe, Middle East and Africa Regions

Within the period of June-July 2019 Contractual Compliance team conducted series of Registrar trainings in EMEA region in collaboration with the Global Domains Division (GDD) and Global Stakeholder Engagement (GSE) teams. The goal of outreach sessions is to increase awareness among registrars in the region, who are not able to participate at ICANN meetings and provide them an opportunity to better understand ICANN Contractual Compliance process and approaches, contractual obligations, a chance to discuss topics of interest in local languages and in person and exchange of ideas or experience with the fellow colleagues within the industry. ICANN Compliance has also started conducting sessions in collaboration with the ICANN Registrant Program that provides educational information about what issues and challenges registrants are facing with the objective to educate them about its rights and obligations. Trainings and outreach sessions conducted in Kampala (Uganda), Lisbon (Portugal) and Tel Aviv (Israel). Survey results demonstrate that Registrars appreciate regional outreach sessions and request for more such activities to be held in the region.

Russia Outreach – 6 June 2019

The Contractual Compliance Istanbul team conducted outreach session for Eastern European registrars in Moscow, Russian Federation, in partnership with Global Domains Division (GDD) and Global Stakeholder Engagement (GSE) teams. Compliance session and all materials were delivered in Russian language with interpretation into English. Topics presented included WHOIS, Abuse, Uniform Domain Dispute Resolution (UDRP), Data Escrow, Transfer Policy, Expired Registration Recovery Policy (ERRP) as well as ICANN's Contractual Compliance Approach and Process. Topics of high interest for registrars were UDRP and Abuse. Per survey results, 70% of respondents were most satisfied with the compliance session. The registrars were appreciative of the ability to interact in their local language and requested for more compliance sessions in the future.

ICANN's 64th International Meeting in Kobe – 9-14 March 2019

The Contractual Compliance team attended the ICANN64 Community Forum in Kobe, Japan from 9-14 March 2019.

On Monday, the team held a Registrar Outreach session to address a list of topics that were brought forward by the Registrar Stakeholder Group compliance sub-group team.

On Tuesday, the team provided a Contractual Compliance Program Update to the community with a focus on the team's recent activities, including processing complaints related to the Temporary Specification for gTLD Registration Data. In addition, the team addressed questions from the attendees.

On Wednesday, the team provided an introduction to ICANN Contractual Compliance upon request to the At-Large Advisory Committee and held a Registry Outreach session focused on the registry audit round.

As in every ICANN meeting, the team attends the Generic Name Supporting Organization (GNSO) sessions, the Governmental Advisory Committee (GAC) sessions, the board meetings with stakeholders and the different working group and review team sessions. The team also held meetings throughout the week with different ICANN community members, including contracted parties and community members based on request.

ICANN 64 Prep Week Webinar – 27 February 2019

Contractual Compliance participated in the ICANN 64 Prep Week by hosting a webinar and presenting a general update on 27 February 2019 regarding its activities since ICANN 63. You can find additional details regarding the ICANN 64 Prep Week here.

Middle DNS Forum – 20–21 February 2019

Contractual Compliance Istanbul team conducted outreach session for Registrants in partnership with Global Domain Division team at Middle East DNS Forum. The session was dedicated to common issues and challenges impacting domain name registrants. During the session, the team shared the list of common complaints received from registrants and answered the questions asked by providing tips and guidance on how to avoid domain name management-related issues. The audience consisted of registrants, resellers, registrars, end users and other parties actively involved in the Internet Industry. Participants also had the ability to share their best practices and exchange their ideas on how to increase and improve awareness among registrants and avoid the issues encountered within the industry.

North America Outreach – 26 January 2019

Contractual Compliance conducted a workshop for Registrars and prospective registrars in Las Vegas, Nevada in collaboration with Global Domains Division, Global Stakeholder Engagement, Policy, and representatives from the Registrar Stakeholder Group. Topics presented included WHOIS Inaccuracy, Privacy and Proxy Services, Uniform Domain-Name Dispute-Resolution Policy (UDRP), Registrar Data Escrow (RDE), Reseller Requirements, Registrar Information Specification (RIS) and Web Posting Obligations (WPO), as well as ICANN's Contractual Compliance Approach and Process. Additional information regarding the event, including presentation materials can be found here.

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"""" is not an IDN."