<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I have also had a quick look<div> Some of the redline text is about technical matters and I do not have the expertise to comment - so need another pair of eyes. The only questions I would otherwise raised are:</div><div>In Cl 6.7, ICANN now can grant a fee waiver in its absolute discretion - without having to say why. Do we think that is a problem?</div><div>In CL 7.5- in the earlier version of the contract, if there was a change of control that was okay, it had to be to an entity that is either wholly owned or directly connected to the Registry. That test has been loosened to a wider test - again, is that a problem.</div><div><br></div><div>Again, I leave the technical changes to others, but otherwise, don’t have comments</div><div><br></div><div>Holly<br><div><div>On 2 Jun 2016, at 7:18 am, Cheryl Langdon-Orr <<a href="mailto:langdonorr@gmail.com">langdonorr@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">Hi all... I have also dine a *very quick once over* and concur with Alans appraisal... But note my particular pleasure at seeing the new language in 2.1.5 and more generally relating to IDN's and IANA Db Updates... Others of course should as Alan suggested read and review as well...</p>
<div class="gmail_quote">On 2 Jun 2016 5:59 am, "Alan Greenberg" <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
I did a quick read-through of the redline version of the contract and did
not notice anything onerous, but it would be a good idea if one or more
other people also reviewed it.<br><br>
The redline version is at
<a href="https://www.icann.org/en/system/files/files/draft-registry-agreement-amended-redline-31may16-en.pdf" target="_blank">
https://www.icann.org/en/system/files/files/draft-registry-agreement-amended-redline-31may16-en.pdf</a>
.<br><br>
Alan<br><br>
<br>
<blockquote type="cite">From: ICANN At-Large Staff
<<a href="mailto:staff@atlarge.icann.org" target="_blank">staff@atlarge.icann.org</a>><br>
To: "<a href="mailto:alac-announce@atlarge-lists.icann.org" target="_blank">alac-announce@atlarge-lists.icann.org</a>"<br>
<u></u> <u></u>
<<a href="mailto:alac-announce@atlarge-lists.icann.org" target="_blank">alac-announce@atlarge-lists.icann.org</a>>,
"<a href="mailto:at-large@atlarge-lists.icann.org" target="_blank">at-large@atlarge-lists.icann.org</a>"<br>
<u></u> <u></u>
<<a href="mailto:at-large@atlarge-lists.icann.org" target="_blank">at-large@atlarge-lists.icann.org</a>><br>
Date: Wed, 1 Jun 2016 17:55:59 +0000<br>
Subject: [At-Large] New Public Comment: Proposed Amendments to Base New
gTLD Registry Agreement Follow Updates<br>
Precedence: list<br><br>
Dear All, <br><br>
This is to let you know that the Public Comment on the ‘Proposed
Amendments to Base New gTLD Registry Agreement Follow Updates' has now
gone live:
<a href="https://www.icann.org/public-comments/proposed-amend-new-gtld-agreement-2016-05-31-en" target="_blank">
https://www.icann.org/public-comments/proposed-amend-new-gtld-agreement-2016-05-31-en</a>
<br><br>
Public comment will end on 13 July 2016 23:59 UTC. During this period,
anyone can submit comment via
<a href="mailto:comments-proposed-amend-new-gtld-agreement-31may16@icann.org" target="_blank">comments-proposed-amend-new-gtld-agreement-31may16@icann.org</a>. <br><br>
As an advisory committee of ICANN, the ALAC submits Statements on Public
Comment and advises on policy matters related to the interest of Internet
users worldwide. Not just limited to the 15 ALAC members, members from
the wider At-Large community are welcome to draft a Statement on behalf
of the ALAC. <br><br>
If you are interested in drafting an ALAC Statement on this Public
Comment, kindly contact
<a href="mailto:staff@atlarge.icann.org" target="_blank">staff@atlarge.icann.org</a>.
At-Large Staff will follow up and help you understand the procedure.
<br><br>
Additionally, the wiki workspace for developing a potential ALAC
Statement is here:
<a href="https://community.icann.org/x/uBiOAw" target="_blank">
https://community.icann.org/x/uBiOAw</a>. All pertinent resources for
this public comment can also be found there. <br><br>
<font face="Calibri">Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella
Gruber, Nathalie Peregrine, Terri Agnew and YeÅŸim Nazlar<br><br>
ICANN Policy Staff in support of the At-Large Community<br><br>
E-mail:
<a href="mailto:staff@atlarge.icann.org" target="_blank">staff@atlarge.icann.org</a><br>
<br>
Website:
<a href="https://atlarge.icann.org/" target="_blank">atlarge.icann.org</a><br><br>
Facebook:
<a href="https://www.facebook.com/icannatlarge" target="_blank">facebook.com/icann</a>
<a href="https://www.facebook.com/icannatlarge" target="_blank">atlarge</a><br><br>
Twitter:
<a href="https://twitter.com/ICANNAtLarge" target="_blank">@</a>
<a href="https://twitter.com/ICANNAtLarge" target="_blank">ICANNAtLarge</a><br>
</font>Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<u></u> <u></u>
1;SN1PR0301MB2030;9:2fueJ/5COLmJTmB643qhEVvlhfbjgKSm2l3ppjdejrfepA9HlOXxznZg/hLmGGLHSuDJAbuGlkYc+6RFtdYc+vMtlVloDkN2To4UXjhk1qxqDPjzZE2Cg6b2A3Rns7x2/70CFRADK+TwHMvoHEGv4pTvZhA+CO/Sk06dx9IzFLHH2ZaNiFfE6Ry3f/L8jQsv<br>
<br>
_______________________________________________<br>
At-Large mailing list<br>
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank">At-Large@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" target="_blank">
https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br><br>
At-Large Official Site:
<a href="http://atlarge.icann.org/" target="_blank">
http://atlarge.icann.org</a></blockquote></div>
<br>_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org/" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a><br></blockquote></div>
_______________________________________________<br>ALAC mailing list<br><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br>https://atlarge-lists.icann.org/mailman/listinfo/alac<br><br>At-Large Online: http://www.atlarge.icann.org<br>ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</blockquote></div><br></div></body></html>