ICANN/GNSO GNSO Email List Archives

[council]


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

Re: [council] GAC Communique Review Template

  • To: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>, Council <council@xxxxxxxxxxxxxx>
  • Subject: Re: [council] GAC Communique Review Template
  • From: Stephanie Perrin <stephanie.perrin@xxxxxxxxxxxxxxxx>
  • Date: Tue, 24 Feb 2015 13:02:15 -0500
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephanie.perrin@xxxxxxxxxxxxxxxx;
  • In-reply-to: <54ECA18F.7090905@key-systems.net>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <D111FADF.3E633%marika.konings@icann.org> <54ECA18F.7090905@key-systems.net>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0

Thanks for this and thanks to Marika for doing a great job on the grid. I find myself wanting, in some cases, more clarification of the GAC comment in the communique....a column that is essentially "tell us more, we need more information, what exactly do you mean". I may be alone in that view, but I also think it would be extremely useful where the Communique contains a compromise line that does not unpack the policy issues (presumably because the issues were intractable, and they simply wanted to flag a generalized concern and not provide guidance as to how to resolve it). I could furnish some examples of these cases if needed.
Stephanie Perrin
On 2015-02-24 11:06, Volker Greimann wrote:
Dear councillors,

please find attached a proposed draft template (with examples based on the current GAC advice) of how our analysis of the GAC Communique could look like.

The "meat" of our response will obviously be centered on the last column, and this will likely have to be determined on a case by case basis depending on the content of the Communique and its impact on the GNSO.I would expect that this will require some form of inter-sessional discussion with regard to our comments there.

Any comments or suggestions are of course welcome. We will also be looking after the first round if this template has served us well or needs further refinement. As always, Marika has been of immense help putting this template together.
--

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:vgreimann@xxxxxxxxxxxxxxx

Web:www.key-systems.net  /www.RRPproxy.netwww.domaindiscount24.com  
/www.BrandShelter.com

Follow us on Twitter or join our fan community on Facebook and stay updated:
www.facebook.com/KeySystemswww.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
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.








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