Skip to main content

Munich Registry/Registrar Event

On 12-13 May 2011, ICANN hosted its Europe Regional Registry/Registrar Event in Munich, Germany. ICANN shared news of this event with the community in its 28 March 2011 blog post.

More than 60 participants including representatives from gTLD registries, ICANN-accredited registrars, and numerous observers including a ccTLD registry and future new gTLD applicants, attended the event. ICANN introduced the regional event model in 2005 and the primary goals are two-fold. First, they provide an educational opportunity, to discuss topics important to the effective contractual compliance and operation of a gTLD registry or ICANN-accredited registrar. Second, the sessions are intended to broaden participation in the ICANN multi-stakeholder governance model. Additionally, the event is open to observers that may have an interest in becoming a gTLD registry or ICANN-accredited registrar.   

While the agenda for ICANN general meetings includes policy issue debates and decision-making by various ICANN groups, these regional events have a different focus.  They are not intended as a replacement for attendance at the ICANN meetings, but are designed to assure that the parties to contracts with ICANN better understand their roles and responsibilities while encouraging them to participate more fully in the process. These events are also an opportunity for future gTLD registries and ICANN-accredited registrar to learn more about what is involved in serving in those stakeholder groups. Efforts to enhance the interactive nature of the presentations have proven successful as participants actively contribute to the presentations with questions and input gleaned from their own experiences.

The two-day agenda included ICANN staff providing updates and answering questions on topics including, new gTLDs, GSNO Policy Development, Contractual Compliance, gTLD Registry and Registrar Operational Readiness for new gTLDs, Registrar Training Program, and IDNs. Additionally, Stéphane van Gelder, Chair of the GNSO Council and Chuck Gomes, former Chair of the GSNO Council, led a session about the GNSO, Jean-Christophe Vignes, Vice Chair of the Registrar Stakeholder Group, and James Bladel, Director, Policy Planning at GoDaddy, led a session about the Stakeholder group, Michele Neylon, CEO of Blacknight Internet Solutions Ltd., facilitated a discussion about Registrars/Law Enforcement, and Edmon Chung, CEO of DotAsia, led a session about the Joint IDN Working Group. Lastly, the following gTLD registries opted to provide an update on their TLDs' activities to attendees: DotAsia, Verisign, and ICM Registry, LLC. ICANN staff is grateful for the broad participation and contributions these speakers made to the event. Overall feedback from participants to date has been very positive.

In the interest of transparency, the following information is available from the event.

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