<html>
<body>
At 02/06/2016 04:04 AM, Holly Raiche wrote:<br><br>
<blockquote type=cite class=cite cite="">I have also had a quick
look<br>
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:<br>
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?</blockquote><br>
It doesn't say they don't have to say why. It says it is at their sole
discretion. It sounds like the waiver would be quid pro quo for something
it gets in return ("<i>Operator’s acceptance of the terms and
conditions set forth in such waiver.</i>") I have no specific
information on when they might do this, but ICANN has used fee reductions
as enticements to get registrars to move to new contracts, as an
example.<br><br>
<blockquote type=cite class=cite cite="">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.</blockquote><br>
Doesn't sound like an issue that concerns me.The description of the
changes is "<i>Revision creates a new defined term, “Affiliated
Assignee,” which has the effect of facilitating reorganizations by
Registry Operator without triggering a consent right of ICANN. Revision
also clarifies that the Affiliated Assignee’s assumption of the
obligations under the Registry Agreement must be made in
writing.</i>" I think it just acknowledges that corporate lawyers
(and perhaps tax accountants) can be imaginative in how they change
things.<br><br>
Alan<br><br>
<br>
<blockquote type=cite class=cite cite="">Again, I leave the technical
changes to others, but otherwise, don’t have comments<br><br>
Holly<br>
On 2 Jun 2016, at 7:18 am, Cheryl Langdon-Orr
<<a href="mailto:langdonorr@gmail.com">langdonorr@gmail.com</a>>
wrote:<br><br>
<blockquote type=cite class=cite cite="">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...<br>
On 2 Jun 2016 5:59 am, "Alan Greenberg"
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
> wrote:<br>
<dl>
<dd>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>
<dd>The redline version is at
<a href="https://www.icann.org/en/system/files/files/draft-registry-agreement-amended-redline-31may16-en.pdf">
https://www.icann.org/en/system/files/files/draft-registry-agreement-amended-redline-31may16-en.pdf</a>
.<br><br>
<dd>Alan<br><br>
<br>
<blockquote type=cite class=cite cite="">
<dd>From: ICANN At-Large Staff
<<a href="mailto:staff@atlarge.icann.org">staff@atlarge.icann.org</a>
><br>
<dd>To:
"<a href="mailto:alac-announce@atlarge-lists.icann.org">
alac-announce@atlarge-lists.icann.org</a>"<br>
<dd>
<<a href="mailto:alac-announce@atlarge-lists.icann.org">
alac-announce@atlarge-lists.icann.org</a>>,
"<a href="mailto:at-large@atlarge-lists.icann.org">
at-large@atlarge-lists.icann.org</a>"<br>
<dd>
<<a href="mailto:at-large@atlarge-lists.icann.org">
at-large@atlarge-lists.icann.org</a>><br>
<dd>Date: Wed, 1 Jun 2016 17:55:59 +0000<br>
<dd>Subject: [At-Large] New Public Comment: Proposed Amendments to Base
New gTLD Registry Agreement Follow Updates<br>
<dd>Precedence: list<br><br>
<dd>Dear All, <br><br>
<dd>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">
https://www.icann.org/public-comments/proposed-amend-new-gtld-agreement-2016-05-31-en</a>
<br><br>
<dd>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">
comments-proposed-amend-new-gtld-agreement-31may16@icann.org</a>.
<br><br>
<dd>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>
<dd>If you are interested in drafting an ALAC Statement on this Public
Comment, kindly contact
<a href="mailto:staff@atlarge.icann.org">staff@atlarge.icann.org</a>.
At-Large Staff will follow up and help you understand the procedure.
<br><br>
<dd>Additionally, the wiki workspace for developing a potential ALAC
Statement is here:
<a href="https://community.icann.org/x/uBiOAw">
https://community.icann.org/x/uBiOAw</a>. All pertinent resources for
this public comment can also be found there. <br><br>
<dd><font face="Calibri">Heidi Ullrich, Silvia Vivanco, Ariel Liang,
Gisella Gruber, Nathalie Peregrine, Terri Agnew and YeÅŸim
Nazlar<br><br>
<dd>ICANN Policy Staff in support of the At-Large Community<br><br>
<dd>E-mail:
<a href="mailto:staff@atlarge.icann.org">staff@atlarge.icann.org</a><br>
<br>
<dd>Website:
<a href="https://atlarge.icann.org/">atlarge.icann.org</a><br><br>
<dd>Facebook:
<a href="https://www.facebook.com/icannatlarge">facebook.com/icann</a>
<a href="https://www.facebook.com/icannatlarge">atlarge</a><br><br>
<dd>Twitter: <a href="https://twitter.com/ICANNAtLarge">@</a>
<a href="https://twitter.com/ICANNAtLarge">ICANNAtLarge</a><br>
</font>
<dd>Content-Type: text/plain; charset="us-ascii"<br>
<dd>Content-Transfer-Encoding: 7bit<br>
<dd>Content-Disposition: inline<br>
<dd>X-Microsoft-Exchange-Diagnostics:<br>
<dd>
1;SN1PR0301MB2030;9:2fueJ/5COLmJTmB643qhEVvlhfbjgKSm2l3ppjdejrfepA9HlOXxznZg/hLmGGLHSuDJAbuGlkYc+6RFtdYc+vMtlVloDkN2To4UXjhk1qxqDPjzZE2Cg6b2A3Rns7x2/70CFRADK+TwHMvoHEGv4pTvZhA+CO/Sk06dx9IzFLHH2ZaNiFfE6Ry3f/L8jQsv<br>
<br>
<dd>_______________________________________________<br>
<dd>At-Large mailing list<br>
<dd><a href="mailto:At-Large@atlarge-lists.icann.org">
At-Large@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br><br>
<dd>At-Large Official Site:
<a href="http://atlarge.icann.org/">http://atlarge.icann.org</a>
</blockquote><br>
<dd>_______________________________________________<br>
<dd>ALAC mailing list<br>
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</a>
<br>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
<br><br>
</dl>_______________________________________________<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" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" eudora="autourl">
http://www.atlarge.icann.org</a><br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC" eudora="autourl">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)</blockquote><br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;BY2PR0301MB2023;9:bPMXXecd1GK0TDnPmfSTuH2BT6QfAnHeTWT7x5pCcQhcXzW0ASlo1UoZW4absQB1qSTwsJcy//3Vrf5j9WI2QuU7DAFQzGMvcNJUm5cGVrHiBPDSSXGvhq9vGItkFhQ/0qG9a4sGzrdyG2DSANDXeNqqCDKLFpdVWgoFbfMTtAYrMGb9Nx/lYsYM5ve7v1u3<br>
<br>
_______________________________________________<br>
ALAC mailing list<br>
ALAC@atlarge-lists.icann.org<br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" eudora="autourl">
http://www.atlarge.icann.org</a><br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC" eudora="autourl">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)</blockquote></body>
</html>