RE: [gnso-policyimpl-wg] Fwd: [IPC Discussion List] FW: [council] Moving ahead on the GAC communique

["Michael Graham (ELCA)" <migraham@xxxxxxxxxxx>]

Greg:

My thought exactly.  Perhaps one of the new processes we are discussing might 
be applicable to aid this process?

Michael R.

Michael R. Graham
Senior Corporate Counsel, Intellectual Property
Expedia Legal & Corporate Affairs
T +1 425.679.4330 | F +1 425.679.7251
M +1 425.241.1459
Expedia, Inc.
333 108th Avenue NE | Bellevue | WA 98004
MiGraham@xxxxxxxxxxx<mailto:MiGraham@xxxxxxxxxxx>
CONFIDENTIALITY NOTICE: This electronic message may contain private, 
confidential, and privileged material for the sole use of the intended 
recipient. Any review, copying, or distribution of this message by others is 
strictly prohibited. If you are not the intended recipient, please (i) contact 
the sender immediately; and (ii) permanently delete the original and any copies 
of the message including file attachments.  Thank you for your cooperation.


From: owner-gnso-policyimpl-wg@xxxxxxxxx 
[mailto:owner-gnso-policyimpl-wg@xxxxxxxxx] On Behalf Of Greg Shatan
Sent: Wednesday, December 03, 2014 11:17 PM
To: gnso-policyimpl-wg@xxxxxxxxx
Subject: [gnso-policyimpl-wg] Fwd: [IPC Discussion List] FW: [council] Moving 
ahead on the GAC communique

I wanted to bring the proposal below to the attention of our group, to consider 
how it dovetails (or doesn't) with both the issues and the mechanisms we are 
dealing with.
Greg
---------- Forwarded message ----------

________________________________
From: owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx> 
[owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>] on behalf 
of Volker Greimann [vgreimann@xxxxxxxxxxxxxxx]
Sent: Thursday, 4 December 2014 5:15
To: Council
Subject: [council] Moving ahead on the GAC communique

As discussed during the last council meeting, one of our action items is for 
the Council to 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.

In the discussion, a 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é.

As a framework for discussion, the following steps are suggested:

1) GAC publishes its communique
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
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.

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

Potential responses could be:
- Council recommends initiation of new policy work based on GAC advice

- 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

- Council recommends revisiting prior PDP to analyse and deliberate the impact 
of suggested advice on existing policy.

- Council advises Board that existing policy already covers [suggestion] and 
[suggestion] is a mere question of implementation of said policy

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.

--

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<tel:%2B49%20%280%29%206894%20-%209396%20901>

Fax.: +49 (0) 6894 - 9396 851<tel:%2B49%20%280%29%206894%20-%209396%20851>

Email: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>



Web: www.key-systems.net<http://www.key-systems.net> / 
www.RRPproxy.net<http://www.RRPproxy.net>

www.domaindiscount24.com<http://www.domaindiscount24.com> / 
www.BrandShelter.com<http://www.BrandShelter.com>



Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:

www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>

www.twitter.com/key_systems<http://www.twitter.com/key_systems>



Geschäftsführer: Alexander Siffrin

Handelsregister Nr.: HR B 18835 - Saarbruecken

Umsatzsteuer ID.: DE211006534



Member of the KEYDRIVE GROUP

www.keydrive.lu<http://www.keydrive.lu>



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<tel:%2B49%20%280%29%206894%20-%209396%20901>

Fax.: +49 (0) 6894 - 9396 851<tel:%2B49%20%280%29%206894%20-%209396%20851>

Email: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>



Web: www.key-systems.net<http://www.key-systems.net> / 
www.RRPproxy.net<http://www.RRPproxy.net>

www.domaindiscount24.com<http://www.domaindiscount24.com> / 
www.BrandShelter.com<http://www.BrandShelter.com>



Follow us on Twitter or join our fan community on Facebook and stay updated:

www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>

www.twitter.com/key_systems<http://www.twitter.com/key_systems>



CEO: Alexander Siffrin

Registration No.: HR B 18835 - Saarbruecken

V.A.T. ID.: DE211006534



Member of the KEYDRIVE GROUP

www.keydrive.lu<http://www.keydrive.lu>



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.