<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I've just been through the questionnaire for the first, and I have two overall observations.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">First, as a member of the WG, this still appears to be quite rough for something intended for distribution in two weeks.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Second, as a member (and Chair) of a SO/AC/SG/C (IPC), this is going to be an incredibly heavy lift. There are an incredible number of questions and subquestions here, and most should not be answered "off the cuff." It would be better if this were issued in pieces, though I understand how much more useful it will be to us if we have all the answers at the same time. I can't imagine the logistics and the effort involved in getting this done by my constituency on a "massively parallel" basis in any reasonable period of time. Inevitably, many questions will get short shrift in the struggle to get this done.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Good luck to all of us!</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"></p><div><p style="text-indent:0in"><span style="font-size:12.8px"><a name="UNIQUE_ID_SafeHtmlFilter_UNIQUE_ID_SafeHtmlFilter__GoBack"></a></span><b style="font-size:12.8px"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#002e62">Greg
Shatan<br>
</span></b><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">C: 917-816-6428<br>
S: gsshatan<br>Phone-to-Skype: </span><font color="#000000" face="Arial, sans-serif"><span style="font-size:13.3333px">646-845-9428<br></span></font><a href="mailto:gregshatanipc@gmail.com" style="font-family:Arial,sans-serif;font-size:10pt;text-indent:0in" target="_blank"><span style="color:#1155cc">gregshatanipc@gmail.com</span></a></p><p style="font-size:12.8px;text-indent:0in"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""></span></p></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Mon, Feb 20, 2017 at 10:51 AM, Alexander Schubert <span dir="ltr"><<a href="mailto:alexander@schubert.berlin" target="_blank">alexander@schubert.berlin</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72"><div class="m_-478475285543368382WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt">Hi WG members,<br><br>in 2.3 (Reserved Names). We in this WG are dealing with the terminology on daily basis – but not everybody we are tasking to provide feedback does. I have seen time after time people confusing the top-level and the second level when it comes to “reserved names”. For the avoidance of doubt I suggest to add for each section whether it pertains the top-level or the second level. Seems all bullet points but 2.3.5 concern top-level strings, only 2.3.5 is related to the 2<sup>nd</sup> level?<br><br>In 2.3.3 we ask: “…..should Country or Territory Names be allowed within the New gTLD Program (e.g., section 2.2.1.4.1 of the Applicant Guidebook)?”. <br>This seems to be rather unspecific. What is “e.g., section 2.2.1.4.1 of the Applicant Guidebook” be meant to say? 2.2.1.4.1 is the ONLY provision excluding ISO 3166 Alpha 3 / territory names. Why “e.g.”? That suggests there were other provisions. There are not. <br>2.2.1.4.1 was a placeholder created to postpone the decision how ISO 3166 Alpha 3 / territory names are dealt with. An entire cross community WG spent YEARS to deal with the problem – and came recently up with very little (I am member of it). This can’t be addressed in a side sentence. I suggest the following changes:<br><br>Current version:<br>“</span><span><b><i><span>For instance, should Country or Territory Names be allowed within the New gTLD Program (e.g., section 2.2.1.4.1 of the Applicant Guidebook)?</span></i></b></span><b><i>”</i></b><u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Suggested version:<u></u><u></u></p><p class="MsoNormal"><span><b><i><span>For instance, should Country </span></i></b></span><b><i>& <span><span>Territory Names</span></span> or ISO 3166 Alpha-3 code elements (as specified in <span><span>section 2.2.1.4.1 of the Applicant Guidebook</span></span>)<span><span> be allowed within the New gTLD Program</span></span>? According to the current AG version they would already automatically require government support (<span><span>2.2.1.4.2</span></span> AG). Would that be sufficient or would you suggest additional requirements (e.g. approval by the relevant ccTLD manager or GAC member)?<u></u><u></u></i></b></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Background: I have observed in WGs and ICANN sessions as well as in personal discussions with ccTLD managers and GAC members that most stakeholders are NOT aware that removing <span>section 2.2.1.4.1 of the Applicant Guidebook</span> would OF COURSE still require Government support for these strings – as they are all part of the various sections of ISO 3166! Removing <span>2.2.1.4.1</span> would NOT result in territory, country names or 3166 Alpha 3 codes being available WITHOUT government support (nor should it in my opinion). <br><br>Thanks,<br><br>Alexander Schubert<br><br><span style="font-size:11.0pt"><br><br><u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p><div><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> <a href="mailto:gnso-newgtld-wg-bounces@icann.org" target="_blank">gnso-newgtld-wg-bounces@icann.<wbr>org</a> [mailto:<a href="mailto:gnso-newgtld-wg-bounces@icann.org" target="_blank">gnso-newgtld-wg-<wbr>bounces@icann.org</a>] <b>On Behalf Of </b>Steve Chan<br><b>Sent:</b> Friday, February 17, 2017 3:47 AM<br><b>To:</b> <a href="mailto:gnso-newgtld-wg@icann.org" target="_blank">gnso-newgtld-wg@icann.org</a><br><b>Subject:</b> [Gnso-newgtld-wg] - Community Comment 2 Next Steps<u></u><u></u></span></p></div></div><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span style="font-size:11.0pt">Dear WG Members,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt">As you probably know, the WG is currently drafting its second request for community comment. The WG co-chairs and co-leaders of the work tracks encourage you to review the draft Community Comment 2 (CC2) questions and make suggestions in the document to amend language, add questions, omit questions, etc. The WG is collaborating via Google Docs, which can be found here: <a href="https://docs.google.com/document/d/1iZBCVEAJPBYEDg7jLsMHKkNczR_b6-jH2Wl5eVH-WWM/edit?usp=sharing" target="_blank">https://docs.google.com/<wbr>document/d/<wbr>1iZBCVEAJPBYEDg7jLsMHKkNczR_<wbr>b6-jH2Wl5eVH-WWM/edit?usp=<wbr>sharing</a>. Attached, please find an extract of the questions in Word, for those that are unable to access Google Docs.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt">The intention is to distribute and publish these questions for public comment before ICANN58. To do so, here is the suggested path forward:<u></u><u></u></span></p><p class="m_-478475285543368382MsoListParagraph"><u></u><span style="font-size:11.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><b><span style="font-size:11.0pt">Members review and suggest changes. Some WTs may choose to discuss during their meetings, but we hope to conclude this phase on 24 February. Your contributions are critical to ensuring your voice is heard!<u></u><u></u></span></b></p><p class="m_-478475285543368382MsoListParagraph"><u></u><span style="font-size:11.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt">The full WG reviews CC2 on 27 February. This will be considered the first reading of CC2.<u></u><u></u></span></p><p class="m_-478475285543368382MsoListParagraph"><u></u><span style="font-size:11.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt">An additional full WG meeting will be scheduled for 6 March, where CC2 will be reviewed and be considered the second, and presumably final reading. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt">Assuming agreement is reached on the 6 March meeting, CC2 would then be published for public comment, as well as distributed to the chairs of the various Stakeholder Groups, Constituencies, Supporting Organizations, and Advisory Committees. <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt">If you have any questions, please let staff or the WG leadership know.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt">Best,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt">Steve<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:10.0pt"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:10.0pt"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:10.0pt"><u></u> <u></u></span></p><p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:11.0pt">Steven Chan</span></b><span style="font-size:11.0pt;font-family:"MS Mincho"">
</span><span style="font-size:11.0pt"><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">Sr. Policy Manager</span><span style="font-size:11.0pt;font-family:"MS Mincho"">
</span><span style="font-size:11.0pt"><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt"> <u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:11.0pt">ICANN</span></b><span style="font-size:11.0pt"><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">12025 Waterfront Drive, Suite 300<u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">Los Angeles, CA 90094-2536</span><span style="font-size:11.0pt;font-family:"MS Mincho"">
</span><span style="font-size:11.0pt"><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt"><a href="mailto:steve.chan@icann.org" target="_blank"><span style="color:blue">steve.chan@icann.org</span></a><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">mobile: <a href="tel:(310)%20339-4410" value="+13103394410" target="_blank">+1.310.339.4410</a><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">office tel: <a href="tel:(310)%20301-5800" value="+13103015800" target="_blank">+1.310.301.5800</a><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">office fax: <a href="tel:(310)%20823-8649" value="+13108238649" target="_blank">+1.310.823.8649</a><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt"> <u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">Find out more about the GNSO by taking our i<a><span style="color:#57005a">nteractive courses</span></a> and visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers" target="_blank"><span style="color:#57005a">GNSO Newcomer pages</span></a>.<u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt"> <u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">Follow @GNSO on Twitter: <a href="https://twitter.com/ICANN_GNSO" target="_blank"><span style="color:#0000e3">https://twitter.com/<wbr>ICANN_GNSO</span></a><u></u><u></u></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt">Follow the GNSO on Facebook: <a href="https://www.facebook.com/icanngnso/" target="_blank">https://www.<wbr>facebook.com/icanngnso/</a> <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><a href="http://gnso.icann.org/en/" target="_blank"><span style="color:#0000e3">http://gnso.icann.org/en/</span></a><u></u><u></u></span></p></div></div></div></div><br>______________________________<wbr>_________________<br>
Gnso-newgtld-wg mailing list<br>
<a href="mailto:Gnso-newgtld-wg@icann.org">Gnso-newgtld-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-newgtld-wg</a><br></blockquote></div><br></div>