June 2018 - Ccwg-auctionproceeds

Notes and action items from today's new gTLD Auction Proceeds CCWG meeting
by Marika Konings 27 Jun '18

27 Jun '18

Dear All, Please find below the notes and action items from today’s new gTLD Auction Proceeds CCWG meeting. As a reminder: Action item #1: CCWG review the mechanism summary descriptions<https://community.icann.org/download/attachments/84220195/CCWG.AP%20Mechani…> and identify any further questions they may have to relay to Sarah by 9 July 2018. Action Item #2: Staff will re-open the Google document https://docs.google.com/document/d/13Kbjnnflt0h5ZVkP57s2nP0trJyQCcuTfdWjzbg…. CCWG members are requested to review the proposed responses and provide input to questions identified by 9 July 2018. The next meeting is scheduled for Thursday 12 July at 14.00 UTC. Best regards, Marika ============= New gTLD Auction Proceeds CCWG Meeting – 27 June 2018 (ICANN62 – Panama) These high-level notes are designed to help the CCWG navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/display/CWGONGAP/2018+Meetings. 1. Roll Call * Roll Call will be taken from Adobe Connect * Please remember to state your name for transcription purposes and don't forget to mute your line / microphone when not speaking to avoid interruption. 2. Welcome & SOI/DOI updates * Reminder - please check your SOI/DOIs and make sure these are up to date * Tony Harris: Stepping down as a member and continuing as a participant, and Marilyn Cade will join as a member from the Commercial Stakeholder Group (GNSO). 3. Status Update: Reminder of the purpose of this WG (see slides 5 through 14) * Process for development for auction proceeds allocation (slide 9) – you have the full communication channels with the Board, which is very helpful, to avoid issues at the end. * CCWG-AP Work Plan (slide 10): Now in Phase 5 -- Answer Charter Questions as Organized by Phase 1 for Mechanism(s) Determined in Phase 4. * Determine whether there is a preference for a mechanism or mechanisms, perhaps via a poll. * Four possible mechanisms for further consideration (slide 11): * How to participate (slide 14) – newsletters, join as a member, or as an observer. Also provide input in the public forum when the report is published. * Timeline: Goal is to release a draft report three weeks before ICANN63 (October 2018), and there will be a requirement for a public comment period of at least 40 days. * Publication is dependent on the number and type of comments in the public comment period. 4. Board Liaison Update/Discussion in the Board * Noted in the four models that none of them were preferred, so didn’t talk about the models. Differences were not clear to everyone. * Funds should be allocated in tranches. * Evaluation: two separate functions – administrative/criteria fulfillment – could be inside or outside ICANN, but it should be neutral and cost effective; content evaluation/qualitative analysis should be an independent panel that is neutral, with no conflicts of interest. * Not clear whether the Board signs off on proposals and note that the selection should not be second-guessed by the Board. Just that the process has been carried out properly. * Should be a step in there for a review to see that the process is meeting expectations. * There should be reports that provide feedback, at least on an annual basis, as well as a status report on the funding disbursement. There is a charter question about whether a review mechanism should be put in place and there is a Google doc to help develop suggestions. 5. Review of mechanism descriptions developed by Sarah Berg, Ponsonby Partners, ICANN Contracted Advisor on Strategic Development and Philanthropic Programs Sarah Berg, Ponsonby Partners (See summary descriptions<https://community.icann.org/display/CWGONGAP/2018-06-27+-+ICANN62+Panama+-+…> proposed: https://community.icann.org/x/IxkFBQ) Mechanism 1: Internal ICANN Department Mechanism 2: ICANN+ External Organization Mechanism 3: ICANN Foundation Mechanism 4: External Entity Questions/Discussion: * If in house it would be separate from the rest of ICANN Org. * Mechanisms 2 – ICANN could work with a couple of different organizations. * Question: Even considering that is short term department to be create, the compared cost still minimal considering people need to be dismissed after 2-3 years for instance? Answer: If you had a sunset period you could hire a team that would exist as long as you wanted to have this running. * Question: Would a foundation have to be US-based? Answer: Given that ICANN is a US entity it would probably be a US entity, but that would be ICANN’s decision. * Question: What would be the liability? Answer: It would be the same as for a 501c3. But if you are talking about a foundation it has its own legal liability and Board/fiduciary requirements. * Question: Is the separate board requirement applicable for all types of 501c3 entities or are there exceptions? Answer: The separate board requirement only applies to mechanism 3. * Question: Do the tax filing requirements have any limits on eligibility? Answer: When you are a listed on which tax filing it doesn’t matter that all potential grant funders need to adhere to ICANN’s mission. * Question: In comparing mechanism 1 and 2, is there a benefit to not have grant activity listed ICANN’s annual tax filings with the US government? Would ICANN be better protected by having the DAF reporting for grant activity in its tax filling? Answer: That depends on ICANN and who the recipients are. * Question re: the ability for ICANN to apply for funds: Do any of the models restrict that? Answer: With Mechanism 3 – the foundation – ICANN could not decide to allocate some of the funds to its own use (such as the reserve fund). Include this question as part of the gap analysis. Action item #1: CCWG review summary descriptions and identify any further questions they may have to relay to Sarah by 9 July 2018. 6. Review of proposed responses to remaining charter questions (see https://docs.google.com/document/d/13Kbjnnflt0h5ZVkP57s2nP0trJyQCcuTfdWjzbg… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…>) * Background: Charter questions need to be answered for each of the mechanisms (slide 18). Still quite a few open issues. Cannot move forward without input. * Meeting the timeline requires input from the WG. Action Item #2: Staff will re-open the Google document https://docs.google.com/document/d/13Kbjnnflt0h5ZVkP57s2nP0trJyQCcuTfdWjzbg…. CCWG members are requested to review the proposed responses and provide input to questions identified by 9 July 2019. 7. Review of work plan and next steps (see slide 24 of presentation) * The goal is to have the draft report three weeks ahead of ICANN63. * Propose meetings every two weeks, but may increase to weekly if necessary to meet the goal. * May have some flexibility with publication date. * Should there be time in the schedule for WG members to take the Google doc back to their members for consideration? * There is time built in for another poll on the mechanisms. 8. Confirm next meeting (Thursday 12 July at 14.00 UTC) Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Proposed agenda new gTLD Auction Proceeds CCWG meeting on 27 June from 15.15 - 16.45 local time
by Marika Konings 27 Jun '18

27 Jun '18

Dear All, Please find below the proposed agenda for next week’s new gTLD Auction Proceeds CCWG meeting. As a reminder, remote participation details can be found here: https://community.icann.org/x/6QQFBQ. As another reminder, please review the draft responses to the charter questions and provide any comments and/or questions you may have in the google doc (https://docs.google.com/document/d/13Kbjnnflt0h5ZVkP57s2nP0trJyQCcuTfdWjzbg…) by Saturday 23 June at the latest. Best regards, Marika ================= Proposed Agenda – new gTLD Auction Proceeds Cross-Community Working Group F2F Meeting – 27 June 2018 from 15.15 – 16.45 local time 1. Roll Call 2. Welcome – SOI & DOI Updates 3. Status Update 4. Review of mechanism descriptions developed by Sarah Berg (see attached) 5. Review of proposed responses to remaining charter questions (see https://docs.google.com/document/d/13Kbjnnflt0h5ZVkP57s2nP0trJyQCcuTfdWjzbg…) 6. Review of work plan and next steps 7. Confirm next meeting (Thursday 12 July at 14.00 UTC) Looking forward to receiving your feedback. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

2 1

Re: [Ccwg-auctionproceeds] Proposed agenda new gTLD Auction Proceeds CCWG meeting on 27 June from 15.15 - 16.45 local time
by Marika Konings 27 Jun '18

27 Jun '18

As a reminder, the CCWG meeting will take place today in Salon 9 at 15.15 local time. All the documents that will be discussed during the meeting have been posted here: https://community.icann.org/x/IxkFBQ. Best regards, Marika From: Ccwg-auctionproceeds <ccwg-auctionproceeds-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Thursday, June 21, 2018 at 14:58 To: "ccwg-auctionproceeds(a)icann.org" <ccwg-auctionproceeds(a)icann.org> Subject: [Ccwg-auctionproceeds] Proposed agenda new gTLD Auction Proceeds CCWG meeting on 27 June from 15.15 - 16.45 local time Dear All, Please find below the proposed agenda for next week’s new gTLD Auction Proceeds CCWG meeting. As a reminder, remote participation details can be found here: https://community.icann.org/x/6QQFBQ [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. As another reminder, please review the draft responses to the charter questions and provide any comments and/or questions you may have in the google doc (https://docs.google.com/document/d/13Kbjnnflt0h5ZVkP57s2nP0trJyQCcuTfdWjzbg… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…>) by Saturday 23 June at the latest. Best regards, Marika ================= Proposed Agenda – new gTLD Auction Proceeds Cross-Community Working Group F2F Meeting – 27 June 2018 from 15.15 – 16.45 local time 1. Roll Call 2. Welcome – SOI & DOI Updates 3. Status Update 4. Review of mechanism descriptions developed by Sarah Berg (see attached) 5. Review of proposed responses to remaining charter questions (see https://docs.google.com/document/d/13Kbjnnflt0h5ZVkP57s2nP0trJyQCcuTfdWjzbg… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…>) 6. Review of work plan and next steps 7. Confirm next meeting (Thursday 12 July at 14.00 UTC) Looking forward to receiving your feedback. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses [learn.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

For your review - draft responses to remaining charter questions
by Marika Konings 16 Jun '18

16 Jun '18

Dear All, The leadership team has worked on a first draft response to the remaining charter questions, reviewing information from the charter question templates that were developed at an earlier stage of our work (see https://community.icann.org/x/PNrRAw) as well as the input provided by external experts (see https://community.icann.org/x/BSW8B) Some specific issues/questions for CCWG consideration have been highlighted in yellow, but of course, input is sought on all aspects of the proposed responses. Please review this document and provide any comments and/or questions you may have in the google doc by Saturday 23 June at the latest. This will allow the leadership team to review your feedback and prepare accordingly for the CCWG session which will take place on Wednesday 27 June from 15.15 – 16.45 local time (see https://62.schedule.icann.org/meetings/699541) For remote participation details, please see https://community.icann.org/x/6QQFBQ. To review the draft responses, please see https://docs.google.com/document/d/13Kbjnnflt0h5ZVkP57s2nP0trJyQCcuTfdWjzbg…. Thanks, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

3 2

Re: [Ccwg-auctionproceeds] Notes and action items - new gTLD Auction Proceeds CCWG meeting of 31 May 2018
by Sylvia Cadena 14 Jun '18

14 Jun '18

Hi everyone, Apologies for not being able to participate in the last call but traveling schedules have not allowed me to join the call, as I wish I had being able to do. I just wanted to say that I fully support all the action items as agreed below. I am not sure how advanced Erika and Ching are going with the draft answers to the charter questions, but I just wanted to say that I think that there are quite a few responses from other charter questions that we did through surveys before, that although were not done in light of the proposed options for a mechanism, could be used to fill in the cells on that table and that it will be really appreciated that a note for cross reference is made, so that is clear from where those responses came from, to make use of the contributions from this group and the thinking behind them. I look forward to the calendar information about the next meeting as well as the details to join remotely -if possible- to those meeting in Panama. Warm regards, Sylvia --------- Sylvia Cadena | APNIC Foundation - Head of Programs | sylvia(a)apnic.net | http://www.apnic.foundation ISIF Asia, WSIS Champion on International Cooperation 2018 | http://www.isif.asia | FB ISIF.asia | @ISIF_Asia | G+ ISIFAsia | 6 Cordelia Street, South Brisbane, QLD, 4101 Australia | PO Box 3646 | +10 GMT | skypeID: sylviacadena | Tel: +61 7 3858 3100 | Fax: +61 7 3858 3199 * Love trees. Print only if necessary. From: Ccwg-auctionproceeds <ccwg-auctionproceeds-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Friday, 1 June 2018 at 6:46 am To: "ccwg-auctionproceeds(a)icann.org" <ccwg-auctionproceeds(a)icann.org> Subject: [Ccwg-auctionproceeds] Notes and action items - new gTLD Auction Proceeds CCWG meeting of 31 May 2018 Dear All, Please find below the notes and action items of today’s new gTLD Auction Proceeds CCWG meeting. Note that the next meeting will be scheduled for Thursday 14 June at 14.00 UTC Best regards, Marika Notes & Action Items – CCWG Auction Proceeds Meeting – 31 May 2018 These high-level notes are designed to help the CCWG navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/x/DLHDAw<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. 1. Roll Call · Roll Call will be taken from Adobe Connect · Please remember to state your name for transcription purposes and don't forget to mute your line / microphone when not speaking to avoid interruption. · Audio only: Xavier Calvez (only first part of the meeting), Kavouss Arasteh 2. Welcome & SOI/DOI updates · Reminder - please check your SOI/DOIs and make sure these are up to date 3. Next steps for addressing charter questions · See email circulated by Erika earlier today · See template that was circulated to facilitate developing a response to the remaining charter questions. Leadership is offering to develop a first draft response to the charter questions for CCWG review, if possible prior to ICANN62. · See letter from the ICANN Board providing input on the mechanisms discussion. Board is of the view that there should be various tranches of funding so that the mechanism chosen can be closely monitored and adjustments, if needed, can be made. Mechanisms chosen should focus on effective and efficient disbursement. More information will be needed on relevant costs of the different mechanisms. Should be able to evaluate and monitor projects on a global basis. More work needed on ensuring a common understanding and providing additional definition of the mechanisms in advance of public comment. · Board letter seems to suggest that CCWG should not rush for public comment. · Any direct costs like communication, etc. should all be funded out of the proceeds or would some of these come out of ICANN's general budget? Board has not actually discussed that yet - cost for evaluating, managing, running the program would need to come out of the funding. Discreet items such as a communications plan in advance has not been discussed in particular, but could be considered inclusive of overall running of the program. Cost associated with a communication plan should be factored in. Measuring efficiency of funds need to take into account holistic viewpoint of costs that are associated with setting up / running a mechanism. CCWG may need to map out the different cost elements to get a better idea and track key areas of costs to determine how these would be funded. Need to look at costs from a standalone perspective. ICANN's ongoing funding is not set up to take care of this - all costs are expected to come out of auction proceeds. Once implementation starts, this is expected to come out of auction proceeds funding. · Further input on expected / max overhead costs may also be needed. Board previously mentioned a 5% threshold. Is there flexibility there to ensure efficiency / effectiveness balance? What is reasonable and what is cost effective, depends on the circumstances and the nature of the grants that are being made. % was never intended to be a hard / fast line. % needs to be reasonable in light of the objectives of the program. Focus should be on the use for proceeds in furtherance of the mission instead of administrative costs. Could ask in work on general description to provide an indication if overhead costs would be closer to 3 or 10 %, for example. · Need to also evaluate mechanisms according to the defined principles mentioned in the Board letter. Factor this into the draft response to charter questions. · Need to further consider how feasible tranching is as it will depend on size of fund allocation, similar would need to further discuss what mechanisms would need to be put in place that would warrant changes / corrections. Board is committed to the notion that funds would be allocated over a period of time to be able to ensure in earlier stages that proper controls are in place to monitor and manage applications and evaluations. Board has not yet considered possible size of fund allocation to projects. Objectives of fund allocation determined by the community would hopefully further clarity / guide that conversation. Intersection between size of projects and costs of overhead. · One of the factors that will significantly impact costs, which is not usually considered in any standard percentage, is the cost inherent to supporting a multistakeholder process: whether it is to organize some community communication on the overall process of the auction proceeds, or to support transparency and accountability mechanisms, these activities are rarely encountered elsewhere but are prevalent at ICANN and are very resource consuming. That will significantly impact the costs incurred for the program. If you take an illustration that the Drafting Team early on and now this CCWG AP have been working on the topic for 2 years, with ICANN's support, the costs is already significant and we have not even started implementing anything. · CCWG could consider whether certain amounts are allocated to baskets to focus on certain types of projects, including different sizes. CCWG to re-evaluate if that is a recommendation it would like to made. · The topic of tranches is one of the operational consequence of the board's fiduciary duty that the funds are used within mission and effectively: releasing funds in tranches to a given recipient allows to establish accountability mechanisms for that recipient to demonstrate that the funds are appropriately used. The other tranche topic is, as an example, to provide X million of dollars for allocation during a given year, which also allows to control the amount of effort required for evaluation and disbursement, allowing to minimize risks of errors or issues. · As a reminder, Sarah Berg has been asked to assist with developing a general description of each of these mechanisms. Action item #1: CCWG leadership to work on first draft of responses to charter questions, factoring in board input as well as discussion during today's meeting (31/5). To be circulated at the latest by 18 June to allow for sufficient time for CCWG to review. Action item #2: CCWG to consider developing list of cost elements to get a better idea and track key areas of costs and determine how these would be funded (from auction proceeds or differently). 4. Planning for ICANN62 · See email sent by Erika proposing to delay HIT session to ICANN63 and have a F2F meeting instead which would include an update to the community. In addition, leadership team is available to come and speak to / present to those groups that are interested. CCWG could consider other mechanisms to provide updates to the community for example in the form of a webinar. Regular newsletters are already provided to ensure that chartering organizations have regular status updates. Action item #3: CCWG to move forward with the changes that have been proposed (postpone HIT session to ICANN63 and change it to a F2F meeting instead. 5. Finalisation of preamble & reminder to review project examples by Monday 4 June at 18:00 UTC · No further input received on the preamble so that document should be considered final for inclusion in the Initial Report. Action item #4: reminder, CCWG to review project examples by Monday 4 June at 18.00 UTC at the latest. 6. Next steps & confirm next meeting (Thursday 7 or 14 June at 14:00 UTC) · Next meeting to be scheduled for 14 June at 14.00 UTC. Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Re: [Ccwg-auctionproceeds] [Ext] Re: Notes and action items - new gTLD Auction Proceeds CCWG meeting of 31 May 2018
by Daniel Dardailler 14 Jun '18

14 Jun '18

Hello all I realized yesterday that the way names were removed in the earlier anonymization phase of the examples denatured the intent of my original example. I'd like that my original example be edited as describe below (with my rationales). On 2018-06-05 21:25, Marika Konings wrote: > Thanks, Daniel. I have no issue updating it as suggested but can you > please share your suggestion with the mailing list so others have an > opportunity to weigh in? > > Best regards, > > Marika > > On 6/5/18, 13:14, "Daniel Dardailler" <danield(a)w3.org> wrote: > > Hello Marika, > > I realize this email didn't go out yesterday, I hope you can still > include it. > > It's a modification to the example that I originally provided and > that > was edited when the anonymization took place. > > Today it reads: > > Support work done by open standards developing organizations that > are of > common interest such as: > ● enhanced online security and privacy, > ● work on handling IDN and Universal acceptance issues, > ● more guidelines and tools for Internet users, > ● better education programs on Open Standards, > ● more open APIs for mobile apps and social network platform to > ensure a > strong hyperlink paradigm, > ● more involvement in Open standard advocacy, and in solving IPR > issues, > ● more resources for testing standards - critical to providing an > open > environment. > (Note, any such work should be in service of ICANN’s mission). > > > And if I could update the googledoc, I'd replace it with: > > Support work done by Internet and Web Open Standards Developing > Organizations that are of common interest such as: > ● enhanced online Internet and Web security and privacy, > ● work on handling IDN and Universal acceptance issues in Web > browsers > and tools, > ● more guidelines and tools for Internet and Web users, > ● better education programs on Internet and Web Open Standards, > ● open APIs for Web mobile apps and social network platform to > ensure a > strong hyperlink paradigm, > ● more involvement in Internet and Web Open standard advocacy, and > in > solving IPR issues, > ● more resources for testing Internet and Web standards - critical > to > providing an open environment. > (Note, any such work should be in service of ICANN’s mission). > > > The rationale is that since there is an explicit caveat wrt to the > mission service, being precise about the fact that it's for > Internet and > Web standards is important, as I don't want my example to give > ideas to > non Internet related SDOs. > > > Thanks. > > > > On 2018-05-31 22:46, Marika Konings wrote: > > Dear All, > > > > Please find below the notes and action items of today’s new gTLD > > Auction Proceeds CCWG meeting. Note that the next meeting will be > > scheduled for Thursday 14 June at 14.00 UTC > > > > Best regards, > > > > Marika > > > > NOTES & ACTION ITEMS – CCWG AUCTION PROCEEDS MEETING – 31 MAY > 2018 > > > > > > _These high-level notes are designed to help the CCWG navigate > through > > the content of the call and are not meant as a substitute for the > > transcript and/or recording. The MP3, transcript, and chat are > > provided separately and are posted on the wiki at: > > > __https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_… > [1]_._ > > > > 1. Roll Call > > > > * Roll Call will be taken from Adobe Connect > > * Please remember to state your name for transcription purposes > and > > don't forget to mute your line / microphone when not speaking to > avoid > > interruption. > > * Audio only: Xavier Calvez (only first part of the meeting), > Kavouss > > Arasteh > > > > 2. Welcome & SOI/DOI updates > > > > * Reminder - please check your SOI/DOIs and make sure these are > up > > to date > > > > 3. Next steps for addressing charter questions > > > > * See email circulated by Erika earlier today > > * See template that was circulated to facilitate developing a > > response to the remaining charter questions. Leadership is > offering to > > develop a first draft response to the charter questions for CCWG > > review, if possible prior to ICANN62. > > * See letter from the ICANN Board providing input on the > mechanisms > > discussion. Board is of the view that there should be various > tranches > > of funding so that the mechanism chosen can be closely monitored > and > > adjustments, if needed, can be made. Mechanisms chosen should > focus on > > effective and efficient disbursement. More information will be > needed > > on relevant costs of the different mechanisms. Should be able to > > evaluate and monitor projects on a global basis. More work needed > on > > ensuring a common understanding and providing additional > definition of > > the mechanisms in advance of public comment. > > * Board letter seems to suggest that CCWG should not rush for > public > > comment. > > * Any direct costs like communication, etc. should all be funded > out > > of the proceeds or would some of these come out of ICANN's > general > > budget? Board has not actually discussed that yet - cost for > > evaluating, managing, running the program would need to come out > of > > the funding. Discreet items such as a communications plan in > advance > > has not been discussed in particular, but could be considered > > inclusive of overall running of the program. Cost associated with > a > > communication plan should be factored in. Measuring efficiency of > > funds need to take into account holistic viewpoint of costs that > are > > associated with setting up / running a mechanism. CCWG may need > to map > > out the different cost elements to get a better idea and track > key > > areas of costs to determine how these would be funded. Need to > look at > > costs from a standalone perspective. ICANN's ongoing funding is > not > > set up to take care of this - all costs are expected to come out > of > > auction proceeds. Once implementation starts, this is expected to > come > > out of auction proceeds funding. > > * Further input on expected / max overhead costs may also be > needed. > > Board previously mentioned a 5% threshold. Is there flexibility > there > > to ensure efficiency / effectiveness balance? What is reasonable > and > > what is cost effective, depends on the circumstances and the > nature of > > the grants that are being made. % was never intended to be a hard > / > > fast line. % needs to be reasonable in light of the objectives of > the > > program. Focus should be on the use for proceeds in furtherance > of the > > mission instead of administrative costs. Could ask in work on > general > > description to provide an indication if overhead costs would be > closer > > to 3 or 10 %, for example. > > * Need to also evaluate mechanisms according to the defined > > principles mentioned in the Board letter. Factor this into the > draft > > response to charter questions. > > * Need to further consider how feasible tranching is as it will > > depend on size of fund allocation, similar would need to further > > discuss what mechanisms would need to be put in place that would > > warrant changes / corrections. Board is committed to the notion > that > > funds would be allocated over a period of time to be able to > ensure in > > earlier stages that proper controls are in place to monitor and > manage > > applications and evaluations. Board has not yet considered > possible > > size of fund allocation to projects. Objectives of fund > allocation > > determined by the community would hopefully further clarity / > guide > > that conversation. Intersection between size of projects and > costs of > > overhead. > > * One of the factors that will significantly impact costs, which > is > > not usually considered in any standard percentage, is the cost > > inherent to supporting a multistakeholder process: whether it is > to > > organize some community communication on the overall process of > the > > auction proceeds, or to support transparency and accountability > > mechanisms, these activities are rarely encountered elsewhere but > are > > prevalent at ICANN and are very resource consuming. That will > > significantly impact the costs incurred for the program. If you > take > > an illustration that the Drafting Team early on and now this CCWG > AP > > have been working on the topic for 2 years, with ICANN's support, > the > > costs is already significant and we have not even started > implementing > > anything. > > * CCWG could consider whether certain amounts are allocated to > > baskets to focus on certain types of projects, including > different > > sizes. CCWG to re-evaluate if that is a recommendation it would > like > > to made. > > * The topic of tranches is one of the operational consequence of > the > > board's fiduciary duty that the funds are used within mission and > > effectively: releasing funds in tranches to a given recipient > allows > > to establish accountability mechanisms for that recipient to > > demonstrate that the funds are appropriately used. The other > tranche > > topic is, as an example, to provide X million of dollars for > > allocation during a given year, which also allows to control the > > amount of effort required for evaluation and disbursement, > allowing > > to minimize risks of errors or issues. > > * As a reminder, Sarah Berg has been asked to assist with > developing > > a general description of each of these mechanisms. > > > > ACTION ITEM #1: CCWG leadership to work on first draft of > responses to > > charter questions, factoring in board input as well as discussion > > during today's meeting (31/5). To be circulated at the latest by > 18 > > June to allow for sufficient time for CCWG to review. > > > > ACTION ITEM #2: CCWG to consider developing list of cost elements > to > > get a better idea and track key areas of costs and determine how > these > > would be funded (from auction proceeds or differently). > > > > 4. Planning for ICANN62 > > > > * See email sent by Erika proposing to delay HIT session to > ICANN63 > > and have a F2F meeting instead which would include an update to > the > > community. In addition, leadership team is available to come and > speak > > to / present to those groups that are interested. CCWG could > consider > > other mechanisms to provide updates to the community for example > in > > the form of a webinar. Regular newsletters are already provided > to > > ensure that chartering organizations have regular status updates. > > > > ACTION ITEM #3: CCWG to move forward with the changes that have > been > > proposed (postpone HIT session to ICANN63 and change it to a F2F > > meeting instead. > > > > 5. Finalisation of preamble & reminder to review project examples > by > > Monday 4 June at 18:00 UTC > > > > * No further input received on the preamble so that document > should > > be considered final for inclusion in the Initial Report. > > > > ACTION ITEM #4: reminder, CCWG to review project examples by > Monday 4 > > June at 18.00 UTC at the latest. > > > > 6. Next steps & confirm next meeting (Thursday 7 or 14 June at > 14:00 > > UTC) > > > > * Next meeting to be scheduled for 14 June at 14.00 UTC. > > > > _MARIKA KONINGS_ > > > > _Vice President, Policy Development Support – GNSO, Internet > > Corporation for Assigned Names and Numbers (ICANN) _ > > > > _Email: marika.konings(a)icann.org _ > > > > _ _ > > > > _Follow the GNSO via Twitter @ICANN_GNSO_ > > > > _Find out more about the GNSO by taking our interactive courses > [2] > > and visiting the GNSO Newcomer pages [3]. _ > > > > > > > > Links: > > ------ > > [1] > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… > > [2] > https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses… > > [3] > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn… > > _______________________________________________ > > Ccwg-auctionproceeds mailing list > > Ccwg-auctionproceeds(a)icann.org > > https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds

2 3

Re: [Ccwg-auctionproceeds] [Ext] Re: [Ntfy-ccwg-auctionproceeds] Canceled: CANCELLED-CCWG New gTLD Auction Proceeds
by Marika Konings 12 Jun '18

12 Jun '18

Marilyn, your message may not have gone to the mailing list as it was sent to the ntfy list instead, so I am hereby reposting. One question I do have for you is what you expect with regards to community engagement? Compared to the previous meeting, there have not been any major new developments and/or draft recommendations that seem to warrant community consultation / engagement, as such, the idea was to provide a status update (what has happened between ICANN61 and ICANN62), outline expected next steps and identify when the next engagement opportunities are expected. Is there something that is missing from this update from your perspective? Best regards, Marika From: Marilyn Cade <marilynscade(a)hotmail.com> Date: Tuesday, June 12, 2018 at 06:27 To: ICANN Policy Calendar <PolicyCalendar(a)icann.org>, "ntfy-ccwg-auctionproceeds(a)icann.org" <ntfy-ccwg-auctionproceeds(a)icann.org>, Marika Konings <marika.konings(a)icann.org>, Joke Braeken <joke.braeken(a)icann.org>, Emily Barabas <emily.barabas(a)icann.org>, Nathalie Peregrine <nathalie.peregrine(a)icann.org>, Michelle DeSmyter <michelle.desmyter(a)icann.org>, Andrea Glandon <andrea.glandon(a)icann.org>, Terri Agnew <terri.agnew(a)icann.org>, Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Re: [Ntfy-ccwg-auctionproceeds] Canceled: CANCELLED-CCWG New gTLD Auction Proceeds While I appreciate that the leadership team is seeking more time, this puts the participants at a disadvantage as not all will be able to attend ICANN62 in person, and we really need to prepare for engaging with the ICANN community while we are in Panama. Just saying that there can be casual 15 minute updates from the co chairs is not really an effective approach to engagement with the community. I know we all know that. So, what to do? Let me propose that CCWG-AP hold a meeting on Monday or Tuesday, and all of us will do our best but to have at least a discussion BEFORE ICANN62. I am sure all of us will do our best to shift things around so that we can have a working session BEFORE ICANN62. ________________________________ From: ICANN Policy Calendar <PolicyCalendar(a)icann.org> Sent: Tuesday, June 12, 2018 8:21 AM To: ntfy-ccwg-auctionproceeds(a)icann.org; Marika Konings; Joke Braeken; Emily Barabas; Nathalie Peregrine; Michelle DeSmyter; Andrea Glandon; Terri Agnew; Julie Bisland Subject: [Ntfy-ccwg-auctionproceeds] Canceled: CANCELLED-CCWG New gTLD Auction Proceeds When: Thursday, June 14, 2018 10:00 AM-11:30 AM. Where: 14:00 UTC As more time is needed by the leadership team to develop proposed responses to the draft charter questions, this week's meeting is cancelled. The CCWG will reconvene during ICANN62 on Wednesday 27 June from 15.15 - 16.45 local time. The leadership team anticipates sharing the proposes responses well in advance to allow for review prior to the meeting Meeting: CCWG New gTLD Auction Proceeds call Date/Time: Recurring meeting every Thursday beginning 17 May 2018 at 14:00 UTC for 90 minutes, ending 21 June 2018 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Friday) 00:00 Melbourne AEST For other times: https://tinyurl.com/yaj3wqy8 [nam03.safelinks.protection.outlook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam03.safelinks.protec…> Agenda Wiki: https://community.icann.org/x/khAFBQ [nam03.safelinks.protection.outlook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam03.safelinks.protec…> New Connection Information New Web conference tool: Adobe Connect Please join the meeting room here: https://participate.icann.org/newgtlds-auction [nam03.safelinks.protection.outlook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__nam03.safelinks.protec…> If you require a dial-out or to send apologies (do not send to full working group) please send an email request with your preferred contact number to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> If you cannot join the WebEx room join via telephone listed below. Please let me know if you have any questions. Thank you. Kind regards, Julie ______________________________________________________________________ Participant passcode: AUCTION Dial in numbers: Country Toll Toll Free ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL RIO DE JANEIRO: 55-21-40421490 0800-7610651 BRAZIL SAO PAULO: 55-11-3958-0779 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CROATIA 080-08-06-309 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 EGYPT 0800000-9029 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 36-1-700-8856 06-800-12755 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 ITALY ROME: 39-06-8751-6018 800-986-383 ITALY TORINO: 39-011-510-0118 800-986-383 JAPAN OSAKA: 81-6-7878-2631 0066-33-132439 JAPAN TOKYO: 81-3-6868-2631 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 8002-9246 MALAYSIA 1-800-81-3065 MEXICO GUADALAJARA (JAL): 52-33-3208-7310 001-866-376-9696 MEXICO MEXICO CITY: 52-55-5062-9110 001-866-376-9696 MEXICO MONTERREY: 52-81-2482-0610 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 1800-111-42453 POLAND 00-800-1212572 PORTUGAL 351-2-10054705 8008-14052 ROMANIA 40-31-630-01-79 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 0800-002066 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 TURKEY 00-800-151-0516 UNITED ARAB EMIRATES 8000-35702370 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 VIETNAM 120-11751

2 1

ICANN62: GNSO Sessions How to Get Organized and Remote Participation Details
by Nathalie Peregrine 06 Jun '18

06 Jun '18

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings’ team has put together an updated ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN62 Meeting Schedule<https://62.schedule.icann.org/> GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ> Step 1 – Create a profile and your personalized ICANN62 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you’ve added all your chosen meetings to “My Schedule” go to Export. 1. Importing creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. 2. Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. * For Outlook calendars: http://support.pathable.com/knowledgebase/articles/81449-moving-your-schedu…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> * For Google calendars: http://support.pathable.com/knowledgebase/articles/1313-moving-your-schedul…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> Step 3 All Adobe Connect rooms (which can be found on the session information on the Meeting Schedule<https://62.schedule.icann.org/> and on the GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ>) will provide audio streaming only Adobe Connect room microphones will not be enabled. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ> for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Step 4 Please download the mobile app by searching for “ICANN62” in your app stores. Nathalie Peregrine and Terri Agnew will be onsite in Panama to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<applewebdata://FB60497E-61D8-4FE9-BF9C-EB238191E416/gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

REMINDER TO REGISTER IN ADVANCE / Announcement: Pre-ICANN62 Policy Webinar
by Terri Agnew 04 Jun '18

04 Jun '18

https://www.icann.org/news/announcement-2018-05-23-en Register Now: Pre-ICANN62 Policy Webinar - 12 June 2018 The Policy Development Support Team is pleased to announce two webinar sessions to assist with the community's preparations for the ICANN62 Policy Forum: Pre-ICANN62 Policy Webinar Tuesday, 12 June 2018 10:00 and 19:00 Coordinated Universal Time (UTC) The webinar will run in English with simultaneous Spanish interpretation. The presentation materials will be translated into Spanish, and posted following the Webinar with the recordings of the sessions <https://www.icann.org/resources/pages/presentations-2012-08-27-en> here. Please register via <https://goo.gl/vZw8kM> this form by 11 June 2018! In this 90-minute webinar, the Policy Development Support Team will summarize the key policy activities taking place across the ICANN community. The Team will also answer your questions about ongoing community policy and advisory work and discuss what to expect at the ICANN62Policy Forum. To ensure that your questions about policy activities are addressed during the session, the Policy Team invites you to submit your questions through the <https://goo.gl/forms/dVbmhQOT8sakSsmg2> registration form or by email to <mailto:policyinfo@icann.org> policyinfo(a)icann.org. To assist with your preparation for this webinar and for ICANN62, the "Pre-ICANN62 Policy Report" and "Generic Names Supporting Organization Policy Briefing: ICANN62 Edition" will be published by Tuesday, 5 June 2018. Please be sure to download and review these materials beforehand for helpful background on policy activities and topics that the Policy Development Support Team will cover during the webinar, such as: * The cross-community discussions that will take place at ICANN62: * Geographic Names at the Top-Level (Work Track 5) * Update from the Registration Directory Service-WHOIS2 Review Team * General Data Protection Regulation (GDPR) Compliance, Access to WHOIS and Accreditation * The expected Initial Report from the New generic Top-Level Domain (gTLD) Auction Proceeds Cross Community Working Group * Presentation of the Final CCWG-Accountability Work Stream 2 Recommendations * The various policy development processes underway in the Country Code Names Supporting Organization (ccNSO), the Generic Names Supporting Organization (GNSO) and the Address Supporting Organization (ASO): * Retirement of Country Code Top-Level Domains * Review of All Rights Protection Mechanisms in All gTLDs * Next steps in relation to Registration Directory Services policy work * Curative Rights Protections for International Governmental Organizations and International Non-Governmental Organizations * New gTLD Subsequent Procedures * Regional Internet Registry policy development activities * Advisory Committee activities within the At Large Advisory Committee (ALAC), Governmental Advisory Committee (GAC), Root Server System Advisory Committee (RSSAC) and Security & Stability Advisory Committee (SSAC): * Organizational Review of the At-Large community: Next steps, implementation, and ALACsessions during ICANN62 * GDPR and Key Signing Key (KSK) Rollover discussions * At-Large discussion on new gTLDs and Work Tracks 1-5 * Regional At-Large Organization (RALO) Policy Hot Topics * GAC discussions on .amazon, IGO protections and 2-character codes at the second level * Board-GAC GDPR consultations * RSSAC statement on the distinction between RSSAC and Root-Ops (RSSAC033) * SSAC work concerning name collisions * Other topics of note: * Organizational Review of the ASO * ccNSO sessions on disaster and recovery and business continuity, ccNSO members meeting sessions, and Tech Day. * GAC onboarding initiatives * Report from the RSSAC May 2018 Workshop (RSSAC034) To complement this Pre-ICANN62 Policy Webinar, the GNSO Policy Development Support Team will host, with the Council leadership and Policy Development Process (PDP) working group chairs, a GNSOpolicy-focused webinar on Monday, 18 June 2018 at 21:00 UTC for 90 minutes. This webinar is intended to serve as a replacement for the previously-offered GNSO PDP updates provided during the GNSO weekend sessions and will assist the community in preparing for GNSO policy-related discussions at ICANN62. If you would like to participate in the GNSO Policy Webinar, please register <https://docs.google.com/forms/d/1Z5ENBC3wa2IOvAeYr27-pGU0lJIEeZCmgZkpAo2l0S 0/edit> here. The Policy Development Support Team looks forward to helping the ICANN community prepare for ICANN62!

1 0