Skip to main content
Resources

Minutes | Board Governance Committee (BGC) Meeting

Published 8 May 2015

BGC Attendees: Chris Disspain – Chair, Gonzalo Navarro, Mike Silber, Bruce Tonkin, and Suzanne Woolf

BGC Member Apologies:  Cherine Chalaby, Erika Mann

Other Board Member Attendees:  George Sadowsky

Executive and Staff Attendees: Megan Bishop (Board Support Coordinator), Michelle Bright (Board Support Manager), Samantha Eisner (Associate General Counsel), John Jeffrey (General Counsel and Secretary), Liz Le (Senior Counsel), and Amy Stathos (Deputy General Counsel)


The following is a summary of discussions, actions taken, and actions identified:

  1. Minutes – The BGC approved the minutes from the 19 March 2015 meeting.
  2. Ombudsman - The BGC discussed the length of the Ombudsman's term.  Following the discussion, the BGC decided to continue the discussion to the next BGC meeting.
  3. Reconsideration Request 15-4 – Staff briefed the BGC regarding the request submitted by Schwarz Domains & Services GmbH & Co. KG, seeking reconsideration of ICANN's decision to deny the Requester's request, submitted pursuant to the New gTLD Application Change Request Process and Criteria (“Change Request Process”), to change its application for the string .SCHWARZGROUP to an application for the string .KAUFLAND.  Staff explained that upon receipt of the change request, staff evaluated the Requester's change request in accordance with the Change Request Process.  The Requester's change request was denied because, among other reasons, requests to change applied-for strings generally are not acceptable. The only exceptions have been in the cases of typographical or otherwise minor errors and the Requester's change request instead proposed an entirely new string.  After discussion, the BGC determined that the Requester has not demonstrated any violation of established policy or procedure in implementing the Change Request Process, and that ICANN staff evaluated the Requester's change request in accordance with the Change Request Process.  As such, the BGC concluded that Requester has failed to demonstrate that ICANN's denial of the change request violates any ICANN policy or procedure.  The Bylaws authorize the BGC to make a final determination on Reconsideration Requests brought regarding staff action or inaction and the BGC concluded that its determination on Request 15-4 is final; no consideration by the NGPC is warranted.
  4. Reconsideration Request 15-5:  Staff briefed the BGC regarding the request submitted by Atgron, Inc. seeking reconsideration of the BGC's determination of Reconsideration Request 15-1.  Request 15-1 challenged staff's actions in processing the Requester's Registry Services Evaluation Policy (“RSEP”) request to allow the Requester to offer third-level domain name registrations in .WED.  On 19 March 2015, the BGC determined that the Requester failed to demonstrate that ICANN staff acted in contravention of any established policy or procedure in responding to the RSEP Request and therefore, the BGC denied Request 15-1.  After discussion, the BGC continued its consideration of Request 15-5 to its next meeting.
  • Action:  Staff to facilitate revisions to the BGC's Recommendation in light of the discussion, and present to the BGC for consideration at the next BGC meeting.
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."