<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=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><base href="x-msg://10694/"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Cambria;
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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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-converted-space
{mso-style-name:apple-converted-space;}
span.StileMessaggioDiPostaElettronica18
{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 lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Dear BC Members,<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><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Please find below an email sent by Stephane Van Gelder which was unfortunately caught in an internal mailing list bounce and therefore did not get published on the list.<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><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>-- <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Kind Regards,<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><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Benedetta Rossi<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>BC Secretariat<o:p></o:p></span></p><p class=MsoNormal><span lang=IT style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="bc-secretariat@icann.org"><span lang=EN-US style='color:blue'>bc-secretariat@icann.org</span></a></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=IT style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="https://community.icann.org/display/gnsobc/Home"><span lang=EN-US style='color:blue'>https://community.icann.org/display/gnsobc/Home</span></a></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=IT style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="www.bizconst.org"><span style='color:blue'>www.bizconst.org</span></a><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>Le 7 mai 2013 à 11:58, Stéphane Van Gelder Consulting <<a href="mailto:stephvg@gmail.com">stephvg@gmail.com</a>> a écrit :<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>Thanks Steve, and apologies in advance as I will not be able to attend the call as I will be flying back from the Dallas INTA meeting at that time.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I have one comment on the process questions that the GAC Advice brings into focus. Without going into the detail of each point, this advice can be seen as rewriting the new gTLD program's basic rulebook at a very late stage in the game. In fact, I would argue that the GAC's Beijing Communiqué reads almost like a reboot of the GNSO recommendations and the implementation work done since then.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>At the very least, this ought to be problematic from a timing point of view. BC members just like everyone else in the community participated in the bottom-up process that led to the GNSO recommendations and then the implementation of the program based on those recommendations. They did not include many of the new rules the GAC is asking for in its Beijing advice. Is this fair to applicants and the community? Is this a predictable process?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks,<o:p></o:p></p></div><div><div><div><div><div><div><div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";color:black'><br>Stéphane Van Gelder<br>Chairman and Managing Director/Fondateur<br>STEPHANE VAN GELDER CONSULTING<br><br>T (UK): +44 (0)7583 457053<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";color:black'>T (FR): +33 (0)6 20 40 55 89<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";color:black'>Skype: SVANGELDER<br><a href="http://www.stephanevangelder.com/" target="_blank">www.StephaneVanGelder.com</a></span><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'><br></span><span style='font-size:13.5pt;font-family:"Arial","sans-serif";color:black'>----------------<br>Follow us on Twitter: @stephvg and "like" us on Facebook: <a href="http://www.facebook.com/DomainConsultant">www.facebook.com/DomainConsultant</a><br><br><o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial","sans-serif";color:black'>LinkedIn: <a name=webProfileURL></a><a href="http://fr.linkedin.com/in/domainconsultant/" title="View public profile">fr.linkedin.com/in/domainconsultant/</a><o:p></o:p></span></p></div></div></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Le 6 mai 2013 à 17:01, Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>> a écrit :<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Here is an updated outline for Wednesday's member discussion of BC comments on GAC Advice (below and attached). Under the red headings I summarized discussion from last week on the first half of the outline. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Also attached are 1-May call minutes taken by Benedetta, our Secretariat. 3rd attachment is transcript from that call. <o:p></o:p></span></p></div></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Public Comment page at <a href="http://www.icann.org/en/news/public-comment/gac-safeguard-advice-23apr13-en.htm">http://www.icann.org/en/news/public-comment/gac-safeguard-advice-23apr13-en.htm</a>.<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Initial comments due 14-May; Reply comments close 4-Jun.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Full GAC Communique and Advice is at <a href="http://www.icann.org/en/news/correspondence/gac-to-board-18apr13-en.pdf">http://www.icann.org/en/news/correspondence/gac-to-board-18apr13-en.pdf</a> <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Just the Safeguards in section IV 1.b and Annex 1 are being posted for public comment. </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>But I think the BC could also post separate comments on other GAC advice, such as Singular-Plural contention sets, Whois, etc.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'>BC commentary on GAC Advice, in general</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>BC members discussed what we would say in introductory comments. <span class=apple-converted-space> </span>Recognition that GAC has supported BC priorities on the new gTLD program. <span class=apple-converted-space> </span>Also recognition that this GAC advice includes new requirements not in the Guidebook or Registry contract. <span class=apple-converted-space> </span>Ron Andruff and Andrew Mack volunteered to draft a few paragraphs of introductory comments.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>1. New gTLDs:</span></b><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>a. GAC objections to specific applications (. africa . gcc . islam . halal)</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>b. Safeguards for<span class=apple-converted-space> </span><u>all<span class=apple-converted-space> </span></u>new gTLDs (Annex 1)</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>1. Registry does Whois verification checks 2x per year</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>2. Registrant ToS should prohibit malware, botnets, phishing, piracy, TM/copyright infringement, fraud, deception, or anything contrary to applicable law.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>3. Registry to periodically check domains in TLD for security threats (pharming, phishing, malware, botnets). <span class=apple-converted-space> </span>Notify registrar and suspend domain if no immediate remedy.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>4. Registry to maintain stats on inaccurate Whois , security threats found, and actions taken.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>5. Registry needs mechanism to handling complaints about inaccurate Whois, security, etc.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>6. Registry must ensure immediate consequences (incl suspension) for inaccurate Whois or domain use in breach of applicable law</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'>BC commentary on Safeguards for all TLDs:</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Elisa reminded BC members that we are required to take the perspective of business registrants and users/customers – even if we have other interests in new gTLDs.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>A majority of BC members on the 1-May call generally support 1.b safeguards. <span class=apple-converted-space> </span>(Ron, Anjali, David, Elisa, Sarah, Susan, Zahid)</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Subsequent discussion revealed nuances and concerns about some safeguards:</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Emmett O’Keefe believes GAC advice goes far beyond settled requirements in the final Guidebook.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Andy Abrams prefers PDPs instead of ICANN implementing these safeguards based solely on GAC advice.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Elisa noted that many of these items are already required of registrars per the proposed RAA. <span class=apple-converted-space> </span>(need to identify these items)</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Susan Kawaguchi questioned how registriescould do the security scans required in item 3.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>“Applicable law” could be extremely broad, covering laws of any nation whose registrants or users access the TLD. <span class=apple-converted-space> </span>David Fares and Sarah Deutsch pointed out that broad application of law is usually beneficial for business users and registrants.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>John Berard questions how ICANN could require these safeguards, since Guidebook and Contract are finalized. <span class=apple-converted-space> </span>Steve pointed out that registry operators can add safeguards to their Public Interest Commitments (Specification 11),provided ICANN allows updates at this point. <span class=apple-converted-space> </span>Phil Corwin responded that hundreds of unique PIC Specs would make compliance enforcement extremely difficult for ICANN.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Phil Corwin opposes the “suspension” requirement in safeguards 3 and 6 unless there were due process protections for registrants.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Safeguards for Category 1 gTLDs: consumer protection, sensitive strings and regulated markets </span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <span class=apple-converted-space> </span>(non-exhaustive list of TLDs in annex 1, page 9)</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>1. Registrant ToS should require compliance with applicable laws, incl privacy, consumer protection, fair lending, organic farming, disclosures</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>2. Registry will require registrars to notify registrants of ToS at time of registration.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>3. Registry will require registrants collecting sensitive health or financial data have reasonable security measures as defined by applicable laws and industry standards.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>4. Registry to establish relationship with regulators or industry self-regulatory body, plus strategy to mitigate risks of fraud & illegal activities.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>5. Registry will require registrants to have single point of contact for complaints and mitigation</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'>BC commentary on safeguards forCategory 1 TLDs:</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Item 3 raised concerns from most members on the call since it might be interpreted to require registries to police registrants as to their data security practices. <span class=apple-converted-space> </span>Steve DelBianco suggested that BC recommend registries be required to indicate #3 as part of the Terms of Service for registrants -- but not to require registries to police registrant practices. <span class=apple-converted-space> </span>Ron Andruff agreed, so BC will encourage ICANN to make #3 part of the ToS requirement in #1 and #2.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Jim Baskin and Susan Kawaguchi said safeguards 3 and 4 would be placing too much new responsibility on registries to monitor conduct of registrants.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Items 1 and 3 raise same comment on “applicable laws” as noted on safeguards for all TLDs (above).</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'>--remaining items to be discussed on May 8</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Additional Safeguards for Category 1 gTLDs in financial, gambling, professional services, environmental, health and fitness, corporate identifiers, and charity:</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>6. Registry must verify and validate registrant authorization, charter, license or other credentials</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>7. if in doubt about credentials, Registry should consult with national supervisory authority</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>8. Registry must do periodic checks on registrant validity and compliance with above requirements.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Safeguards for Category 2 gTLDs: restricted registration policies</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>1. Strings in Category 1 may restrict registration, appropriate to risks. <span class=apple-converted-space> </span>Be transparent and give equal access to registrars and registrants.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>2. Generic gTLDs may have “exclusive” registry access if it serves a public interest goal. <span class=apple-converted-space> </span>Non-exhaustive list of generic terms where applicant has proposed exclusive access:</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:72.0pt'><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>.antivirus, .app, .autoinsurance, .baby, .beauty, .blog, .book, .broker, .carinsurance,.cars, .cloud, .courses, .cpa, .cruise, .data, .dvr, .financialaid, .flowers, .food, .game, .grocery, .hair, .hotel, .hotels .insurance, .jewelry, .mail,.makeup, .map, .mobile, .motorcycles, .movie, .music, .news, .phone,.salon,.search, .shop, .show, .skin, .song, .store, .tennis, .theater, .theatre, .tires, .tunes, .video, .watches, .weather, .yachts</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>c. For further GAC consideration (.amazon .patagonia <span class=apple-converted-space> </span>.date <span class=apple-converted-space> </span>.spa <span class=apple-converted-space> </span>.yun <span class=apple-converted-space> </span>.thai <span class=apple-converted-space> </span>.zulu <span class=apple-converted-space> </span>.wine <span class=apple-converted-space> </span>.vin )</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>d. Ability for applicants to change applied-for string in order to address GACconcerns</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>-- no prior BC position. <span class=apple-converted-space> </span>Concerns with changing strings?</span></i><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>e. Opinion of impacted community should be duly taken into account</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>-- consistent with BC support for community priority for new gTLDs (2010)</span></i><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span></i><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>f. Reconsider contention sets for singular and plural versions of the same string.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>--consistent with BC consensus discussions before and in Beijing</span></i><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>g. Initial protection for intergovernmental organization names and acronyms atsecond level</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>--no official BC position, but generally supportive of GAC;</span></i><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>--BC should support “Strawman” TMCH warning notices for IGOs -- <span class=apple-converted-space> </span>at least until GAC review of RPMs one year after 75<sup>th</sup><span class=apple-converted-space> </span>gTLD is launched</span></i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>2. finalize RAA and require it for registrars selling domains in new gTLDs.</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>--consistent with BC position (Jan-2012)</span></i><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>3. GAC’s 2007 Whois Principles should be “duly taken into account” by Directory Services Expert Working Group. <span class=apple-converted-space> </span>(Susan K)</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>4. Amend registry agreement to require permanent protection of Olympics and Red Cross</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>--no official BC position, but generally supportive of GAC;</span></i><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>5. more information on Public Interest Commitments (PIC) Specifications:</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>1. can 3<sup>rd</sup><span class=apple-converted-space> </span>party or governments raise concern about PIC compliance?</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>2. can applicants later amend their PICs?</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>3. will ICANN make registry operators aware of their PICs?</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>4. requirements to maximize public visibility of PICs?</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>5. how to amend where a registry made no PICs? <span class=apple-converted-space> </span>(but should have)</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>6. Are PICs enforceable?</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:72.0pt'><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>--BC said ICANN should enforce PICs</span></i><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>7. Will ICANN follow sanctions recommended by PIC DRP?</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div style='margin-left:36.0pt'><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>8. Measures to remediate serious damage from past registration policies?</span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-family:"Cambria","serif"'><o:p></o:p></span></p></div></div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'><Notes for BC comments on Beijing GAC Advice.docx><Minutes BC Members call MAY 1 2013[1].pdf><BC May 1 2013.pdf><o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></blockquote></div></body></html>