[ALAC] Ratification Pending: ALAC Statement on the Proposed Renewal of .NET Registry Agreement

[Seun Ojedeji]

Hello,

I think the 10% increase needs to be noted and deleting that sentence loses
that note. I suggest rewording to the following:

"The proposed 10% annual increase which all goes to the registry is
significantly​ high and should be re-considered."

Regards
Sent from my Mobile
Kindly excuse brevity and typos

On May 31, 2017 05:15, "Maureen Hilyard" <maureen.hilyard at gmail.com> wrote:

> Happy to have the sentence deleted and the statement tidied up. Glad to
> eventualy get some input. Its been there for a while.
>
> Maureen
>
> On Wed, May 31, 2017 at 1:53 PM, Alan Greenberg <alan.greenberg at mcgill.ca>
> wrote:
>
>> Sorry, I should have checked by this got by me.
>>
>> I presume the $10 in the statement should have been 10%  and I really
>> don't understand what is meant by "is also out of scope for an ICANN
>> Registry Agreement", since it is clearly not out of scope. It is not the
>> norm, and is out of scope for a NORMAL registry agreement, but certainly is
>> in scope for this very unusual agreement.
>>
>> I suggest the this sentence be dropped and the statement re-issued.
>>
>> Alan
>>
>> At 30/05/2017 07:04 PM, ICANN At-Large Staff wrote:
>>
>> Dear All,
>>
>> Please be so kind to find attached the ALAC Statement on the Proposed
>> Renewal of .NET Registry Agreement.
>>
>> In the interest of time, the ALAC Chair requested that the Statement be
>> transmitted to the ICANN public comment process, copying the ICANN Staff
>> member responsible for this topic, with a note that the Statement is
>> pending ALAC ratification. Once ratified, this Statement will be
>> resubmitted incorporating updated ratification information in the
>> introduction section.
>>
>> ICANN Policy Staff in support of the At-Large Community
>> E-mail: staff at atlarge.icann.org
>> Website: atlarge.icann.org
>> Facebook: facebook.com/icann <https://www.facebook.com/icannatlarge>
>> atlarge <https://www.facebook.com/icannatlarge>
>> Twitter: @ <https://twitter.com/ICANNAtLarge> ICANNAtLarge
>> <https://twitter.com/ICANNAtLarge>
>>
>>
>> Content-Type: application/pdf; name="AL-ALAC-ST-0517-07-00-EN.pdf"
>> Content-Description: AL-ALAC-ST-0517-07-00-EN.pdf
>> Content-Disposition: attachment; filename="AL-ALAC-ST-0517-07-00-EN.pdf";
>>          size=241838; creation-date="Tue, 30 May 2017 23:04:44 GMT";
>>          modification-date="Tue, 30 May 2017 23:04:44 GMT"
>> Content-ID: <944AB3A64D187B4E9FF9870710BA62A2 at pexch112.icann.org>
>> X-Microsoft-Exchange-Diagnostics:
>>          1;DM5PR03MB2714;27:BUowScGu0hA4GBTcD/FJ69QsbdHvvSOlLQrtTS2lb
>> 4fL6BFuFe5vGCTFzjx46jlFiJotAUKXPaJMd2YqQ+o7zna9yqtpeOTHDTw0p
>> GRGA33OcCMeKkjtECf7zmZe7xgMo8faEMUrWb9wD34FaKxxKw==
>> X-Microsoft-Antispam-Mailbox-Delivery:
>>          ex:0;auth:0;dest:I;ENG:(400001000100)(400125000095)(20160514
>> 016)(520000050)(520002050)(750028)(400001001128)(
>> 400125100095)(400001002128)(400125200095);
>>
>>
>
> _______________________________________________
> ALAC mailing list
> ALAC at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/alac
>
> At-Large Online: http://www.atlarge.icann.org
> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+
> Advisory+Committee+(ALAC)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20170531/bc66762c/attachment.html>