[ECAdmin] Secretary's Notice to Empowered Community of Board Approval of FY20 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2020

Manal Ismail manal at tra.gov.eg
Mon May 20 11:12:35 UTC 2019


+1 to Katrina’s suggestions .. All very useful ..
Kind Regards
--Manal

From: Katrina Sataki <katrina at nic.lv>
Sent: Monday, May 20, 2019 1:09 PM
To: 'Stephen Deerhake @ ASNIC' <sdeerhake at nic.as>; 'Samantha Eisner' <Samantha.Eisner at icann.org>
Cc: 'Peg Rettino' <peg.rettino at icann.org>; ecadmin at icann.org; chair at nro.net; 'Maureen Hilyard' <maureen.hilyard at gmail.com>; 'Drazek, Keith' <kdrazek at verisign.com>; Manal Ismail <manal at tra.gov.eg>; 'Goran Marby' <goran.marby at icann.org>; 'Cherine Chalaby' <cherine.chalaby at board.icann.org>
Subject: RE: [ECAdmin] Secretary's Notice to Empowered Community of Board Approval of FY20 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2020

Dear All,

I absolutely agree with Sam and Stephen - it is enough to provide links to the documents.

However, there are few other things that I believe need fixing to make things easier for the community and staff:

1.            Subject lines of both documents are identical – RE: Notice of Board Approval of FY20 Operating Plan and Budget - even though the content is not. I do not know how these documents are made but, judging by the number of mistakes every time, I suspect that people just take one of the previous documents and try to change the relevant parts. By now it has become obvious that it does not work very well. I suggest that you create a template and highlight all the parts that need to be inserted.

2.            Speaking about subject line, can we stick to terminology used in the Bylaws? I.e. “Rejection Action Board Notice”, for example, “Rejection Action Board Notice of Approval of FY20 Operating Plan and Budget” (or something similar but with the right terminology)

3.            I also suggest that all the deadlines are already included in the document - there is absolutely no need for each DP to do the counting (and make mistakes) separately. It’s better to be on the same page. Speaking about deadlines, even though the Bylaws refer to a time zone unknown to me, may we use UTC? At least in parentheses.

4.            To make referencing easier, can we number rejection and approval action Board notices, e.g. RA2019/1 or AA2019/1? If there is a petition (or several petitions) from a DP, then the petition number should contain a reference to the DP and the relevant RA/AA, e.g. ccNSO/RA2019/1 (in case of several petitions, ccNSO/RA2019/1-1 and ccNSO/RA2019/1-2).

Kind regards,

]{atrina


From: Stephen Deerhake @ ASNIC [mailto:sdeerhake at nic.as]
Sent: Sunday, May 19, 2019 8:44 PM
To: Samantha Eisner <Samantha.Eisner at icann.org<mailto:Samantha.Eisner at icann.org>>
Cc: Peg Rettino <peg.rettino at icann.org<mailto:peg.rettino at icann.org>>; ecadmin at icann.org<mailto:ecadmin at icann.org>; chair at nro.net<mailto:chair at nro.net>; Maureen Hilyard <maureen.hilyard at gmail.com<mailto:maureen.hilyard at gmail.com>>; katrina at nic.lv<mailto:katrina at nic.lv>; Drazek, Keith <kdrazek at verisign.com<mailto:kdrazek at verisign.com>>; Manal Ismail <manal at tra.gov.eg<mailto:manal at tra.gov.eg>>; Goran Marby <goran.marby at icann.org<mailto:goran.marby at icann.org>>; Cherine Chalaby <cherine.chalaby at board.icann.org<mailto:cherine.chalaby at board.icann.org>>
Subject: Re: [ECAdmin] Secretary's Notice to Empowered Community of Board Approval of FY20 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2020

Greetings,

Please accept my apology for the tardy reply.  The 9th was a travel day for me and I didn’t see a big chunk of that day’s email.

Glad to see that people are paying attention.  I think we can live nicely with the historical format of including links to the underlying documents.

Best Regards,
Stephen Deerhake
ccNSO representative to the Empowered Community Administration

From: Samantha Eisner <Samantha.Eisner at icann.org<mailto:Samantha.Eisner at icann.org>>
Date: Thursday, May 9, 2019 at 00:16
To: "Stephen Deerhake @ ASNIC" <sdeerhake at nic.as<mailto:sdeerhake at nic.as>>
Cc: Peg Rettino <peg.rettino at icann.org<mailto:peg.rettino at icann.org>>, "ecadmin at icann.org<mailto:ecadmin at icann.org>" <ecadmin at icann.org<mailto:ecadmin at icann.org>>, "chair at nro.net<mailto:chair at nro.net>" <chair at nro.net<mailto:chair at nro.net>>, Maureen Hilyard <maureen.hilyard at gmail.com<mailto:maureen.hilyard at gmail.com>>, "katrina at nic.lv<mailto:katrina at nic.lv>" <katrina at nic.lv<mailto:katrina at nic.lv>>, "Drazek, Keith" <kdrazek at verisign.com<mailto:kdrazek at verisign.com>>, Manal Ismail <manal at tra.gov.eg<mailto:manal at tra.gov.eg>>, Goran Marby <goran.marby at icann.org<mailto:goran.marby at icann.org>>, Cherine Chalaby <cherine.chalaby at board.icann.org<mailto:cherine.chalaby at board.icann.org>>
Subject: Re: [ECAdmin] Secretary's Notice to Empowered Community of Board Approval of FY20 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2020

To confirm, the notice provided includes a link to where each of the documents is located. This is the same manner of notice and reference to the adopted documents as has been delivered for each notice period since the Empowered Community went into effect. If any member of the EC Administration or Decisional Participant requires a PDF of any of the documents, please let us know and we will have those forwarded from the Secretary’s office.

Best regards,

Sam Eisner
Deputy General Counsel, ICANN
Sent from my iPhone

On May 8, 2019, at 6:53 PM, Stephen Deerhake @ ASNIC <sdeerhake at nic.as<mailto:sdeerhake at nic.as>> wrote:
Greetings Peg,

On behalf of the Empowered Community Administration, I thank you for providing us with the ICANN Corporate Secretary’s formal notification of the recent ICANN Board action with respect to their adoption of the FY20 Operating Plan and Budget and their adoption of the Updates to the Five Year Operating Plan 2020, thus initiating a Rejection Action Petition Period per Annex D, Section2.2(a) of the ICANN Bylaws.

However, on behalf of the Empowered Community Administration, I also note that this formal notification from the ICANN Secretary is deficient with respect to ICANN’s obligations under Section 22.4(a)(v) of the ICANN Bylaws, which require that “…the Secretary shall provide a Board Notice to the EC Administration and the Decisional Participants , which Board Notice shall enclose a copy of the Operating Plan that is the subject of the Operating Plan Approval.” (https://www.icann.org/resources/pages/governance/bylaws-en/#article22 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_governance_bylaws-2Den_-23article22&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=w1jlqVWntmqtI5dedIDLQ6uBxH_Jh-uBee_4imohzko&m=frNwrvff2Tt1UdLa9uuTuszNa-YO_SglqyCwJJ2Kwqw&s=7VZTujR1OU37jnKLYZjgWBxFblDMF1stLXPSBapu_yk&e=>).

For the record, the Empowered Community Administration was NOT provided in the notification email to which I am responding with a “…copy of the Operating Plan that is the subject of the Operating Plan Approval”, as specified under Section 22.4(a)(v) of the ICANN Bylaws.

Also for the record, and again on behalf of the Empowered Community Administration, this will not be a hinderance to our acceptance of the formal notification with regards to the ICANN Board’s adoption of the FY20 Operating Plan and Budget, as well as their adoption of the Updates to the Five Year Operating Plan 2020.

However, going forward, the Empowered Community Administration expects that ICANN will fully comply with their obligations with respect to Empowered Community Administration notification as expressed in Section 22.4(a)(v) of the ICANN Bylaws.


Best Regards,
Stephen Deehake
ccNSO representative to the Empowered Community Administration



From: ECAdmin <ecadmin-bounces at icann.org<mailto:ecadmin-bounces at icann.org>> on behalf of Peg Rettino <peg.rettino at icann.org<mailto:peg.rettino at icann.org>>
Date: Wednesday, May 8, 2019 at 17:46
To: "ecadmin at icann.org<mailto:ecadmin at icann.org>" <ecadmin at icann.org<mailto:ecadmin at icann.org>>, "chair at nro.net<mailto:chair at nro.net>" <chair at nro.net<mailto:chair at nro.net>>, Maureen Hilyard <maureen.hilyard at gmail.com<mailto:maureen.hilyard at gmail.com>>, "katrina at nic.lv<mailto:katrina at nic.lv>" <katrina at nic.lv<mailto:katrina at nic.lv>>, "Drazek, Keith" <kdrazek at verisign.com<mailto:kdrazek at verisign.com>>, Manal Ismail <manal at tra.gov.eg<mailto:manal at tra.gov.eg>>
Cc: Goran Marby <goran.marby at icann.org<mailto:goran.marby at icann.org>>, Cherine Chalaby <cherine.chalaby at board.icann.org<mailto:cherine.chalaby at board.icann.org>>
Subject: [ECAdmin] Secretary's Notice to Empowered Community of Board Approval of FY20 Operating Plan and Budget and Secretary's Notice to Empowered Community of Board Approval of Updates to Five Year Operating Plan 2020

Greetings,

Attached please find the Secretary’s Notice of Board Approval of FY20 Operating Plan and Budget and Secretary’s Notice of Board Approval of Updates to Five Year Operating Plan 2020 sent on behalf of John Jeffrey.


Best,
Peg



--
Peg Rettino
Project Specialist & Executive Assistant to John Jeffrey
General Counsel and Secretary
ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094
peg.rettino at icann.org<mailto:peg.rettino at icann.org>
Skype: peg.rettino
Direct: 310-301-3868


_______________________________________________
ECAdmin mailing list
ECAdmin at icann.org<mailto:ECAdmin at icann.org>
https://mm.icann.org/mailman/listinfo/ecadmin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ecadmin/attachments/20190520/1204a4d5/attachment.html>


More information about the ECAdmin mailing list