- ECAdmin - lists.icann.org

UPDATE (Re: Error in ICANN Announcement of the start of the Rejection Action Petition Periods triggered by the Board's Budget and Operating Plan approvals on Friday)
by Mary Wong June 26, 2017

June 26, 2017

Dear all, Please note that the announcement on the ICANN website about the triggering of the Empowered Community’s rejection power has been updated with additional information about the process and a link to the relevant ICANN Bylaws: https://www.icann.org/news/announcement-2017-06-24-en Thank you. Cheers Mary From: Stephen Deerhake <sdeerhake(a)nic.as> Organization: AS Domain Registry Reply-To: "sdeerhake(a)nic.as" <sdeerhake(a)nic.as> Date: Monday, June 26, 2017 at 09:20 To: John Jeffrey <john.jeffrey(a)icann.org>, "sdeerhake(a)nic.as" <sdeerhake(a)nic.as> Cc: Mary Wong <mary.wong(a)icann.org>, "katrina(a)nic.lv" <katrina(a)nic.lv>, "ecadmin(a)icann.org" <ecadmin(a)icann.org>, Chris Disspain <chris(a)disspain.uk>, Bart Boswinkel <bart.boswinkel(a)icann.org>, David Olive <david.olive(a)icann.org> Subject: [Ext] RE: [ECAdmin] Error in ICANN Announcement of the start of the Rejection Action Petition Periods triggered by the Board's Budget and Operating Plan approvals on Friday, Posting the Bylaw section in the announcement would certainly provide the background and thus the clarification that I am seeking. Thanks for this suggestion! Best Regards, Stephen Deerhake ccNSO Representative to the Empowered Community Administration ccNSO Council Member AS Domain Registry GDNS, LLC +1 212 334 3660 +1 212 656 1982 (fax) +1 917 744 7313 (mobile) From: John Jeffrey [mailto:john.jeffrey@icann.org] Sent: Sunday, June 25, 2017 12:53 PM To: sdeerhake(a)nic.as Cc: Mary Wong <mary.wong(a)icann.org>; katrina(a)nic.lv; ecadmin(a)icann.org; Chris Disspain <chris(a)disspain.uk>; Bart Boswinkel <bart.boswinkel(a)icann.org>; David Olive <david.olive(a)icann.org> Subject: Re: [ECAdmin] Error in ICANN Announcement of the start of the Rejection Action Petition Periods triggered by the Board's Budget and Operating Plan approvals on Friday, Perhaps we should post the Bylaw sections. Indicating a correction was requested by Stephen to be clear and accurate. Sent from my iPhone On Jun 25, 2017, at 6:10 PM, Stephen Deerhake <sdeerhake(a)nic.as<mailto:sdeerhake@nic.as>> wrote: Greetings Mary, The announcement reads: Decisional Participants of the Empowered Community have 28 days to bring forth a petition to reject any of these documents. It’s very nicely written for what it omits. It omits the fact that a member of a Decisional Participant SO/AC has 21 days to both submit their rejection petition to their Decisional Participant decision-making body, and get said decision making body to agree to sponsor. It. It doesn’t describe how the Rejection Action Petitioning Decisional Period has only a week to (a) secure a buy-in from another Decisional Participant so they have the required support of Rejection Action Supporting Decisional Participant, get both their paperwork and that of the Supporting Decisional Participant to the Empowered Community Administration, who in turn need to notify the ICANN Secretary. So yes, on one level it is technically accurate. In reality, it is much less so, and needs to be corrected, and the correction publicized. Best Regards, Stephen Deerhake ccNSO Representative to the Empowered Community Administration ccNSO Council Member AS Domain Registry GDNS, LLC +1 212 334 3660 +1 212 656 1982 (fax) +1 917 744 7313 (mobile) From: Mary Wong [mailto:mary.wong@icann.org] Sent: Sunday, June 25, 2017 11:40 AM To: sdeerhake(a)nic.as<mailto:sdeerhake@nic.as>; John Jeffrey <john.jeffrey(a)icann.org<mailto:john.jeffrey@icann.org>> Cc: katrina(a)nic.lv<mailto:katrina@nic.lv>; ecadmin(a)icann.org<mailto:ecadmin@icann.org> Subject: Re: [ECAdmin] Error in ICANN Announcement of the start of the Rejection Action Petition Periods triggered by the Board's Budget and Operating Plan approvals on Friday, Dear Stephen and other members of the Empowered Community Administration, Thank you for your message. As you noted, under Section 2.2(b) of Annex D of the Bylaws, there is a 21-day Rejection Action Petition Period (commencing with the delivery of the Secretary’s Notice) during which time an individual may petition a Decisional Participant seeking to initiate the Rejection Process. Section 2.2(d) then provides that, in order for the Rejection Process to move forward, a Decisional Participant who accepts the Rejection Action Petition must obtain the support of at least one other Decisional Participant. Such support must be obtained during the 7-day period that immediately follows on the 21-day Rejection Action Petition Period. If the Petitioning Decisional Participant is unable to obtain the requisite support within this 7-day period, the Rejection Process is terminated automatically. In short, the Empowered Community has a total of 28 days to bring forward a Rejection Action Petition pursuant to the procedures described in Annex D since, if no notice of such a petition is timely delivered, the ICANN and IANA Budgets become effective on the 28th day following the required notification date. This is reflected in the language in Sections 22.4 and 22.5 of the Bylaws, and is what staff was attempting to describe in the announcement you referenced. We are sorry if the language of the announcement caused any confusion for you or your community groups. I hope this email helps to clarify the situation and timeline. Cheers Mary Mary Wong Senior Policy Director & Special Adviser for Strategic Policy Planning Internet Corporation for Assigned Names and Numbers (ICANN) Email: mary.wong(a)icann.org<mailto:mary.wong@icann.org> Telephone: +1-603-5744889 From: <ecadmin-bounces(a)icann.org<mailto:ecadmin-bounces@icann.org>> on behalf of Stephen Deerhake <sdeerhake(a)nic.as<mailto:sdeerhake@nic.as>> Organization: AS Domain Registry Reply-To: "sdeerhake(a)nic.as<mailto:sdeerhake@nic.as>" <sdeerhake(a)nic.as<mailto:sdeerhake@nic.as>> Date: Sunday, June 25, 2017 at 09:01 To: John Jeffrey <john.jeffrey(a)icann.org<mailto:john.jeffrey@icann.org>> Cc: "katrina(a)nic.lv<mailto:katrina@nic.lv>" <katrina(a)nic.lv<mailto:katrina@nic.lv>>, "ecadmin(a)icann.org<mailto:ecadmin@icann.org>" <ecadmin(a)icann.org<mailto:ecadmin@icann.org>> Subject: [ECAdmin] Error in ICANN Announcement of the start of the Rejection Action Petition Periods triggered by the Board's Budget and Operating Plan approvals on Friday, Greetings JJ. I note that ICANN has posted an announcement of the start of the Rejection Action Petition Periods in response to the Board’s actions at their workshop on Friday. The announcement I am referencing may be found at https://www.icann.org/news/announcement-2017-06-24-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…>. Please note that there is an important error in the announcement that needs correcting. About 5 paragraphs into the announcements, ICANN States: “Each of these documents will come into effect only after giving the Empowered Community time to consider whether it will raise a petition rejecting the budgets and/or operating plans. Decisional Participants of the Empowered Community have 28 days to bring forth a petition to reject any of these documents.” This is incorrect. Section 2.2(b) of Annex D states: (b) During the period beginning on the Rejection Action Board Notification Date and ending at 11:59 p.m. (as calculated by local time at the location of ICANN's principal office) on the date that is the 21st day after the Rejection Action Board Notification Date (as it relates to a particular Rejection Action, the "Rejection Action Petition Period"), subject to the procedures and requirements developed by the applicable Decisional Participant, an individual may submit a petition to a Decisional Participant, seeking to reject the Rejection Action and initiate the Rejection Process (a "Rejection Action Petition").” Thus the Rejection Action Petition Period is 21 days rather than 28 days, and this correction needs to be made to the announcement and brought to the Community’s attention ASAP. Thank you. Best Regards, Stephen Deerhake ccNSO Representative to the Empowered Community Administration ccNSO Council Member AS Domain Registry GDNS, LLC +1 212 334 3660 +1 212 656 1982 (fax) +1 917 744 7313 (mobile) sdeerhake(a)nic.as<mailto:sdeerhake@nic.as> sdeerhake(a)gdns.net<mailto:sdeerhake@gdns.net>

3 2

Final Slides for Community Forum at ICANN59
by Mary Wong June 26, 2017

June 26, 2017

Dear Empowered Community Administration representatives, Following consultation with Chris Disspain, the Board representative who will join you on the panel for the Community Forum tomorrow, staff has added one slide to the original slide deck that was sent to you last week. This additional slide (Slide #5 in the attachment) briefly describes the proposed Fundamental Bylaw amendments, and we have inserted it in between the introductory overview to the Empowered Community and its powers, and the slides describing the Approval Action process. Stephen – as some of the slides in the deck were prepared by you, staff is assuming that you’ll also be doing the presentation on behalf of the Empowered Community Administration. If you’d like Chris to present the additional slide, please feel free to let him know. Thanks and cheers Mary From: Mary Wong <mary.wong(a)icann.org> Date: Thursday, June 22, 2017 at 05:24 To: "ecadmin(a)icann.org" <ecadmin(a)icann.org> Subject: FOR COMMENT: Slides for Community Forum at ICANN59 Dear Empowered Community Administration representatives, Please find attached a short slide deck which staff has helped Stephen Deerhake (ccNSO representative) to prepare. The idea is that these slides will be used as an introductory overview for the upcoming Community Forum scheduled for Tuesday, 27 June, from 0800-0900 Johannesburg time; and that the preference will be to keep presentations as short as possible, with more time given over to audience participation, Q&A and interactive discussion. Please send any comments you may have on the slides to this list at your earliest convenience, and preferably no later than Friday 23 June. FYI I believe that we have not yet received any written submissions from any SO/AC on the proposed Fundamental Bylaw amendment that is the subject of the planned Community Forum in Johannesburg. Thanks and cheers Mary (on behalf of the staff supporting the Empowered Community and the Empowered Community Administration)

1 0

Error in ICANN Announcement of the start of the Rejection Action Petition Periods triggered by the Board's Budget and Operating Plan approvals on Friday,
by Stephen Deerhake June 26, 2017

June 26, 2017

Greetings JJ. I note that ICANN has posted an announcement of the start of the Rejection Action Petition Periods in response to the Board's actions at their workshop on Friday. The announcement I am referencing may be found at https://www.icann.org/news/announcement-2017-06-24-en. Please note that there is an important error in the announcement that needs correcting. About 5 paragraphs into the announcements, ICANN States: "Each of these documents will come into effect only after giving the Empowered Community time to consider whether it will raise a petition rejecting the budgets and/or operating plans. Decisional Participants of the Empowered Community have 28 days to bring forth a petition to reject any of these documents." This is incorrect. Section 2.2(b) of Annex D states: (b) During the period beginning on the Rejection Action Board Notification Date and ending at 11:59 p.m. (as calculated by local time at the location of ICANN's principal office) on the date that is the 21st day after the Rejection Action Board Notification Date (as it relates to a particular Rejection Action, the "Rejection Action Petition Period"), subject to the procedures and requirements developed by the applicable Decisional Participant, an individual may submit a petition to a Decisional Participant, seeking to reject the Rejection Action and initiate the Rejection Process (a "Rejection Action Petition")." Thus the Rejection Action Petition Period is 21 days rather than 28 days, and this correction needs to be made to the announcement and brought to the Community's attention ASAP. Thank you. Best Regards, Stephen Deerhake ccNSO Representative to the Empowered Community Administration ccNSO Council Member AS Domain Registry GDNS, LLC +1 212 334 3660 +1 212 656 1982 (fax) +1 917 744 7313 (mobile) sdeerhake(a)nic.as <mailto:sdeerhake@nic.as> sdeerhake(a)gdns.net <mailto:sdeerhake@gdns.net>

4 5

Still waiting for a correction to the ICANN Announcement page..
by Stephen Deerhake June 25, 2017

June 25, 2017

Greetings to you both. I note that as of my writing this the Rejection Action Petition Announcement web page on the ICANN web site https://www.icann.org/news/announcement-2017-06-24-en has yet to be corrected as per my brief conversation with you both this morning, and also per an email to the ICANN Corporate Secretary that I sent to him when I first discovered the error even earlier this morning. To recap: The ICANN Web page announcement states that the Rejection Action Petition Period is 28 days. THIS IS INCORRECT. The correct time limit for the Rejection Action Petition Period is 21 days (Annex D Section 2.2(b)) rather than 28 days. I believe the 28 day notion came from an incorrect reading by someone within ICANN of Article 22.4(a)(vi)(A)(2) in the case of the ICANN Budget, Article 22.4((b)(A)(2) in the case of the IANA Budget, Article 22.5(a)(vi)(A)(2) in the case of the Operating Plan, and Article 22.5(b)(A)(2) in the case of the Strategic Plan. These specific sections relate to the minimum number of days that will transpire between the initiation of a Rejection Notice Period as defined in Annex D Section 2.2(b) and when the Budget or Plan subject to the Board Rejection Notice can come into effect. The controlling language regarding the length of the Rejection Action Petition Period is clearly stated in Section 2.2(b) of Annex D as 21 days from the Rejection Action Board Notification Date. So long as this critical error remains uncorrected, ICANN is in effect miss-leading the Empowered Community with respect to their rights under the Bylaws and the specific operational requirements for exercising those rights as detailed in Annex D. I am not (yet) formally stating that this is intentional on ICANN's part, but I made the seriousness of this error clear to both of you to this morning, as well as in my prior correspondence to the Corporate Secretary. I really fail to see how it takes over six hours to make a change of this importance to the ICANN Website. But now by not correcting (and publicizing the correction) ASAP once ICANN was notified of the error, ICANN is in effect manipulating the Rejection Action Petition Process by misleading the Empowered Community with respect to how much time they have to react to the Board's decisions which led to the issuance of the Rejection Action Board Notices. Please have appropriate ICANN Staff attend to this issue immediately. Thank you. Best Regards, Stephen Deerhake ccNSO Representative to the Empowered Community Administration ccNSO Council Member AS Domain Registry GDNS, LLC +1 212 334 3660 +1 212 656 1982 (fax) +1 917 744 7313 (mobile) sdeerhake(a)nic.as <mailto:sdeerhake@nic.as> sdeerhake(a)gdns.net <mailto:sdeerhake@gdns.net>

2 1

Error in ICANN Announcement of the start of the Rejection Action Petition Periods triggered by the Board's Budget and Operating Plan approvals on Friday,
by Stephen Deerhake June 25, 2017

June 25, 2017

Greetings JJ. I note that ICANN has posted an announcement of the start of the Rejection Action Petition Periods in response to the Board's actions at their workshop on Friday. The announcement I am referencing may be found at https://www.icann.org/news/announcement-2017-06-24-en. Please note that there is an important error in the announcement that needs correcting. About 5 paragraphs into the announcements, ICANN States: "Each of these documents will come into effect only after giving the Empowered Community time to consider whether it will raise a petition rejecting the budgets and/or operating plans. Decisional Participants of the Empowered Community have 28 days to bring forth a petition to reject any of these documents." This is incorrect. Section 2.2(b) of Annex D states: (b) During the period beginning on the Rejection Action Board Notification Date and ending at 11:59 p.m. (as calculated by local time at the location of ICANN's principal office) on the date that is the 21st day after the Rejection Action Board Notification Date (as it relates to a particular Rejection Action, the "Rejection Action Petition Period"), subject to the procedures and requirements developed by the applicable Decisional Participant, an individual may submit a petition to a Decisional Participant, seeking to reject the Rejection Action and initiate the Rejection Process (a "Rejection Action Petition")." Thus the Rejection Action Petition Period is 21 days rather than 28 days, and this correction needs to be made to the announcement and brought to the Community's attention ASAP. Thank you. Best Regards, Stephen Deerhake ccNSO Representative to the Empowered Community Administration ccNSO Council Member AS Domain Registry GDNS, LLC +1 212 334 3660 +1 212 656 1982 (fax) +1 917 744 7313 (mobile) sdeerhake(a)nic.as<mailto:sdeerhake@nic.as> sdeerhake(a)gdns.net<mailto:sdeerhake@gdns.net>

1 0

Notices of 24 June 2017 Approvals of FY18 Budgets and Operating Plans
by John Jeffrey June 24, 2017

June 24, 2017

Please see the attached Notices of the Board’s approval of: 1. The FY18 Operating Plan and Budget 2. The FY18 IANA Budget 3. The FY18 Five Year Operating Plan Update For your reference I am also attaching the Budgets and Operating Plans as approved. Best, John Jeffrey General Counsel & Secretary, ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, California 90094-2536 direct dial - +1.310.301.5834 mobile - +1.310.404.6001 JJ(a)ICANN.org<mailto:JJ@ICANN.org>

1 0

FOR COMMENT: Slides for Community Forum at ICANN59
by Mary Wong June 22, 2017

June 22, 2017

Dear Empowered Community Administration representatives, Please find attached a short slide deck which staff has helped Stephen Deerhake (ccNSO representative) to prepare. The idea is that these slides will be used as an introductory overview for the upcoming Community Forum scheduled for Tuesday, 27 June, from 0800-0900 Johannesburg time; and that the preference will be to keep presentations as short as possible, with more time given over to audience participation, Q&A and interactive discussion. Please send any comments you may have on the slides to this list at your earliest convenience, and preferably no later than Friday 23 June. FYI I believe that we have not yet received any written submissions from any SO/AC on the proposed Fundamental Bylaw amendment that is the subject of the planned Community Forum in Johannesburg. Thanks and cheers Mary (on behalf of the staff supporting the Empowered Community and the Empowered Community Administration)

1 0

Following up: ICANN Community Forum in Johannesburg
by Mary Wong June 20, 2017

June 20, 2017

Dear Empowered Community Administration, Thanks very much to Stephen for the arrangements he has suggested for managing the upcoming Community Forum on Tuesday 27 June in Johannesburg. While we (support staff) confirm the logistics, room arrangements and remote participation facilities with our Meetings Team colleagues, I wanted to follow up with you on a number of things that were noted during our planning for this session. On community preparations for the Forum: * We will be sending out a note to all SO/AC leaders shortly, reminding them that, under the Bylaws, all SO/ACs (and not just Decisional Participants) “may deliver to the EC Administration in writing its views and questions on the Approval Action prior to the convening of and during the Approval Action Community Forum” (Annex D, Section 1.3(f)). Any such written comments received will be posted to the ICANN website, and staff will of course notify you if any come in before the Forum, in case you wish to address them during the Forum itself. * Staff had offered previously to provide a briefing to each of your communities on the overall Approval Action process, including the Community Forum and important dates and deadlines. If your community group has some time during its meeting schedule at ICANN59, we will be very happy to come in and do that briefing. Alternatively, we can also schedule a webinar shortly following the meeting if that works better for you and your groups. On Empowered Community Administration preparation for the Forum: * Similarly, if the Empowered Community Administration itself would like a brief run-through of the overall process, we’d be happy to do a call with you prior to your departure for Johannesburg next week, if possible. Alternatively, we will be happy to meet briefly with you in Johannesburg before Tuesday 27 June if you prefer. * Staff will contact Chris Disspain and our Board support colleagues to confirm who from the Board will also be in attendance at the Community Forum, noting that under the Bylaws “Directors representing the Board are expected to attend the Approval Action Community Forum in order to address any questions or concerns regarding the Approval Action” (Annex D, Section 1.3(g).) * Last but not least – for Stephen: if you would like to send the slides you are planning to use to this list, I’d be happy to put them into the official ICANN59 template following any comments from the other Empowered Community Administration representatives. As such, it will be greatly appreciated if the other Empowered Community Administration representatives can provide their comments as soon as possible. Thank you all, Mary (on behalf of ICANN staff supporting the Empowered Community and the Empowered Community Administration) On 6/7/17, 13:20, "Stephen Deerhake" <sdeerhake(a)nic.as> wrote: Greetings fellow ECA members, and Mary. First, thanks to you Mary, and the ICANN meetings staff for choosing the appropriate meeting set up --I believe this grew out of an SO/AC - ICANN59 tele-conference in which I recently participated. I think we got the logistics/room format pretty well sorted then, although I have not had any formal follow up. Given that we are apparently in the GAC room, and they need to fire up their meeting straight away at 09.00h, I believe minimal changes are required from their set-up, other than the ability to have either mics or roaming mics available, as well as translation (which is a given for that meeting room if I am not mistaken). I believe that your assumption "that all five community representatives on the Empowered Community Administration, plus the relevant Board members in charge of “shepherding” the proposed Board Committee handover under the proposed Fundamental Bylaw amendment, will be seated at the head table." is accurate. That's what I had in the back of my mind. As this Fundamental Bylaw change was initiated by one of my two ccNSO Board representatives, I had previously offered my services to take the lead on this with regards to the Community Forum organisation, and if I am not mistaken, my fellow ECA colleagues agreed to the same. I have prepared brief (5 min) comments about the occasion, the role of the Empowered Community Administration (basically paper pushing and vote counting --not decisional!), an introduction of my fellow ECA Colleagues, an introduction to the proposed fundamental Bylaw change, and then I thought I would offer the floor to my fellow ECA Colleagues should they wish to make remarks. After that, my plan was to turn the floor over to Chris Disspain (I have been in discussions with him about this) who would make his case for the fundamental Bylaw change (after all, it is of his making), and then solicit questions from the audience, which Chris will have to respond to. He's OK with this. I have a short set of questions for Chris should there be nothing forthcoming from the Community, although based on the public comments, I think we are going to get a couple from the audience... if you guys have one of those fancy-pants ;-) ICANN-logoed slide sets that illustrates the proposed fundamental By-law change, that would be great. I describe it in my remarks, but my PowerPoint presentations tend to be non-graphical and mono-chromatic. I think otherwise we are pretty set. I invite my fellow ECA Colleagues to weigh in on the matters that you have raised as well. Best Regards, Stephen Deerhake ccNSO Representative to the Empowered Community Administration ccNSO Council Member AS Domain Registry GDNS, LLC sdeerhake(a)nic.as sdeerhake(a)gdns.net -----Original Message----- From: Mary Wong [mailto:mary.wong@icann.org] Sent: Monday, June 05, 2017 7:07 AM To: Alan Greenberg <alan.greenberg(a)mcgill.ca>; sdeerhake(a)nic.as; James Bladel <jbladel(a)godaddy.com>; 'John Curran' <jcurran(a)arin.net>; Thomas.Schneider(a)bakom.admin.ch Cc: ecadmin(a)icann.org Subject: Re: [ECAdmin] Do you feel the need for a publicly-available conference call prior to the Community Public Forum at ICANN-59 in JNB? Dear Empowered Community Administration, Following up on the thread below, staff would like to seek your guidance as to the format, logistics and overall conducting of the upcoming Community Forum at ICANN59. As you know, this has been scheduled for the morning of Tuesday 27 June (Day 2 of the meeting). In submitting the session request, staff took the liberty of requesting a room that can be set up as for an ICANN Public Forum (i.e. with a head table, the room otherwise in theater-style, with standing mics in the aisles for audience speakers, remote participation (Adobe Connect) facilities, and (possibly) roving mics and staff around the room. We are assuming that all five community representatives on the Empowered Community Administration, plus the relevant Board members in charge of “shepherding” the proposed Board Committee handover under the proposed Fundamental Bylaw amendment, will be seated at the head table. We are also assuming that you will want to do a very brief overview of the approval process (since this is the first time the Empowered Community is exercising this power), for which we can help with slides if you wish; and that a Board member will also give a very brief overview of the amendment that is being proposed. Other than that, do you have any thoughts about which of you will lead and/or moderate the discussion, or do you wish to use the services of a professional moderator? Please let us know your suggestions, and let us know also if you think a call amongst ourselves to discuss the logistics will be helpful. Thanks and cheers Mary On 5/31/17, 10:28, "ecadmin-bounces(a)icann.org on behalf of Alan Greenberg" <ecadmin-bounces(a)icann.org on behalf of alan.greenberg(a)mcgill.ca> wrote: I see no need for such a call. We do enough conference calls that we do not need to "practice" for them. Alan At 30/05/2017 10:05 PM, Stephen Deerhake wrote: >Greetings fellow ECA members, > >As you have seen (or will shortly see, once the >ICANN 59 schedule is posted) that we are set to >hold the first ever Community Forum under the >new Bylaws from 08.00-09.00h on Tuesday, 27.06.2017. > >Per Annex D, Section 1.3(2) we (the Empowered >Community Administration) may request that ICANN >set up a "…publically available conference >call…" prior to the Community Forum between >ourselves and the Decisional Participants. > >Personally, I do not see the need for such a >call, but I thought I should solicit your >opinions on this prior to providing ICANN formal >notice regarding the scheduling (or non-scheduling) of such call. > >Can you please let me know within the next >couple of days if you feel you would like such a >tele-conference call to be scheduled? Otherwise >I will notifiy ICANN at week's end that it will >not be necessary to plan the call. > > >Best Regards, > >/Stephen _______________________________________________ ECAdmin mailing list ECAdmin(a)icann.org https://mm.icann.org/mailman/listinfo/ecadmin

3 4

Do you feel the need for a publicly-available conference call prior to the Community Public Forum at ICANN-59 in JNB?
by Stephen Deerhake June 7, 2017

June 7, 2017

Greetings fellow ECA members, As you have seen (or will shortly see, once the ICANN 59 schedule is posted) that we are set to hold the first ever Community Forum under the new Bylaws from 08.00-09.00h on Tuesday, 27.06.2017. Per Annex D, Section 1.3(2) we (the Empowered Community Administration) may request that ICANN set up a ".publically available conference call." prior to the Community Forum between ourselves and the Decisional Participants. Personally, I do not see the need for such a call, but I thought I should solicit your opinions on this prior to providing ICANN formal notice regarding the scheduling (or non-scheduling) of such call. Can you please let me know within the next couple of days if you feel you would like such a tele-conference call to be scheduled? Otherwise I will notifiy ICANN at week's end that it will not be necessary to plan the call. Best Regards, /Stephen

4 5

CORRECTION - Re: Empowered Community’s Approval of Amendments to ICANN’s Fundamental Bylaws
by Mary Wong May 31, 2017

May 31, 2017

Dear Empowered Community Administration representatives and Decisional Participant chairs, Alan Greenberg correctly pointed out that per the Bylaws, if the Community Forum is held during the next scheduled ICANN public meeting and that public meeting is held after 11:59pm (as calculated by local time at the location of ICANN’s principal office) on the 30th day after the Approval Action Board Notification Date, the Community Forum Period shall expire at 11:59pm, local time. As such paragraph four below should be read as: “After the Community Forum period ends at 21:59 UTC (23.59 Johannesburg time) on 29 June 2017, Decisional Participants have 21 days to take a decision on the Fundamental Bylaws amendments. Decisional Participants must act, or choose not to act, by 06:59 UTC on 21 July 2017. At least three Decisional participants must support and no more than one can object for the Fundamental Bylaws amendments to be approved.” Thank you, and please accept our apologies for the initial error regarding the applicable UTC times. Best regards, Mary Mary Wong Senior Policy Director & Special Adviser for Strategic Policy Planning Internet Corporation for Assigned Names and Numbers (ICANN) Email: mary.wong(a)icann.org<mailto:mary.wong@icann.org> Telephone: +1-603-5744889 From: David Olive <david.olive(a)icann.org> Date: Friday, May 26, 2017 at 15:40 To: "ecadmin(a)icann.org" <ecadmin(a)icann.org> Cc: Thomas Schneider <thomas.schneider(a)bakom.admin.ch>, Alan Greenberg <alan.greenberg(a)mcgill.ca>, Katrina Sataki <katrina(a)nic.lv>, "James M. Bladel" <jbladel(a)godaddy.com>, "chair(a)nro.net" <chair(a)nro.net> Subject: Empowered Community’s Approval of Amendments to ICANN’s Fundamental Bylaws Communication to EC Admin and Decisional Participants Dear EC Admin Representatives: On 23 May 2017, the ICANN organization sent a notice<https://www.icann.org/en/system/files/bm/secretarys-notice-2-redacted-23may…> to the Empowered Community that the ICANN Board has approved<https://www.icann.org/resources/board-material/resolutions-2017-05-18-en#1.c> amendments to ICANN’s Fundamental Bylaws to move the Board Governance Committee’s reconsideration responsibilities to another Board Committee. This notice triggered a series of events that have been set in place for the Empowered Community to consider and approve the amendments before they can go into effect. The purpose of this email is to provide you with information on this Empowered Community process, and expected participation. Per the Bylaws a Community Forum must be convened prior to the end of ICANN59 in Johannesburg (by 29 June 2017) for the Decisional Participants and broader community to discuss the amendments. As directed in the 24 May 2017 letter<https://www.icann.org/en/system/files/correspondence/deerhake-to-jeffrey-24…> from the Empowered Community, the Community Forum has tentatively been scheduled for 27 June 2017 at 06:00 UTC and remote participation facilities will be available for those not present in Johannesburg. The Empowered Community Administration shall moderate the Community Forum, including discussion of statements or inputs received from any ICANN SO/AC or ICANN. After the Community Forum period ends at 06:59 UTC on 30 June 2017, and before the deadline for Decisional Participants’ decision at 06:59 UTC on 21 July 2017, the Empowered Community Administration may expect to receive notices of decisions from the Decisional Participants. By 06:59 UTC on 22 July 2017, the Empowered Community Administration must provide notice to the ICANN Secretary on the decisions of the Decisional Participants. At least three Decisional Participants must support and no more than one can object for the Fundamental Bylaws amendments to be approved. The ICANN organization has posted a webpage<https://www.icann.org/en/ec/proposed-fundamentals-bylaws-changes-move-gov-c…> with additional details on the status of this first Empowered Community process. It will also have a space for posting notices to and from the Empowered Community Administration. If there is any additional information that we can provide you about your participation in this important Empowered Community process, please do not hesitate to let us know. Best regards, David David A. Olive Senior Vice President Policy Development Support Managing Director ICANN Regional Office –Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6212<tel:+90.212.999.6212> Mobile: + 1. 202.341.3611<tel:+%201.%20202.341.3611> Mobile: +90.533.341.6550<tel:+90.533.341.6550>

3 2