<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 HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@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 lang=EN-GB link=blue vlink=purple><div class=WordSection1><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></div></body></html>