<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:x="urn:schemas-microsoft-com:office:excel" 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 12 (filtered medium)"><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: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;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri","sans-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.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;color:#1F497D'>Please see below the email that Steve is referring to on the BC call.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;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;color:#1F497D'>Kind Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>Benedetta Rossi<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:#1F497D'>BC Secretariat<o:p></o:p></span></p><p class=MsoNormal><span lang=IT style='font-size:11.0pt;color:#1F497D'><a href="bc-secretariat@icann.org"><span lang=EN-US>bc-secretariat@icann.org</span></a></span><span style='font-size:11.0pt;color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=IT style='font-size:11.0pt;color:#1F497D'><a href="https://community.icann.org/display/gnsobc/Home"><span lang=EN-US>https://community.icann.org/display/gnsobc/Home</span></a></span><span style='font-size:11.0pt;color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=IT style='font-size:11.0pt;color:#1F497D'><a href="www.bizconst.org">www.bizconst.org</a><o:p></o:p></span></p><p class=MsoNormal><span lang=IT style='font-size:11.0pt;color:#1F497D'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;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=IT style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>Da:</span></b><span lang=IT style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'> owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org] <b>Per conto di </b>Steve DelBianco<br><b>Inviato:</b> vendredi 26 avril 2013 15:53<br><b>A:</b> 'bc - GNSO list'<br><b>Oggetto:</b> [bc-gnso] for discussion of BC comment on GAC Advice for new gTLDs <o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal><span style='color:black'>This is for discussion during today's BC Member call, during the Policy segment of the agenda.<o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>Background for BC comments on Beijing GAC Advice</span></b><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>Full GAC Communique and Advice from Beijing </span><span style='color:black'><a href="http://www.icann.org/en/news/correspondence/gac-to-board-18apr13-en.pdf"><span style='font-size:11.0pt;font-family:"Cambria","serif"'>here</span></a></span><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>. Initial public comments due 14-May</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>1. New gTLDs:</span></b><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>a. GAC objections to specific applications (. africa . gcc . islam . halal)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>b. Safeguards for new gTLDs (Annex 1)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>Safeguards for <u>all</u> new gTLDs</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>1. Registry does Whois verification checks 2x per year</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>2. Registrant ToS should prohibit malware, botnets, phishing, piracy, TM/copyright infringement, fraud, deception, or anything contrary to applicable law.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>3. Registry to periodically check domains in TLD for security threats (pharming, phishing, malware, botnets). Notify registrar and suspend domain if no immediate remedy.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>4. Registry to maintain stats on inaccurate Whois , security threats found, and actions taken.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>5. Registry needs mechanism to handling complaints about inaccurate Whois, security, etc.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>6. Registry must ensure immediate consequences (incl suspension) for inaccurate Whois or domain use in breach of applicable law</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>Safeguards for Category 1 gTLDs: consumer protection, sensitive strings and regulated markets (non-exhaustive list of TLDs in annex 1, page 9)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>1. . Registrant ToS should require compliance with applicable laws, incl privacy, consumer protection, fair lending, organic farming, disclsoures </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>2. Registry will require registrars to notify registrants of ToS at time of registration.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>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='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>4. Registry to establish relationship with regulators or industry self-regulatory body, plus strategy to mitigate risks of fraud & illegal activities.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>5. Registry will require registrars to have single point of contact for complaints and mitigation </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>Additional Safeguards for Category 1 gTLDs in financial, gambling, professional services, environmental, health and fitness, corporate identifiers, and charity:</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>6. Registry must verify and validate registrant authorization, charter, license or other credentials</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>7. if in doubt about credentials, Registry should consult with national supervisory authority</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>8. Registry must do periodic checks on registrant validity and compliance with above requirements.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>Safeguards for Category 2 gTLDs: restricted registration policies</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>1. Strings in Category 1 may restrict registration, appropriate to risks. Be transparent and give equal access to registrars and registrants.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>2. Generic gTLDs may have “exclusive” registry access if it serves a public interest goal. Non-exhaustive list of generic terms where applicant has proposed exclusive access:</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:72.0pt'><span style='font-size:10.0pt;color:black'>.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='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>c. For further GAC consideration (.amazon .patagonia .date .spa .yun .thai .zulu .wine .vin )</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>d. Ability for applicants to change applied-for string in order to address GACconcerns</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>-- no prior BC position. Concerns with changing strings?</span></i><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>e. Opinion of impacted community should be duly taken into account </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>-- consistent with BC support for community priority for new gTLDs (2010)</span></i><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span></i><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>f. Reconsider contention sets for singular and plural versions of the same string.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>--consistent with BC consensus discussions before and in Beijing</span></i><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>g. Initial protection for intergovernmental organization names and acronyms atsecond level</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>--no official BC position, but generally supportive of GAC;</span></i><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>--BC should support “Strawman” TMCH warning notices for IGOs -- at least until GAC review of RPMs one year after 75<sup>th</sup> gTLD is launched</span></i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>2. finalize RAA and require it for registrars selling domains in new gTLDs.</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>--consistent with BC position (Jan-2012)</span></i><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>3. GAC’s 2007 Whois Principles should be “duly taken into account” by Directory Services Expert Working Group. (Susan K)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>4. Amend registry agreement to require permanent protection of Olympics and Red Cross</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>--no official BC position, but generally supportive of GAC;</span></i><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>5. more information on Public Interest Commitments (PIC) Specifications:</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>1. can 3<sup>rd</sup> party or governments raise concern about PIC compliance?</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>2. can applicants later amend their PICs?</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>3. will ICANN make registry operators aware of their PICs?</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>4. requirements to maximize public visibility of PICs?</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>5. how to amend where a registry made no PICs? (but should have)</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>6. Are PICs enforceable?</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:72.0pt'><i><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>--BC said ICANN should enforce PICs</span></i><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>7. Will ICANN follow sanctions recommended by PIC DRP?</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'>8. Measures to remediate serious damage from past registration policies?</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div></body></html>