ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

[council] Re: GNSO Review of the Dublin GAC Communique Template

  • To: <gnso.secretariat@xxxxxxxxxxxxxx>, Marika Konings <marika.konings@xxxxxxxxx>, "'Volker Greimann'" <vgreimann@xxxxxxxxxxxxxxx>, "David (dave@xxxxxxxxxxxxxxxxx) (dave@xxxxxxxxxxxxxxxxx)" <dave@xxxxxxxxxxxxxxxxx>, "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
  • Subject: [council] Re: GNSO Review of the Dublin GAC Communique Template
  • From: Stephanie Perrin <stephanie.perrin@xxxxxxxxxxxxxxxx>
  • Date: Mon, 9 Nov 2015 18:46:16 -0500
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephanie.perrin@xxxxxxxxxxxxxxxx;
  • In-reply-to: <D25FB904.50D1A%marika.konings@icann.org>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <D25FB904.50D1A%marika.konings@icann.org>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:23
  • User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

Colleagues, attached is a draft review of the Dublin GAC communique. I would appreciate your input and discussion on a couple of the items, where our proposed response seems to me rather unclear.
A proposed motion folllows.  Thanks to Marika for her help on this task.
Stephanie Perrin


*Adoption of the GNSO Review of GAC Communiqué for submission to the ICANN Board*

Whereas,

1. The Governmental Advisory Committee advises the ICANN Board on
   issues of public policy, and especially where there may be an
   interaction between ICANN's activities or policies and national laws
   or international agreements. It usually does so as part of a
   Communiqué, which is published towards the end of every ICANN meeting.
2. The GNSO is responsible for developing and recommending to the ICANN
   Board substantive policies relating to generic top-level domains.
3. The GNSO has expressed a desire to provide feedback to the ICANN
   Board on issues in the GAC Communiqué as these relate to generic
   top-level domains to inform the ICANN Board as well as the broader
   community of past, present or future gTLD policy activities that may
   directly or indirectly relate to advice provided by the GAC.
4. The GNSO Council developed a template to facilitate this process,
   which was completed following the publication of the Dublin GAC
   Communiqué by a volunteer and shared with the GNSO Council for its
   review
5. The GNSO hopes that the input provided through its review of the GAC
   Communiqué will further enhance the co-ordination and promote the
   sharing of information on gTLD related policy activities between the
   GAC, Board and the GNSO.

Resolved,

1. The GNSO Council adopts the GNSO Review of the Dublin GAC Communiqué
   and requests that the GNSO Council Chair communicate the GNSO Review
   of the Dublin GAC Communiqué to the ICANN Board.
2. Following the communication to the ICANN Board, the GNSO Council
   requests that the GNSO Council Chair informs the GAC Chair as well
   as the GAC-GNSO Consultation Group of the communication between the
   GNSO Council and the ICANN Board.




Attachment: GNSO Review of GAC Communique - Dublindraft1.docx
Description: Microsoft Office



<<< Chronological Index >>>    <<< Thread Index >>>