<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";
color:black;
mso-fareast-language:EN-US;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Thanks Volker and thanks Mikey,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I had to do that one quickly as there was a print deadline.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>However, I will update the front page of the gnso.ican.org website with a comment / blog post.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I’ll aim to weave in your input to the what to watch out for.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Jonathan<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-GB'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-GB'> Volker Greimann [mailto:vgreimann@key-systems.net] <br><b>Sent:</b> 11 March 2014 15:19<br><b>To:</b> jrobinson@afilias.info; council@gnso.icann.org<br><b>Subject:</b> Re: [council] ICANN Singapore : What to watch out for<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Jonathan,<br><br>maybe we also want to highlight the issue of the strategy panels and the role of the GNSO with regard to the internet governance forums, such as:<br><br>A further current subject for deliberation within the GNSO is its involvement in current discussions of the future of internet governance in various fora and the impact of the ICANN strategy panels on the work and role of the GNSO.<br><br>Not quite happy with the language yet, but I wanted to throw something out just as a starting point.<br><br>Volker<br><br><br><br><o:p></o:p></p><div><p class=MsoNormal>Am 11.03.2014 10:29, schrieb Jonathan Robinson:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>All,<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I was asked with relatively short notice to provide content for the meeting guide in a “What to watch out for” format. <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Please see the following for what I have provided:<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>The GNSO is the body within ICANN that is charged with developing policy for generic domain names and the GNSO Council is responsible for managing that policy development. The GNSO Council work commences ahead of the main meeting schedule, typically with our GNSO working sessions over the weekend. As with almost everything we do, these are open to all within the GNSO and indeed the wider ICANN community. You are welcome! On Saturday we are typically are focussed on interaction with GNSO Working Groups and then on Sunday with other key groups such as the ICANN Board and the Government Advisory Committee (GAC). Working Groups are comprised of dedicated volunteers with an interest in the specific topic being tackled and are open to all from the outset. They are the backbone of GNSO policy making and, as the name readily suggests, where the work is actually undertaken. With respect to interaction with other groups, effective interaction between the GNSO policy work and the GAC has emerged as a key area for potential improvement and development. At the Singapore meeting we will see the joint GNSO/GAC Consultation Group report on its work during the joint GNSO/GAC meeting on Sunday.</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Jonathan<o:p></o:p></p></blockquote><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-language:EN-GB'><br><br><o:p></o:p></span></p><pre>-- <o:p></o:p></pre><pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Mit freundlichen Grüßen,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Volker A. Greimann<o:p></o:p></pre><pre>- Rechtsabteilung -<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Key-Systems GmbH<o:p></o:p></pre><pre>Im Oberen Werk 1<o:p></o:p></pre><pre>66386 St. Ingbert<o:p></o:p></pre><pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre><pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre><pre>Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Web: <a href="http://www.key-systems.net">www.key-systems.net</a> / <a href="http://www.RRPproxy.net">www.RRPproxy.net</a><o:p></o:p></pre><pre><a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com">www.BrandShelter.com</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre><pre><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><o:p></o:p></pre><pre><a href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre><pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre><pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre><pre><a href="http://www.keydrive.lu">www.keydrive.lu</a> <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>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.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>--------------------------------------------<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Best regards,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Volker A. Greimann<o:p></o:p></pre><pre>- legal department -<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Key-Systems GmbH<o:p></o:p></pre><pre>Im Oberen Werk 1<o:p></o:p></pre><pre>66386 St. Ingbert<o:p></o:p></pre><pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre><pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre><pre>Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Web: <a href="http://www.key-systems.net">www.key-systems.net</a> / <a href="http://www.RRPproxy.net">www.RRPproxy.net</a><o:p></o:p></pre><pre><a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com">www.BrandShelter.com</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre><pre><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><o:p></o:p></pre><pre><a href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>CEO: Alexander Siffrin<o:p></o:p></pre><pre>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre><pre>V.A.T. ID.: DE211006534<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre><pre><a href="http://www.keydrive.lu">www.keydrive.lu</a> <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>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.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre></div></body></html>