<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-15">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-15">
<p style="margin-bottom: 0cm"><font face="Arial, sans-serif"><font
size="3"><span lang="en-US">As discussed during the last
council meeting, one of our action items is for the Council
to </span></font></font><font face="Arial, sans-serif"><font
size="3"><span lang="en-US">examine ways in which the GAC
communiqués can be channeled
through the ICANN Board to the GNSO Council where they can
be
analyzed for possible policy implications arising from the
recommendations, and where the GNSO Council can report back
to the
ICANN Board with a proposed method of responding to the
communiqué
and initiating policy work if there be a need.</span></font></font></p>
<p style="margin-bottom: 0cm">In the discussion, a <font
face="Arial, sans-serif"><font size="3"><span lang="en-US">lightweight
and informal process was proposed where a call for topics
would be put out to the various GNSO constituencies and
stakeholder
groups and these would be sent in the form a letter by the
Council,
within 30 to 60 days upon receipt of a GAC communiqué, to
the Board
responding to that communiqué.</span></font></font></p>
<p style="margin-bottom: 0cm" lang="en-US">As a framework for
discussion, the following steps are suggested:<br>
</p>
<p style="margin-bottom: 0cm" lang="en-US">1) GAC publishes its
communique<br>
1b) optional: The ICANN board informs the GNSO council about the
Communique and requests an analysis of the communique for issues
that touch upon ongoing or new policy work<br>
2) 1st post-meeting council session: The Council deliberates the
GAC communique and instructs councillors take the communique to
their stakeholder groups and constituencies for analysis of
whether and if so how the communique touches upon, complements or
contradicts existing policy, whether it impacts ongoing policy
work or whether it suggests the initiation of new policy work.
This review should exclude any opinion on such policy and be
limited to the analysis whether policy would be affected and
therefore should be obtainable within a turn-around time of 2
weeks.<br>
</p>
<p style="margin-bottom: 0cm" lang="en-US">3) 2nd post-meeting
council session: The GNSO council deliberates input and drafts a
letter to the ICANN board including a proposed response to the GAC<br>
</p>
<p style="margin-bottom: 0cm" lang="en-US">Potential responses could
be: <br>
- Council recommends initiation of new policy work based on GAC
advice<br>
</p>
<p style="margin-bottom: 0cm" lang="en-US">- Council recommends
informing the GAC that [suggestion] has been deliberated during
previous or ongoing policy work and has been
[accepted/rejected/partially accepted] by the community</p>
<p style="margin-bottom: 0cm" lang="en-US">- Council recommends
revisiting prior PDP to analyse and deliberate the impact of
suggested advice on existing policy.</p>
<p style="margin-bottom: 0cm" lang="en-US">- Council advises Board
that existing policy already covers [suggestion] and [suggestion]
is a mere question of implementation of said policy<br>
</p>
<p style="margin-bottom: 0cm" lang="en-US">I am shooting from the
hip here to put up a straw man, so if anyone would like to add to
these suggestions or suggest a different approach, the floor is
yours.<br>
</p>
<style type="text/css"></style>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
</pre>
</body>
</html>