Skip to main content

The First Week

As I begin my role with ICANN, I wanted to provide you with a quick update on my early days. With a packed schedule, I've been focused on learning as much as possible, and on meeting many members of the ICANN community.

I kicked off with my first Board workshop, in Amsterdam. I spent time with my senior team and the Board, and was able to dig into some of the big issues ICANN is tackling. After the Board Workshop, I attended the first day of the GDD Summit. It was a great opportunity to meet many of the contracted parties that are members of the ICANN community, and I appreciated learning more about issues affecting registries and registrars, as well as the lively discussions on subsequent procedures of generic top-level domains.

After the meetings in Amsterdam, I spent the weekend in Copenhagen, at an informal meeting with the leadership of the "I* organizations." It was an interesting meeting, with an impressive level of collaboration and frank dialogue contributed by all parties involved. We explored areas of possible cooperation, and discussed everything from the status of the implementation of IANA stewardship transition to the Internet of Things and its impact on the work of I* organizations.

On my first formal day at ICANN, I was able to spend the day getting to know my colleagues in the European Internet Numbers community at part of RIPE-72, a community that is part of the core of ICANN. It was a great way to learn more about the issues – and to reaffirm our commitment to work with the community on the IANA transition implementation, and to identify and address any key emerging issues, now and in a post-transition ICANN.

After a brief few days home in Stockholm, I head off to Los Angeles to settle into my new office. The level of collegiality and coordination is what makes this community great, and I am glad to be a part of it. I look forward to learning from, working with and supporting many of you in the near future.

Comments

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