<html><head></head><body bgcolor="#FFFFFF"><div><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><font class="Apple-style-span" face="Helvetica"><span class="Apple-style-span" style="font-size: 17px;">I'm sorry if my email request was unclear. I was referencing the below resolved(s) from the 6 October resolution:<o:p></o:p></span></font></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><o:p style="font-size: 17px;"><font class="Apple-style-span" face="Helvetica"> </font></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><o:p style="font-size: 17px;"><font class="Apple-style-span" face="Helvetica"> </font></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><font class="Apple-style-span" face="Helvetica"><span class="Apple-style-span" style="font-size: 17px;">RESOLVED, the GNSO Council requests an Issues Report on the following possible policy revisions and/or additions:<o:p></o:p></span></font></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><o:p style="font-size: 17px;"><font class="Apple-style-span" face="Helvetica"> </font></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><font class="Apple-style-span" face="Helvetica"><span class="Apple-style-span" style="font-size: 17px;">1. ICANN-accredited registrars must provide to ICANN staff, and ICANN staff must keep on record, a valid physical address for the purpose of receiving legal service. This record must include a valid street address, city, appropriate region, telephone number and fax number.<o:p></o:p></span></font></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><o:p style="font-size: 17px;"><font class="Apple-style-span" face="Helvetica"> </font></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><font class="Apple-style-span" face="Helvetica"><span class="Apple-style-span" style="font-size: 17px;">Registrars must publish this information on their respective web sites, and must notify ICANN staff and update their published addresses within 30 days of a change of address.<o:p></o:p></span></font></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><o:p style="font-size: 17px;"><font class="Apple-style-span" face="Helvetica"> </font></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><font class="Apple-style-span" face="Helvetica"><span class="Apple-style-span" style="font-size: 17px;">2. ICANN-accredited registrars must provide to ICANN staff, and ICANN staff must keep on record, the names of each registrar's respective corporate President, Vice President, and Secretary, or the appropriate equivalents of those positions. These data may be made available upon request to a verified representative of a law enforcement agency, in a manner agreed to by ICANN staff, ICANN-accredited registrars, and representatives of law enforcement agencies. Registrars will notify ICANN of any changes in this information within 30 days of a change.<o:p></o:p></span></font></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><o:p style="font-size: 17px;"><font class="Apple-style-span" face="Helvetica"> </font></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><font class="Apple-style-span" face="Helvetica"><span class="Apple-style-span" style="font-size: 17px;">3. ICANN-accredited registrars must publish on their respective web sites e-mail and postal mail addresses to which law enforcement actions may be directed. The e-mail address will use a uniform convention<o:p></o:p></span></font></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><o:p style="font-size: 17px;"><font class="Apple-style-span" face="Helvetica"> </font></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><font class="Apple-style-span" face="Helvetica"><span class="Apple-style-span" style="font-size: 17px;">(example: <a href="mailto:lawenforcement@example.tld" x-apple-data-detectors="true" x-apple-data-detectors-result="1" style="text-decoration: underline; ">lawenforcement@example.tld</a>) to facilitate ease of use by law enforcement agencies. Registrars may, at their individual discretion, include language in this section of their web sites, directed to the general public, that makes clear the use and expected outcomes of these points of contact and identifies the appropriate points of contact for other forms of business. Requests submitted by verified law enforcement agencies to this discrete point of contact must receive an acknowledgement of receipt from the registrar within 24 hours.<o:p></o:p></span></font></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><o:p style="font-size: 17px;"><font class="Apple-style-span" face="Helvetica"> </font></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><font class="Apple-style-span" face="Helvetica"><span class="Apple-style-span" style="font-size: 17px;">4. Law enforcement agencies provide, within six months of the date of approval of this policy by the ICANN Board and via the general advice of the GAC to the Board, their recommendations for a database and identification system that allows for expedient identification to a registrar of a law enforcement agency, and verification of the contacting party as a law enforcement agency upon that agency's first contact with a registrar.<o:p></o:p></span></font></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><o:p style="font-size: 17px;"><font class="Apple-style-span" face="Helvetica"> </font></o:p></p><p class="MsoNormal" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; "><font class="Apple-style-span" face="Helvetica"><span class="Apple-style-span" style="font-size: 17px;">5. The Issue Report should include a freedom-of-expression impact analysis.</span></font></p><br><div><br></div><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.289062); -webkit-composition-fill-color: rgba(175, 192, 227, 0.222656); -webkit-composition-frame-color: rgba(77, 128, 180, 0.222656); ">Brian J. Winterfeldt, Esq.</span></div><div>Steptoe & Johnson LLP</div><div>1330 Connecticut Avenue, NW</div><div>Washington, DC 20036</div><div>TEL 202.429.6260 | FAX 202.261.7547</div><div><a href="mailto:bwinterfeldt@steptoe.com">bwinterfeldt@steptoe.com</a></div><div> </div><div>The information contained in this e-mail may be privileged, confidential, and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this e-mail message in error, please e-mail the sender at “bwinterfeldt@steptoe.com.” Thank you.<span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.289062); -webkit-composition-fill-color: rgba(175, 192, 227, 0.222656); -webkit-composition-frame-color: rgba(77, 128, 180, 0.222656); "> </span></div></div><div><br>On Oct 27, 2011, at 11:54 AM, "Neuman, Jeff" <<a href="mailto:Jeff.Neuman@neustar.us">Jeff.Neuman@neustar.us</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle19
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]--><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Brian,<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>Which Issue Report are you referring to?<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><div><p class="MsoNormal" style="margin-top:6.0pt;mso-margin-bottom-alt:auto"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D">Jeffrey J. Neuman</span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#3366FF"> <br></span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#068658">Neustar, Inc. / Vice President, Law & Policy</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D"><br><br></span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:red"><o:p></o:p></span></p><p class="MsoNormal" style="margin-top:6.0pt;mso-margin-bottom-alt:auto"><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"><o:p> </o:p></span></p><div><div><div><div><div><div><div><div class="MsoNormal"><span style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:gray"><hr size="1" width="100%" noshade="" style="color:#969696" align="left"></span></div></div></div></div></div></div></div></div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:6.5pt;font-family:"Arial","sans-serif";color:gray">The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.</span><span style="color:#1F497D"><o:p></o:p></span></p><p class="MsoNormal" style="margin-top:6.0pt;mso-margin-bottom-alt:auto"><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"><o:p> </o:p></span></p></div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:owner-council@gnso.icann.org">owner-council@gnso.icann.org</a> [mailto:owner-council@gnso.icann.org] <b>On Behalf Of </b>Winterfeldt, Brian<br><b>Sent:</b> Thursday, October 27, 2011 11:48 AM<br><b>To:</b> Stéphane Van Gelder<br><b>Cc:</b> Council GNSO<br><b>Subject:</b> Re: [council] Wrap-up topics<o:p></o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><div><p class="MsoNormal" style="margin-bottom:12.0pt">Thank you Stéphane. May I request that next steps on the RAA issue report be added to the wrap up agenda? It would probably assist Staff to know how to approach writing it, or whether the need for it has been superseded by subsequent events.<o:p></o:p></p><div><p class="MsoNormal">Thank you,<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Brian<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><span class="apple-style-span">Brian J. Winterfeldt, Esq.</span><o:p></o:p></p></div><div><p class="MsoNormal">Steptoe & Johnson LLP<o:p></o:p></p></div><div><p class="MsoNormal">1330 Connecticut Avenue, NW<o:p></o:p></p></div><div><p class="MsoNormal">Washington, DC 20036<o:p></o:p></p></div><div><p class="MsoNormal">TEL 202.429.6260 | FAX 202.261.7547<o:p></o:p></p></div><div><p class="MsoNormal"><a href="mailto:bwinterfeldt@steptoe.com">bwinterfeldt@steptoe.com</a><o:p></o:p></p></div><div><p class="MsoNormal"> <o:p></o:p></p></div><div><p class="MsoNormal">The information contained in this e-mail may be privileged, confidential, and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this e-mail message in error, please e-mail the sender at “bwinterfeldt@steptoe.com.” Thank you.<span class="apple-style-span"> </span><o:p></o:p></p></div></div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>On Oct 27, 2011, at 9:48 AM, "Stéphane Van Gelder" <<a href="mailto:stephane.vangelder@indom.com">stephane.vangelder@indom.com</a>> wrote:<o:p></o:p></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal">Councillors,<o:p></o:p></p><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">As you know, our ICANN meeting wrap-up sessions do not have a set agenda, as they are discussions and stock-taking sessions.<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">As pointers to those discussions, here are a few topics we might like to consider. These are just suggestions stemming from the notes I have been taking throughout the week. We don't have to discuss them all during the wrap-up, and we can obviously add or delete topics as desired.<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">See you all in Salon Vert room from 12:30 to 2pm today.<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Stéphane<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">IOC Red Cross, working with the GAC</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">A letter has been drafted, to be sent by GNSO Council Chair to GAC Chair. Edits/comments? Should we send?</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Best practices</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Where to next? What does the Council want to do now?</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">JAS Final report</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">What do we want to do now? We reserved our right to approve it in the resolution we passed and we heard from Kurt on Sunday that Staff would now like some direction from the GNSO Council on whether we approve it or not.</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">NCA</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Discussion of possible interactions between the Council and the NomCom going forward (see notes from meeting between NomCom and GNSO leadership earlier this week).</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Cross-TLD registration scam and domain kiting</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">See response from SSAC Chair Patrik Faltstrom sent to Council list this week. Next steps for the Council?</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">ccNSO</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Suggestions from the ccNSO to have work sessions together on looking at the strategic plan. Our response?</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">A suggestion that the GNSO joins the ccNSO in requesting extra detail from the CFO on the budget.</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Meetings: how do we strengthen our meetings with the ccNSO? How do we build the agenda in an effective way? The ccNSO has dedicated 2 people to looking at the agenda. The suggestion is that the GNSO agenda person liaise with them.</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Post newgTLD landscape</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Should the GNSO Council be looking at how the community will change as a result of new gTLDs and VI and ccNSO registries providing new gTLD services and vice-versa?</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Costa Rica preparation</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Who will handle the agenda?</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Open Council meeting: Presentations by SG and C chairs at the start of the open council meeting. A suggestion to post a list of topics to the constituency list prior to the Open Council meeting so that the group leaders know what they are going to discuss…</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">GNSO teleconference schedule for the upcoming year</span><o:p></o:p></p><p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Secretariat to suggest a schedule, to be approved by Leadership team.</span><o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div></div></blockquote></div></div></blockquote></body></html>