Skip to main content

Joint CWG-Stewardship & CCWG-Accountability Chairs' Statement

Lise Fuhr & Jonathan Robinson – CWG-Stewardship
Thomas Rickert, León Sanchez, & Mathieu Weill – CCWG-Accountability

As both Cross Community Working Groups prepare for community engagement and work sessions at ICANN52 in Singapore, the Chairs of the CWG-Stewardship and CCWG-Accountability would like to recognize the interdependence and connected nature of the work of their respective groups, as set out by the ICANN processes1 and further reinforced by each working group's Charter.2

Following the ICANN 51 Meeting in Los Angeles, the CWG-Stewardship Chairs and the Chairs of the CCWG-Accountability Charter Drafting Team started to hold update and coordination calls, a practical and early recognition of the requirement for active collaboration on their respective work efforts. These weekly interchanges and updates are ongoing and serve to keep each other informed about questions and issues arising from their respective working groups. Moving forward, the Chairs commit to continue to actively work together, and synchronize insofar as possible, on timelines and milestones, especially where there are accountability mechanisms that may be relevant for both groups.

To assist in broader community understanding of the interdependencies of the parts of Work Stream 1 that relates to the CWG, a schematic illustration of the dynamics between the two working groups is available in a flowchart [PDF, 154 KB].

Work in Progress

The CCWG-Accountability has just concluded a two-day meeting in Frankfurt, Germany (19-20 January), during which they discussed their Work Stream 1 requirements, with initial input from the CWG-Stewardship on accountability dependencies. Both working groups are expected to continue this dialogue as work progresses.

The CWG-Stewardship, following an intensive work weekend on 10-11 January, is in the process of reviewing its timeline for submission of a proposal to the IANA Stewardship Transition Coordination Group (ICG). A vital part of this endeavor is the seeking of legal advice on questions related to the viability of key elements of the CWG-Stewardship proposal. As the CCWG-Accountability also moves forward to seek legal advice, the Chairs will inform each other of the process used and advice received, so as to further ensure efficient synchronization in light of dependent and compressed timeframe.

ICANN 52 Meeting in Singapore (9-13 February 2015)

The Chairs intend to all be present at both CWG-Stewardship and CCWG-Accountability related sessions during the ICANN 52 Meeting in Singapore, including the ICG-organized events. This will reinforce the working groups' commitment to a productive meeting, advancing discussions and improving collaboration. Below is a compiled list of engagement sessions and working sessions that are relevant to both processes:

*All times in local time (UTC +8)

IANA Stewardship Transition & Enhancing ICANN Accountability Information Session
Olivia Meeting Room
Sunday, 8 February 17:30-19:00

Responses to the ICG RFP Regarding the IANA Stewardship Transition
Padang/Canning Meeting Room
Monday, 9 February 10:30-13:00

CCWG-Accountability Working Session
Padang Meeting Room
Monday, 9 February 16:00-19:00

CCWG-Accountability Engagement Session
Padang Meeting Room
Wednesday, 11 February 9:45-11:15

CWG-Stewardship Working Session
Padang Meeting Room
Wednesday, 11 February 17:15-19:15

CCWG-Accountability Working Session
Padang Meeting Room
Thursday, 12 February 07:00-10:00

CWG-Stewardship Questions & Answers Session
Padang Meeting Room
Thursday, 12 February 10:30-11:45

The full schedule for the ICANN 52 meeting in Singapore is available here.

1 On 6 June 2014, ICANN, in its role as facilitator, published a community-driven process for the IANA Stewardship Transition. Community discussions on the IANA Stewardship Transition led to the development of an additional process on Enhancing ICANN Accountability, which was published on 10 October.

2 The CWG-Stewardship Charter was circulated for adoption on 14 August 2014. The CCWG-Accountability Charter was circulated for adoption on 3 November 2014.

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