[RDS-WHOIS2-RT] Request to Remove RDS-WHOIS2 Review from Short-term options Public Comment

[Dmitry Belyavsky]

Dear Alan,

I totally agree with you.

сб, 2 июня 2018 г., 12:49 Erika Mann <erika at erikamann.com>:

> Understood, I re-checked, you're correct Alan.
>
> Kind regards,
> Erika
>
> On Sat, Jun 2, 2018 at 6:49 AM, Alan Greenberg <alan.greenberg at mcgill.ca>
> wrote:
>
>> Hi Erika,
>>
>> If you look at the FactSheet (latest at
>> https://community.icann.org/download/attachments/64084088/RDS%20Fact%20Sheet%20%2828Mar2018%29.pdf
>> <https://community.icann.org/download/attachments/64084088/RDS%20Fact%20Sheet%20(28Mar2018).pdf>
>> ), you will see that the original budget of $690k was comprised of three
>> items:
>>
>> $200k for contract services - an external consultant to do studies of
>> some other work.
>>
>> $340k for travel
>>
>> $150k for ICANN Org support
>>
>> The $200k external contract is something that we have not found the need
>> for.
>>
>> Our estimated travel is $170k, just about what you would expect given
>> that the RT size is half of what was allowed for in the original budget (we
>> have 10 people and in theory, we could have had 21).
>>
>> The ICANN Org costs we expect to come in at under $100k based on what we
>> have seen to date.
>>
>> So the delta of $400k comes largely from not hiring and external
>> consultant, having a small team, and a modest savings on staff time
>> compared to what was originally estimated.
>>
>> Alan
>>
>>
>>
>> At 02/06/2018 12:25 AM, Erika Mann wrote:
>>
>> Alan - the original 600K may include money spent for ICANN ORG employees
>> and for technical assistance. Maybe we should include a placeholder for an
>> assumed number X.
>> Erika
>>
>> Sent from my iPhone
>>
>> On Jun 2, 2018, at 5:04 AM, Alan Greenberg <alan.greenberg at mcgill.ca >
>> wrote:
>>
>> During our meeting last Monday, we decided to request that ICANN Org
>> remove the RDS-WHOIS2 from the Public Comment(PC) on Short-Term Options to
>> Adjust the Timeline for Specific Reviews.
>>
>> Part of the argument for doing so is that we will be almost finished the
>> bulk of our work by the time the PC completes, and the other part is that
>> the financial savings that the PC presume from our changing scope or
>> pausing the review - $460k is far too high.
>>
>> For this 2nd part, I have summarized our past and projected expenses. If
>> the RT does not agree with these projections, they must be adjusted prior
>> to us making the request (which I hope we can do next Monday).
>>
>>
>>
>> *Facts/Assumptions: *We had a cost of $15k for the Abu Dhabi meeting
>> (people were brought in even though we did not end up having a formal
>> meeting).
>>
>> We have had 2 F2F meetings to date at a cost of about $30k each. To
>> complete its final report, the RT will need the planned F2F meeting in
>> July, and possibly another F2F to complete the final report, potentially in
>> November.
>>
>> We have currently spent about $46k on external contract support (largely
>> Lisa) and I have projected another $40k presuming a large part of the work
>> has already been carried out, but there may be some editing and other needs
>> near the end.
>>
>> It is possible that we may want to bring several people to the March 2019
>> ICANN meeting to formally present the report. I have allowed $20k for that
>> (per person costs will be higher than our Brussels meetings)
>>
>> For general contingency I have added $19k, and also an additional $30k in
>> case, for whatever reason, we need one more F2F meeting.
>>
>> The original review budget allowed $200k for an external study, but there
>> is no indication that this will be used.
>>
>> That results in a total Review Budget $290 compared to the original ICANN
>> estimate of $690k. The FY breakdown is: FY17: $15k; FY18: $130k; FY19:
>> $145k.
>>
>> MSSI has reviewed this and presuming the assumptions of number of
>> meetings and no external contract is correct, they believe that this is
>> reasonable.
>>
>> Are there any questions, and do you feel comfortable proceeding on this
>> basis?
>>
>>
>>
>> *THIS WILL BE DISCUSSED DURING OUR MONDAY MEETING. IF YOU CANNOT ATTEND,
>> PLEASE SEND COMMENTS AHEAD OF TIME. *Alan
>> _______________________________________________
>> RDS-WHOIS2-RT mailing list
>> RDS-WHOIS2-RT at icann.org
>> https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>>
>>
> _______________________________________________
> RDS-WHOIS2-RT mailing list
> RDS-WHOIS2-RT at icann.org
> https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20180603/a099f56b/attachment.html>