EN
Down Arrow
User Icon
Hamburger Icon
`
SEARCH
X

GAC WEBSITE SEARCH

SEARCH

Meetings & Records

Full meetings of the GAC are usually conducted three times a year in conjunction with an ICANN public meeting. They may also be conducted intersessionally. GAC meetings are usually open. This part of the website provides access to past, present and future GAC meeting materials, including other calls and interactions the GAC has internally and with other groups.

Mar
15
2017
ICANN58 - Agenda Item 32 - GAC Meeting with the ICANN Board
09:00 - 10:30 UTC+01:00
|
HALL A2
|
Dial In Info
Session Details:

Discussion of issues with the ICANN Board

2-character country/territory codes at the second level.

  1. GAC Leadership and ICANN staff to liaise with the Board and ICANN organisation on follow-up arrangements.

Red Cross/ Red Crescent / Red Crystal

  1. GAC Members and Observers, supported by the ACIG GAC Secretariat, to monitor GNSO response to the Board Resolution.
Session Minutes:

The GAC met with the ICANN Board and discussed the following issues (outcomes are covered under relevant subject headings elsewhere in these minutes, as the Board meeting is usually only one part of the GAC’s handling of an issue at an ICANN meeting):

  • 2-character country/territory codes at the second level.

This issue was discussed at length in meetings with the Generic Names Supporting Organisation (GNSO) and the ICANN Board. 

As has been the case previously, some GAC members have serious concerns about the Board’s approach to this issue and ICANN’s implementation of it.  These include: Legal rights to own and control such codes being only one dimension, with political and cultural aspects being at least as important; Governments facing excessive pricing if they choose to register a code during the exclusive registration period; Processing of applications should not precede pending discussions with the relevant government; and the handling of this issue making it difficult to argue for ICANN and the multistakeholder model in other forums.

Other members do not share those concerns, and some see no problems with dot brands registrations in this space. However, there was general agreement that the Board’s response to GAC advice (including the most recent Resolution on this issue) has not been clear, and that implementation by the ICANN organisation has not addressed the concerns of a number of governments.

Members of the GNSO Council noted that current arrangements are a compromise that does not reflect the original Policy Development Process (PDP), and that Registries are not particularly happy with them either. They offered to arrange briefing for the GAC if that would help.

Board members reiterated their previous view that the Board has acted consistently with GAC advice. They offered to respond in writing to specific GAC concerns and/or to arrange discussions before the next ICANN meeting.

  • The ICANN CEO’s response to the questions in the Hyderabad Communiqué concerning mitigation of DNS abuse.
  • Confidentiality of GAC documents.
  • The Board’s new process for considering and processing GAC advice.
  • An update on the dot web auction issue.

The GAC sought an update from the Board about concerns raised by some parties about the process for the auction of the gTLD dot web. The Board confirmed that they are aware of an investigation of this issue by the US Justice Department.

  • The facilitated discussion on IGO protections and Red Cross Red Crescent protections.

GAC Members and Observers participated in a facilitated discussion on this issue, led by former ICANN Board member Bruce Tonkin. The discussion was seen as positive and constructive.  The Board supported these discussions by resolving to request the GNSO to reconsider its original PDP recommendations in light of GAC advice. This will be done in accordance with existing PDP rules.

  • CCWG-Accountability WS2.
  • GAC priorities.
  • Scheduling the regular Board-GAC post-Communiqué call for approximately 5 weeks after the Copenhagen meeting.
 
Materials:
Title
Type
Materials:
Title