[Ccwg-auctionproceeds] For your review - latest version of Final Report by Wednesday 11 September 2019

Wed Nov 20 09:33:30 UTC 2019

Dear Emily, Nadine - I will check options and languages tonight - after 9 PM CET. 

Kind regards and thank you! 
Erika 

Sent from my iPhone

> On Nov 20, 2019, at 10:30 AM, Emily Barabas <emily.barabas at icann.org> wrote:
> 
> Hi Nadira and Erika,
>  
> For reference, here is the text in the report currently included in response to charter question #4:
>  
> Charter Question #4: What aspects should be considered to define a timeframe, if any, for the funds allocation mechanism to operate as well as the disbursements of funds? E.g. The timeframe for the operation of this new mechanism may provide the opportunity for long term support, or for funding to be released in tranches linked to milestone achievements, single or multiple disbursements.
>  
> The timeframe should be established in line with and guided by strategic objectives for allocation of the funds. Once it is determined how “success” is defined for this fund, the timeframe should be set to support a successful outcome.
>  
> The CCWG's focus is on the Auction Proceed funds that are currently available without any assumption that additional funds will become available in the future. The role of this CCWG is to identify and to evaluate possible mechanisms to disburse funds received through auctions from the 2012 gTLD application round. Therefore, the CCWG has focused on developing recommendations that will enable the disbursement of the funds in an effective and judicious manner without creating a perpetual mechanism (i.e. not being focused on preservation of capital).
>  
> The CCWG agrees with the Board’s assessment that proceeds should be allocated in tranches over a period of several years, regardless of the mechanism implemented.[1] This would help ensure that the Board is meeting its obligations and allow for adjustments to the framework as needed, noting that changes may have legal, operational, and cost impacts. Tranches may be used to fund large grants over a period of years or to support projects that could be funded in a shorter period. Similarly, smaller grants could be distributed in a single fund transfer.
>  
> CCWG Recommendation #6: The selected mechanism must be implemented to enable the availability of funds for a specific round as well as the disbursement of the funds for selected projects in an effective and judicious manner without creating a perpetual mechanism (i.e. not being focused on preservation of capital).
>  
> CCWG Recommendation #7: Funding availability for a funding round should be staged in tranches over a period of years, regardless of the mechanism implemented. Progressive disbursements may be used to fund projects receiving large grants to be implemented over a period of years. Similarly, progressive disbursements can support projects that could be implemented in shorter periods.
>  
> Kind regards,
> Emily
>  
> From: Ccwg-auctionproceeds <ccwg-auctionproceeds-bounces at icann.org> on behalf of Nadira Alaraj <nadira.araj at gmail.com>
> Date: Wednesday, 20 November 2019 at 10:12
> To: "erika at erikamann.com" <erika at erikamann.com>
> Cc: "ccwg-auctionproceeds at icann.org" <ccwg-auctionproceeds at icann.org>
> Subject: Re: [Ccwg-auctionproceeds] For your review - latest version of Final Report by Wednesday 11 September 2019
>  
> Dear Erika,
> Thanks for your prompt reply. 
>  
> Excuse me for also not following the timeline as well,
> if there are no further public comments then I go with your suggestion. If there is, then it would be sufficient to include something on the legal difficulties for handling the sunset or the ability of each mechanism to handle an investment of an endowment to sustain a long term functioning of the proceed.
> Best wishes,
> Nadira
>  
>  
> On Wed, Nov 20, 2019, 10:22 Erika Mann <erika at erikamann.com> wrote:
> Dear Nadia -
>  
> My advice would be not to include a specific sunset clause. As you’re aware, I chaired and worked with different globally oriented funds and sunset clauses can become a legal burden, simply because a time limitation can become problematic or because the nature of a fund might change. 
>  
> We have included language that talks about a ‘one-off’ AP related money stream (related to the current gTLD round. 
> We should check whether this particular language is sufficiently clear.
>  
> Let us know if this approach is meeting your ideas.
>  
> Kind regards,
> Erika 
> 
> Sent from my iPhone
> 
> On Nov 20, 2019, at 9:03 AM, Nadira Alaraj <nadira.araj at gmail.com> wrote:
> 
> Dear All,
> Apologies for my lack of engagement and my very late comment.
>  
> As I'm trying to catch-up with discussions about the different mechanisms, I didn't see any comparative on the criterion of 
>  
> 
> Ability to sunset (i.e. terminate / close down)
> 
> It might be there and I might not been careful in my reading.
>  
> Best wishes,
> Nadira
> 
> On Sat, Sep 7, 2019, 23:28 Marika Konings <marika.konings at icann.org> wrote:
> Dear CCWG,
>  
> Someone pointed out that the redlines in the pdf were not visible so please try the attached version instead.
>  
> As a reminder, your input is due by Wednesday 11 September 2019 at the latest.
>  
> Thanks,
>  
> Marika
>  
> From: Ccwg-auctionproceeds <ccwg-auctionproceeds-bounces at icann.org> on behalf of Marika Konings <marika.konings at icann.org>
> Date: Friday, August 30, 2019 at 16:32
> To: "ccwg-auctionproceeds at icann.org" <ccwg-auctionproceeds at icann.org>
> Subject: [Ccwg-auctionproceeds] For your review - latest version of Final Report by Wednesday 11 September 2019
>  
> Dear CCWG,
>  
> Please find here for your review the latest version of the Final Report: https://drive.google.com/a/icann.org/file/d/1hWfSYXuhAalh7F_AkkPDuxU7xf-_bNcR/view?usp=sharing [drive.google.com]. Attached you will find a redline version that shows you all the updates that have been made since the previous version but as the large number of redlines may be slightly overwhelming, we have posted the clean version for review and comments. Please note the following:
>  
> Text highlighted in blue are those developed by the different small teams and are new compared to the previous version of the report;
> Text highlighted in yellow are items that need to be updated after completion of the survey and decision on whether or not to publish for public comment.
> Redlines in the attached version are updates in response to comments received on the previous version, clarifications or the result of reorganization of the text because certain recommendations seemed to fit better under a different charter questions.
>  
> You are requested to focus your review on any ‘cannot live with items’ that need further discussion or consideration. Of course, if you spot any grammatical errors, inconsistencies or language that could be clarified, please note those as well. As a reminder your input is requested by Wednesday 11 September 2019 at the latest (see timeline below).
>  
> Best regards,
>  
> Marika
>  
> Action
> Expected Timing - By
> Finalize work on items discussed during today’s meeting
> Friday 23 August 2019
> Staff to integrate agreed to language in draft final report and produce ‘final’ version for review
> Friday 30 August 2019
> CCWG to review draft final report and flag any issues of major concern
> Wednesday 11 September 2019
> CCWG Meeting:
> Discuss any major concerns identified
> Consider whether a public comment period is desirable
> Wednesday 18 September 2019
> Launch indicative survey on mechanisms
> Friday 20 September 2019
> Publish results of indicative survey
> Friday 27 September 2019
> CCWG members to consult with respective groups
> Friday 11 October 2019
> Re-launch survey on mechanisms
> Monday 14 October 2019
> Finalize report based on definitive survey results and either publish for public comment or submit to CO
> Friday 25 October 2019
> ICANN66 session to present Final Report
> Wednesday 6 November 2019 – 15.15 – 18.30
>  
>  
>  
>  
>  
> Marika Konings
> Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) 
> Email: marika.konings at icann.org  
>  
> Follow the GNSO via Twitter @ICANN_GNSO
> Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. 
>  
> _______________________________________________
> Ccwg-auctionproceeds mailing list
> Ccwg-auctionproceeds at icann.org
> https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy [icann.org]) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
> _______________________________________________
> Ccwg-auctionproceeds mailing list
> Ccwg-auctionproceeds at icann.org
> https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy [icann.org]) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
> 
> [1] The CCWG notes that the ICANN Board has advised that in the case of an ICANN Foundation, the proceeds would also be distributed to the ICANN Foundation in tranches.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ccwg-auctionproceeds/attachments/20191120/50a58aae/attachment-0001.html>