<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<base href="x-msg://150/">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
I have been attempting to review the new RAA and am about to give up. I have spent the better part of 12 hours on planes, sleepless nights in hotels, and other "down time" trying to make sense of the new RAA missive.
<div><br>
</div>
<div>The document is now some 42 pages in length supplemented by nearly 25 pages of specifications representing a rough tripling of the volume of information that must be reviewed. Various buts of information contained within both the agreement and specifications
are intricately worded with numerous cross references, exceptions, and other provisos. It may become the quintessential example of how not to structure or author a legal agreement.</div>
<div><br>
</div>
<div>Registrants need not worry since the changes to section 3.7.7 are relatively minor and easy to understand. That section is somewhat out of place in what I find an otherwise inscrutable document. On the down side, registrants gain no useful "rights" and
in fact will be forced to abandon important rights if ICANN and the registrars enter into this agreement.</div>
<div><br>
</div>
<div>A new concept, <i>The Working Group</i>, has been introduced and will no doubt be positioned as an efficiency enhancing mechanisms to effect RAA change. That is entirely possible as is the potential disenfranchisement of registrants and registries with
respect to registrar-related policies. <i>The Working Group</i> will consist of representatives of the "Applicable Registrars and other members of the community that the Registrar Stakeholder Group appoints from time to time".</div>
<div><br>
</div>
<div>This explains why several members of the registrar community have said to me that I (and I now suspect no other non-registrar) will ever sit in on a discussion/negotiation of the RAA. This is not and can not be considered a multi-stakeholder approach.</div>
<div><br>
</div>
<div>I have also read, and attempted to understand how the new WHOIS requirements will enhance accuracy and consequently mitigate the well-documented issues of using WHOIS to seek corrective action for a range of detrimental or malevolent actions. At this time,
I believe the provisions in the proposed RAA, if implemented, may do little to help. I also suspect it may be possible for registrars to indefinitely postpone implementation of some of the provisions. One way to interpret the language suggest that to be the
case. Another reading would set a time limit of 1 January 2014.</div>
<div><br>
</div>
<div>It also appears that bulk access to WHOIS data will be effectively eliminated.</div>
<div><br>
</div>
<div>Much of what I see implemented in the proposed RAA was never discussed within the ICANN Community. Provisions, really policy, seems to have been invented out of whole cloth with little regard for ICANN's supposed bottoms-up, consensus-based, multi-stakeholder
model.</div>
<div><br>
</div>
<div>I fear we will have this agreement for some time to come. I further fear that registrants are losing important rights. Lastly, I am more convinced that ICANN is operating not in the public interest but rather in the interest of contracted parties - including
themselves.</div>
<div><br>
</div>
<div>Preparing a well-reasoned response to the proposed RAA would require resources beyond those available to the BC or any other member of "the public". Without such a review, about all I can recommend is that we propose to start over from a blank sheet and
attempt to develop a document that is simple, understandable, and consistent with the principles of this Community</div>
<div>
<div><br>
<div>
<div>On Apr 26, 2013, at 8:54 AM, Marilyn Cade <<a href="mailto:marilynscade@hotmail.com">marilynscade@hotmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div class="hmmessage" style="font-size: 12pt; font-family: Calibri; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<div dir="ltr">Anjali,
<div>Would it possibly be useful to have a 45 min call with interested members to assist? so many of us are drowning in other items that drafting may escape us,but I could join a brief call.</div>
<div><br>
</div>
<div>I take note that this is now a fairly complex updated document, and that is helpful to share views?</div>
<div><br>
</div>
<div>Not sure if that is useful to your rapporteur efforts, but I can join a call if that is helpful. Probably can't do drafting. </div>
<div><br>
</div>
<div>I agree that the 'improved' RAA is quite important for the BC members. Maybe Steve could also tell us what /whether the BC's scorecard issues were met, which might help define some input.</div>
<div><br>
</div>
<div>Marilyn <br>
<br>
<div>
<div id="SkyDrivePlaceholder"></div>
<hr id="stopSpelling">
From: <a href="mailto:AHansen@council.bbb.org">AHansen@council.bbb.org</a><br>
To: <a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>; <a href="mailto:bc-gnso@icann.org">
bc-gnso@icann.org</a><br>
Subject: [bc-gnso] Also for discussion of BC comment on RAA<span class="Apple-converted-space"> </span><br>
Date: Fri, 26 Apr 2013 14:30:23 +0000<br>
<br>
<div class="ecxWordSection1">
<div style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; ">All,</span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; ">I volunteered to draft comments for the BC on the proposed revisions to the RAA. As Steve noted, ICANN recently released an updated version of the RAA,
which may address some of the BC members’ prior concerns. See ICANN’s issues memo (attached) on the latest revisions as a summary.</span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; ">If any of you have had the chance to look at the latest version and can provide input today at our meeting, that would be great. However, comments are
now not due until May 13, so I would welcome your written comments by next Thursday. I can then circulate a draft of the comments to everyone by end of next week.</span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; ">There are a lot of specifications that need to be looked at as well. Here is the link: <a href="http://www.icann.org/en/news/public-comment/proposed-raa-22apr13-en.htm" target="_blank">http://www.icann.org/en/news/public-comment/proposed-raa-22apr13-en.htm</a></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; ">I had no idea what I was taking on when I volunteered for this project! I will be greatly relying on everyone’s input.</span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; ">Thank you and talk with you soon,</span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; ">Anjali</span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; "> </span></p>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; "></span></p>
<div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; color: maroon; ">Anjali Karina Hansen</span><span style="font-size: 7.5pt; font-family: Verdana, sans-serif; color: rgb(31, 73, 125); "> </span><span style="font-size: 8pt; font-family: Verdana, sans-serif; "> <i>Deputy
General Counsel</i></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 8pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><b><span style="font-size: 8pt; font-family: Verdana, sans-serif; ">Tel: 703-247-9340</span></b><span style="font-size: 8pt; font-family: Verdana, sans-serif; "></span></div>
<div style="margin: 0px; padding: 0px; "><b><span style="font-size: 8pt; font-family: Verdana, sans-serif; ">Fax: 703-276-0634</span></b><span style="font-size: 8pt; font-family: Verdana, sans-serif; "></span></div>
<div style="margin: 0px; padding: 0px; "><b><span style="font-size: 8pt; font-family: Verdana, sans-serif; ">Email:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 8pt; font-family: Verdana, sans-serif; "><a href="mailto:ahansen@council.bbb.org"><b><span style="color: windowtext; ">ahansen@council.bbb.org</span></b></a></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 8pt; font-family: Verdana, sans-serif; "><a href="http://www.bbb.org/" target="_blank"><b><span style="color: windowtext; ">bbb.org</span></b></a><b><span class="Apple-converted-space"> </span> Start
With Trust<i><sup>®</sup></i></b></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 8pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 8pt; font-family: Verdana, sans-serif; ">Council of Better Business Bureaus, Inc.</span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 8pt; font-family: Verdana, sans-serif; ">3033 Wilson Boulevard, Suite 600</span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 8pt; font-family: Verdana, sans-serif; ">Arlington, VA 22201</span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 8pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><b><span style="font-size: 8pt; font-family: Verdana, sans-serif; ">For consumer tips, scams and alerts:</span></b><span style="font-size: 8pt; font-family: Verdana, sans-serif; "><span class="Apple-converted-space"> </span><a href="http://www.bbb.org/blog/" title="http://www.bbb.org/us/blog/" target="_blank"><span style="color: windowtext; ">Read
our blog<b><br>
</b></span></a><b>Find us on:<span class="Apple-converted-space"> </span><a href="http://www.twitter.com/bbb_us" title="http://www.twitter.com/bbb_us" target="_blank"><span style="color: windowtext; font-weight: normal; ">Twitter</span></a></b><span class="Apple-converted-space"> </span>|<span class="Apple-converted-space"> </span><b><a href="http://www.facebook.com/pages/Better-Business-Bureau-US/25368131403" title="http://www.facebook.com/pages/Better-Business-Bureau-US/25368131403" target="_blank"><span style="color: windowtext; font-weight: normal; ">Facebook</span></a><span class="Apple-converted-space"> </span></b>|<span class="Apple-converted-space"> </span><a href="http://www.linkedin.com/groups?about=&gid=1917928&trk=anet_ug_grppro" title="http://www.linkedin.com/groups?about=&gid=1917928&trk=anet_ug_grppro" target="_blank"><span style="color: windowtext; ">LinkedIn</span></a><span class="Apple-converted-space"> </span>|<span class="Apple-converted-space"> </span><a href="http://www.youtube.com/user/BBBconsumerTips" title="http://www.youtube.com/user/BBBVideoTips" target="_blank"><span style="color: windowtext; ">YouTube</span></a><span class="Apple-converted-space"> </span>|<span class="Apple-converted-space"> </span><a href="http://www.flickr.com/photos/bbb_us" title="http://www.flickr.com/photos/bbb_us" target="_blank"><span style="color: windowtext; ">Flickr</span></a><b></b></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 8pt; font-family: Verdana, sans-serif; "> </span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 8pt; font-family: Verdana, sans-serif; ">This message is a private communication, and may contain confidential and/or privileged information. If you have received this message by mistake, please
notify the sender by reply email and then delete the message from your system without printing, copying or forwarding it. Thank you.</span></div>
</div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; font-family: Verdana, sans-serif; "> </span></p>
<div>
<div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in; ">
<div style="margin: 0px; padding: 0px; "><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><span class="Apple-converted-space"> </span><a href="mailto:owner-bc-gnso@icann.org">owner-bc-gnso@icann.org</a>
[mailto:owner-<a href="mailto:bc-gnso@icann.org">bc-gnso@icann.org</a>]<span class="Apple-converted-space"> </span><b>On Behalf Of<span class="Apple-converted-space"> </span></b>Steve DelBianco<br>
<b>Sent:</b><span class="Apple-converted-space"> </span>Friday, April 26, 2013 9:53 AM<br>
<b>To:</b><span class="Apple-converted-space"> </span>'bc - GNSO list'<br>
<b>Subject:</b><span class="Apple-converted-space"> </span>[bc-gnso] for discussion of BC comment on GAC Advice for new gTLDs</span></div>
</div>
</div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "> </p>
<div>
<div style="margin: 0px; padding: 0px; "><span style="">This is for discussion during today's BC Member call, during the Policy segment of the agenda.</span></div>
</div>
<div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style=""> </span></p>
</div>
<div>
<div style="margin: 0px; padding: 0px; "><b><span style="font-size: 11pt; font-family: Cambria, serif; ">Background for BC comments on Beijing GAC Advice</span></b><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">Full GAC Communique and Advice from Beijing<span class="Apple-converted-space"> </span></span><span style=""><a href="http://www.icann.org/en/news/correspondence/gac-to-board-18apr13-en.pdf" target="_blank"><span style="font-size: 11pt; font-family: Cambria, serif; ">here</span></a></span><span style="font-size: 11pt; font-family: Cambria, serif; ">.
Initial public comments due 14-May</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "></span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><b><span style="font-size: 11pt; font-family: Cambria, serif; ">1. New gTLDs:</span></b><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">a. GAC objections to specific applications (. africa . gcc . islam . halal)</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">b. Safeguards for new gTLDs (Annex 1)</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">Safeguards for<span class="Apple-converted-space"> </span><u>all</u><span class="Apple-converted-space"> </span>new gTLDs</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">1. Registry does Whois verification checks 2x per year</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">2. Registrant ToS should prohibit malware, botnets, phishing, piracy, TM/copyright infringement, fraud, deception, or anything contrary to applicable law.</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">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=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">4. Registry to maintain stats on inaccurate Whois , security threats found, and actions taken.</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">5. Registry needs mechanism to handling complaints about inaccurate Whois, security, etc.</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">6. Registry must ensure immediate consequences (incl suspension) for inaccurate Whois or domain use in breach of applicable law</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">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=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">1. . Registrant ToS should require compliance with applicable laws, incl privacy, consumer protection, fair lending, organic farming, disclsoures</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">2. Registry will require registrars to notify registrants of ToS at time of registration.</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, 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=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, 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=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">5. Registry will require registrars to have single point of contact for complaints and mitigation</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">Additional Safeguards for Category 1 gTLDs in financial, gambling, professional services, environmental, health and fitness, corporate identifiers, and charity:</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">6. Registry must verify and validate registrant authorization, charter, license or other credentials</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">7. if in doubt about credentials, Registry should consult with national supervisory authority</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">8. Registry must do periodic checks on registrant validity and compliance with above requirements.</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">Safeguards for Category 2 gTLDs: restricted registration policies</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">1. Strings in Category 1 may restrict registration, appropriate to risks. Be transparent and give equal access to registrars and registrants.</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">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=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 10pt; ">.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=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">c. For further GAC consideration (.amazon .patagonia .date .spa .yun .thai .zulu .wine .vin )</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">d. Ability for applicants to change applied-for string in order to address GACconcerns</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><i><span style="font-size: 11pt; font-family: Cambria, serif; ">-- no prior BC position. Concerns with changing strings?</span></i><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">e. Opinion of impacted community should be duly taken into account</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><i><span style="font-size: 11pt; font-family: Cambria, serif; ">-- consistent with BC support for community priority for new gTLDs (2010)</span></i><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><i><span style="font-size: 11pt; font-family: Cambria, serif; "> </span></i><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">f. Reconsider contention sets for singular and plural versions of the same string.</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><i><span style="font-size: 11pt; font-family: Cambria, serif; ">--consistent with BC consensus discussions before and in Beijing</span></i><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">g. Initial protection for intergovernmental organization names and acronyms atsecond level</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><i><span style="font-size: 11pt; font-family: Cambria, serif; ">--no official BC position, but generally supportive of GAC;</span></i><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><i><span style="font-size: 11pt; font-family: Cambria, serif; ">--BC should support “Strawman” TMCH warning notices for IGOs -- 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: 11pt; font-family: Cambria, serif; ">.</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">2. finalize RAA and require it for registrars selling domains in new gTLDs.</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><i><span style="font-size: 11pt; font-family: Cambria, serif; ">--consistent with BC position (Jan-2012)</span></i><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">3. GAC’s 2007 Whois Principles should be “duly taken into account” by Directory Services Expert Working Group. (Susan K)</span><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">4. Amend registry agreement to require permanent protection of Olympics and Red Cross</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><i><span style="font-size: 11pt; font-family: Cambria, serif; ">--no official BC position, but generally supportive of GAC;</span></i><span style=""></span></div>
<p class="ecxMsoNormal" style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; "> </span><span style=""></span></p>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">5. more information on Public Interest Commitments (PIC) Specifications:</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">1. can 3<sup>rd</sup><span class="Apple-converted-space"> </span>party or governments raise concern about PIC compliance?</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">2. can applicants later amend their PICs?</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">3. will ICANN make registry operators aware of their PICs?</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">4. requirements to maximize public visibility of PICs?</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">5. how to amend where a registry made no PICs? (but should have)</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">6. Are PICs enforceable?</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><i><span style="font-size: 11pt; font-family: Cambria, serif; ">--BC said ICANN should enforce PICs</span></i><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">7. Will ICANN follow sanctions recommended by PIC DRP?</span><span style=""></span></div>
<div style="margin: 0px; padding: 0px; "><span style="font-size: 11pt; font-family: Cambria, serif; ">8. Measures to remediate serious damage from past registration policies?</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>