Skip to main content

Chair’s Blog: An Overview of the March Remote Board Workshop

With so many things on our plate, the ICANN community, organization, and Board are all confronted with a sudden need to find new ways of getting things done. The Board’s recent decision to change ICANN67 from a face-to-face meeting in Cancún, Mexico, into a fully remote meeting was a difficult one. After our decision, we noted the further expansion of the virus and continuing uncertainties on how it will be contained. We truly appreciate the ICANN community’s support and understanding, especially as we continue to work out all of the technical and logistical details.

On behalf of the Board, I’d like to express my deep gratitude to our colleagues from ICANN org, who are working day and night to ensure our first virtual ICANN meeting will be as smooth and productive as possible. We are also very grateful to all of you in the community who came together to reorganize the meeting schedule so that it became manageable remotely. And a thank you to the local hosts for their understanding and collaboration, as they have been working closely with us to make this the best ICANN meeting ever.

While the workshop setting is not what we planned it to be, the Board remains fully committed to making meaningful progress on the work that needs to get done. We will continue to focus on the most time-critical matters, including the proposed change of ownership of Public Interest Registry (PIR), the .COM contract amendment, progressing work on key issues related to updating the operational plan and budget, and other matters that we can successfully address during our remote workshop. Additionally, we will prepare for our conversations with the community on the topics identified, including subsequent procedures, DNS abuse, and other important matters raised by the community.

On Monday, 2 March, following my opening remarks, we began our day with our usual dialogue with ICANN President and CEO Göran Marby. He provided us with the latest updates on matters relating to his goals for this year. We also carved out a large block of time to discuss contingency matters.

The second day of the remote workshop, Tuesday 3 March, focuses on the proposed transfer of ownership of PIR and related issues. Quite a lot has happened since the Internet Society (ISOC) announced its intent to sell PIR to Ethos Capital, and it is important that we understand all of the ins and outs of where we currently stand, including the announcement of the Public Interest Commitments (PICs) by PIR and Ethos Capital.  

On Wednesday, 4 March, Avri Doria will lead an update and discussion on New generic top-level domain (gTLD) Subsequent Procedures. Additional time has also been allotted to discuss any contingency matters.

Thursday, 5 March, will start off with a session about the .COM contract amendments, including an update on the results of the Public Comment period that closed on 14 February 2020. A report on the comments received will be published on 6 March 2020. Göran will then lead the Board’s discussion regarding DNS abuse. After that, we have another planned contingency block.

Both Friday, 6 March, and Saturday, 7 March, will be used to prepare for Constituency Day and engagement with any constituencies that want to meet with the Board regarding specific matters. On Friday, the ICANN org Policy Team will provide a briefing on the meeting’s hot topics. On Saturday, the Board will review the areas of interest received from the Supporting Organizations and Advisory Committees (SO/ACs) and consider its responses. We will also hold a training session for the Board to discuss and prepare for the two ICANN67 remote Public Forums. Contingency time has been allocated on both days, and will be used on Saturday to review resolutions or active accountability mechanisms.

Turning the Board’s workshop into a fully remote workshop is certainly a challenge, and one that we share with the Community. Not only does it mean not being face-to-face or being at the same location, but also not being within the same time zone. However, exceptional circumstances require exceptional measures. Virtual meetings are not new, but this is the first time we’ve ever held a fully virtual ICANN meeting. Let’s make the best of it. We are in this together.

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