[NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg | Supported Travelers Database Due | Thursday, 22 June 2023
Benjamin Akinmoyeje
benakin at gmail.com
Tue Jun 27 18:10:43 CEST 2023
Dear ECs,
Good day and I hope your week is going well.
I like to send a gentle reminder for the ICANN78 strategic engagement plan
by intending ICANN-funded travelers.
Please do well to submit your plan, it was due last Friday.
Kind regards,
Benjamin
On Fri, Jun 23, 2023 at 6:18 PM Benjamin Akinmoyeje <benakin at gmail.com>
wrote:
> Dear Mili,
> Thank you for your email.
>
> On Thu, Jun 22, 2023 at 7:19 PM Mili <milisemlani at gmail.com> wrote:
>
>> Hi all,
>> Firstly, it is unfair to suddenly emphasize on the plan when for the
>> first 2 meetings in the year this was not followed at all.
>>
> It is awesome that you have raised the "unfair" term again.I do not think
> it is fair to have EC who attend meetings without plans and strategies to
> enhance the outreach and active participation of NCUC at the meeting.
>
>
>> Nevertheless, it’s a good start to follow the rules . I do second Ken
>> that it is indeed a very short time to put a plan together which is well
>> thought out. @Benjamin as you will be a funded traveller too I believe you
>> also need to fulfill the requirement of submitting a similar plan
>>
>
> As the chair I do not have a choice if you have been observing and
> following the meetings you would have seen that it is my role to make sure
> the agenda is set, to attend various leadership meetings. In the past two
> meetings I have been funded by Article 19 and I had to have detailed plans
> and reports to be at those meetings, Since I have chosen to make this a
> personal attack on me as I decided to perform my duty as the EC chair. I
> will come out and address some of your shortcomings... First as an EC you
> were nowhere to be found during ICANN77 - despite the fact that there was a
> significant participation from the APAC region there was no EC member from
> the region to engage the attendees even virtually.Secondly, during the APAC
> space meeting you were also not seen. I remembered that you
>
>> and yours will be immensely helpful for us to use as a template and also
>> feel inspired. Afterall I would imagine as Chair, your should have the
>> wider vision and we can then breakdown the broader vision into actionable
>> steps in ours
>>
>> You campaigned and got voted for the position, I did not recruit you for
> the position, if you are unsure of what to do , there are other attendees
> from the region who have been interested in supporting the community and
> participating in our face to face meetings. So I will encourage you to
> review the NCUC mandate and your candidate statement during the election to
> fulfill your commitment to the constituency.
>
> Secondly, I do not agree that a plan can be a basis for selecting who gets
>> the travel slots in the future. The plan sure can be a requirement for
>> selected funded travellers to submit but not a basis for selection. I
>> emphasized on laying down policies and criteria’s for selection early this
>> year which was completely disregarded and same for the rotating roster Olga
>> made. In the next monthly meeting we should put it in place for next year
>> already.
>>
>> You are free to disagree, but travel slots are not automatic, it is based
> on the plans each ECs have, if ECs will not show up and participate
> actively - we will give the slots to community members who are engaging. At
> ICANN77 - community members asked repeatedly to see ECs, Only Ken showed up
> as NCUC members at various meetings outside the 2 NCUC meetings, How do we
> keep our influence if our elected leaders are not up and about interacting
> at the various meetings to hold up our flags both virtual and face to face.
> I agree that we should pull up the roster that Olga did and abide by it (In
> Fact that is what we should do). The only reason I had made the
> recommendation I made was trying to accomodate you since you could not
> make DC an otherwise rightful person for ICNN78 EC Slot is Olga because she
> has not attended the last two meetings. I also hold myself accountable to
> have skewed the travel slot rotation by always taking external travel
> funding. I think it will be a good idea to stop it or refuse ECs from
> getting my slot once I get an external funding so we can maintain the
> roster.
>
> And lastly, for the LAC EC selection of we were to try to fill in that
>> seat, we must come up with stronger process of selection than just someone
>> willing to become on. Even it that means having a simple poll on the
>> mailing list or a candidate call or so. But that is something we can tackle
>> after icann Hamburg.
>>
>
> Finally, I know how many meetings or engagement that have been disregarded
> because you (Mili) said you are not available. Should we check the EC
> meeting attendance to review each person's attendance rate? All of these
> issues you are bringing up, were on the agenda of the cancelled meeting
> proceeding ICANN77. Can we review why that meeting did not hold and what
> happened to items on the agenda.We need not wait for ICANN78 to
> straighten up everything since we are all engaging on this list now.
>
> If this is the way we want to keep going back and forth with each other,
> fair enough This is distracting and exhausting.
>
> Kindly submit your membership engagement strategy and plan for ICANN78 as
> requested, even if it is a draft/ .
>
> Regards,
> Benjamin
>
>>
>>
>
>> --
>> With gratitude
>> Mili Semlani
>> Journalist & Engagement Manager
>> Founder @ Youth4IG <http://youth4ig.asia/>
>> Instagram <https://www.instagram.com/theuntraveller/> | LinkedIn
>> <https://www.linkedin.com/in/milisemlani/>
>>
>> On Jun 22, 2023, at 10:17, Andrea Glandon <andrea.glandon at icann.org>
>> wrote:
>>
>>
>>
>> Hello all,
>>
>>
>>
>> Thank you, Benjamin. I will submit the names as you requested.
>>
>>
>>
>> As a reminder, before Olga can apply for the CROP slot for ICANN78, the
>> NCUC FY24 Outreach Strategic Plan needs to be completed and approved:
>> https://docs.google.com/document/d/1OVDefXv9YmPlW6j7R7yiDzu3h4rf-sLqdMp2qrXUxJs/edit.
>>
>>
>>
>>
>> After this is done, Olga can apply for the CROP trip here:
>> https://docs.google.com/document/d/184J_VEElfZIXeuphTaGifIsQc35Zur0e1g3EbnmaIZg/edit.
>>
>>
>>
>>
>> Please make sure you also read the travel guidance for FY24 here:
>> https://docs.google.com/document/d/1RjgCLefvk-lb7MU1M2p8aAUNY3oTrzxGd0rZrQw64ck/edit.
>>
>>
>>
>>
>> Thank you!
>>
>> Kind Regards,
>>
>> Andrea
>>
>>
>>
>>
>>
>>
>>
>> *From: *NCUC-EC <ncuc-ec-bounces at lists.ncuc.org> on behalf of Benjamin
>> Akinmoyeje <benakin at gmail.com>
>> *Date: *Thursday, June 22, 2023 at 09:42
>> *To: *Ken Herman <ken at kherman.com>
>> *Cc: *"Exec. Comm" <ncuc-ec at lists.ncuc.org>
>> *Subject: *Re: [NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg |
>> Supported Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> Dear Andrea and Ken,
>>
>> Thank you for the responses, these offer some relief. I believe the
>> ability to act proactively rests on every one of us. As we might have
>> noticed our active participation only increases during travel slots
>> conversation.
>>
>>
>>
>> We ought to have met multiple times before today, I recommended and
>> called for a meeting without anyone agreeing to meet.
>>
>>
>>
>> We will go ahead with the names as indicated however all intended
>> supported funded travelers (both CROP and ICANN funded) would have to
>> develop their plan to support active participation and reporting to the
>> community during and after ICANN78.
>>
>> Ken, you can also share the schedule based on the state of various ECs'
>> travels and the future understanding that LAC EC will join the group soon.
>>
>>
>>
>> I will appreciate it if we can share our draft plans before COB, on June
>> 23, 2023.
>>
>>
>>
>> This is the duty we owe the community.
>>
>>
>>
>> Dear Andrea - I believe we can proceed with Benjamin, Mili, and Ken,
>> while we put Olga's name for CROP.
>>
>>
>>
>> Kind regards,
>>
>> Benjamin
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Jun 22, 2023 at 3:04 PM Ken Herman <ken at kherman.com> wrote:
>>
>> Dear Benjamin.
>>
>>
>>
>> Good idea to call for a plan from the EC members attending meetings. I
>> notice this is the first meeting that this requirement is being acted upon;
>> better late than never, I suppose.
>>
>>
>>
>> I will be happy to provide one, but the decision on participation needs
>> to be made shortly and I, for one, won’t have any time to prepare one
>> between now and tomorrow’s deadline to provide Org with names. What would
>> help is a template to use, and if you can share your own plan it would help
>> in many ways, both as a template as well as to align whatever we can do to
>> support your efforts.
>>
>>
>>
>> Nevertheless, I feel confident, as I hope you do as well, that all the EC
>> members attending ICANN78 will follow-through on our obligations for
>> following issues and working to enhance engagement. Since it seems that the
>> CROP issue for Olga has been resolved, there should be no issues with
>> submitting names for ICANN travelers (Mili and I) and CROP for Olga.
>>
>>
>>
>> Finally, I agree with Olga that we can do more to be proactive, including
>> creating a schedule for participation in future ICANN meetings that cover
>> engagement and policy commitments. Olga prepared a travel proposal in the
>> past and we can easily do one going forward that can be used as a
>> reference, even if there is a possibility of names changing. Preparing a
>> schedule for the next year also allows EC members to plan their own
>> schedules accordingly.
>>
>>
>>
>> Ken
>>
>>
>>
>> *From:* NCUC-EC <ncuc-ec-bounces at lists.ncuc.org> *On Behalf Of *Benjamin
>> Akinmoyeje
>> *Sent:* Wednesday, June 21, 2023 5:57 PM
>> *To:* Andrea Glandon <andrea.glandon at icann.org>
>> *Cc:* Exec. Comm <ncuc-ec at lists.ncuc.org>
>> *Subject:* Re: [NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg |
>> Supported Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> Dear ECs,
>>
>> I will encourage every EC to submit a concise proposal for ICANN78, the
>> plan to improve NCUC outreach & engagement, and the policy topics you hope
>> to follow.
>>
>>
>>
>> This has become pertinent based on the way our travel slots have been
>> executed and the limited participation we have seen in ICANN77 NCUC
>> membership meeting.
>>
>>
>>
>> Please the CROP GSE will require our strategy of constituency engagement.
>>
>>
>>
>> I will encourage ECs to articulate their role at ICANN78 and we also use
>> it to determine those who will represent the NCUC.
>>
>>
>>
>> Kind regards,
>>
>> Benjamin
>>
>>
>>
>> On Wed, Jun 21, 2023 at 10:55 PM Andrea Glandon <andrea.glandon at icann.org>
>> wrote:
>>
>> That is correct.
>>
>>
>>
>> Kind Regards,
>>
>> Andrea
>>
>>
>>
>>
>>
>> *From: *Mili <milisemlani at gmail.com>
>> *Date: *Wednesday, June 21, 2023 at 15:39
>> *To: *Andrea Glandon <andrea.glandon at icann.org>
>> *Cc: *Ken Herman <ken at kherman.com>, Olga Kyryliuk <olga_kyryliuk at ukr.net>,
>> "Exec. Comm" <ncuc-ec at lists.ncuc.org>
>> *Subject: *Re: [NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg |
>> Supported Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> So can we confirm that if we submit the EC names, can we change the EC
>> names too after we learn more on CROP and before Sept 6?
>>
>> --
>>
>> With gratitude
>>
>> Mili Semlani
>>
>> Journalist & Engagement Manager
>>
>> Founder @ Youth4IG [youth4ig.asia]
>> <https://urldefense.com/v3/__http:/youth4ig.asia/__;!!PtGJab4!-hXEiuZfii5LvZnDKSJo5v-zGQ90VXYr8hsUP_djqytv0sy2WVD1TGWLYrSN5KJP_8RrdebBA5761JOREUXSth6Ve5JEVA$>
>>
>> Instagram [instagram.com]
>> <https://urldefense.com/v3/__https:/www.instagram.com/theuntraveller/__;!!PtGJab4!-hXEiuZfii5LvZnDKSJo5v-zGQ90VXYr8hsUP_djqytv0sy2WVD1TGWLYrSN5KJP_8RrdebBA5761JOREUXSth45ml3ouw$>
>> | LinkedIn [linkedin.com]
>> <https://urldefense.com/v3/__https:/www.linkedin.com/in/milisemlani/__;!!PtGJab4!-hXEiuZfii5LvZnDKSJo5v-zGQ90VXYr8hsUP_djqytv0sy2WVD1TGWLYrSN5KJP_8RrdebBA5761JOREUXSth6n0tTlLA$>
>>
>>
>> On Jun 21, 2023, at 15:29, Andrea Glandon <andrea.glandon at icann.org>
>> wrote:
>>
>> I am checking with some other colleagues. Also, as I said, additions and
>> replacements on those slots can be submitted until 6 September. So things
>> can be updated as I get more information.
>>
>>
>>
>> On Jun 21, 2023, at 3:21 PM, Mili <milisemlani at gmail.com> wrote:
>>
>> Thanks noted on 1 and 2.
>>
>>
>>
>> Is there any other faster way or anyone else we can ask in the ICANN org
>> team to clarify the CROP regional limitations.
>>
>> --
>>
>> With gratitude
>>
>> Mili Semlani
>>
>> Journalist & Engagement Manager
>>
>> Founder @ Youth4IG [youth4ig.asia]
>> <https://urldefense.com/v3/__http:/youth4ig.asia/__;!!PtGJab4!7XS_M8CAHO6wVE5IZdSM5rG82R7-ULImxemkXexS9s_Ogy6bT7sfJmG8u6BRfKbY4OJUN44rENS5kMZkZZVw76mB2yQF9g$>
>>
>> Instagram [instagram.com]
>> <https://urldefense.com/v3/__https:/www.instagram.com/theuntraveller/__;!!PtGJab4!7XS_M8CAHO6wVE5IZdSM5rG82R7-ULImxemkXexS9s_Ogy6bT7sfJmG8u6BRfKbY4OJUN44rENS5kMZkZZVw76kIMuh8CA$>
>> | LinkedIn [linkedin.com]
>> <https://urldefense.com/v3/__https:/www.linkedin.com/in/milisemlani/__;!!PtGJab4!7XS_M8CAHO6wVE5IZdSM5rG82R7-ULImxemkXexS9s_Ogy6bT7sfJmG8u6BRfKbY4OJUN44rENS5kMZkZZVw76kPwwkzqw$>
>>
>>
>> On Jun 21, 2023, at 15:10, Andrea Glandon <andrea.glandon at icann.org>
>> wrote:
>>
>> Hi Mili,
>>
>>
>>
>> 1. As stated in the CROP Procedures and Guidelines, up to 2 CROP
>> slots can be used for an ICANN Public Meeting. *It is very important
>> that everyone read the FY24 CROP Procedures and Guidelines: **https://docs.google.com/document/d/1yRob30L_xP9ZU8AiXp-LETHfBCbnTZbiPUJCFvEsrwg/edit
>> [docs.google.com]*
>> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1yRob30L_xP9ZU8AiXp-LETHfBCbnTZbiPUJCFvEsrwg/edit__;!!PtGJab4!_D03sQFmbwcWIWVyqHzHDgFUQrymiO7PiixHhXT4057I11dnwgy-rdzFB9PU6MqWm7z3XLAByGlJgpAzy_y6IBAgHLpmcDa8CHM$>
>> 2. The ICANN78 slots are due to the GNSO Secretariat by Friday, 23
>> June at the latest.
>> 3. I am going completely based off of the GSE list that clearly has
>> Europe separate from Eastern Europe and Central Asia. As I said, I am going
>> to confirm this with my colleague when he returns, but I wanted all of the
>> possibilities to be known. My colleague will not be back until after the
>> ICANN78 slots are due on Friday, 23 June.
>>
>>
>>
>> Thank you.
>>
>> Kind Regards,
>>
>> Andrea
>>
>>
>>
>>
>>
>> *From: *Mili <milisemlani at gmail.com>
>> *Date: *Wednesday, June 21, 2023 at 15:04
>> *To: *Andrea Glandon <andrea.glandon at icann.org>
>> *Cc: *Ken Herman <ken at kherman.com>, Olga Kyryliuk <olga_kyryliuk at ukr.net>,
>> "Exec. Comm" <ncuc-ec at lists.ncuc.org>
>> *Subject: *Re: [NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg |
>> Supported Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> Hi Andrea
>>
>> Some more clarifications needed:
>>
>>
>>
>> 1. Why are there 2 crop slots for EU? Usually I remember only 1 slot.
>> Only asking if something has changed about the crop programme or is this
>> something specific to EU.
>>
>>
>>
>> 2. Can we get a days extension to submit the EC names as clearly we need
>> more information to make this decision and that’s completely time zone
>> related and not in our control.
>>
>>
>>
>> 3. The EU region does include Eastern Europe too as far as the GSE team
>> and its reach go and also the official ICANN regions. I am aware that there
>> are sub divisions in the main 5 regions made sometimes for ease of covering
>> them (APAC for eg is divided into north asia, South Asia, pacific etx.) but
>> I for CROP it applies to the whole region.
>>
>> Cuz if east Europe is not under EU for CROP then which regional CROP
>> funding would members in Eastern Europe be eligible for?
>>
>>
>>
>> --
>>
>> With gratitude
>>
>> Mili Semlani
>>
>> Journalist & Engagement Manager
>>
>> Founder @ Youth4IG [youth4ig.asia]
>> <https://urldefense.com/v3/__http:/youth4ig.asia/__;!!PtGJab4!-k2Pv_yT8wn6rAbue_fKccZQ_tO_XBZ_lkpn2T88sYARR9Bw2kiXfI70qYr1hEuNyXNkJ4ufZ0ycY4xn9P2UP4ZIVz01Uw$>
>>
>> Instagram [instagram.com]
>> <https://urldefense.com/v3/__https:/www.instagram.com/theuntraveller/__;!!PtGJab4!-k2Pv_yT8wn6rAbue_fKccZQ_tO_XBZ_lkpn2T88sYARR9Bw2kiXfI70qYr1hEuNyXNkJ4ufZ0ycY4xn9P2UP4ZkCxu0-A$>
>> | LinkedIn [linkedin.com]
>> <https://urldefense.com/v3/__https:/www.linkedin.com/in/milisemlani/__;!!PtGJab4!-k2Pv_yT8wn6rAbue_fKccZQ_tO_XBZ_lkpn2T88sYARR9Bw2kiXfI70qYr1hEuNyXNkJ4ufZ0ycY4xn9P2UP4beDwAXQA$>
>>
>>
>> On Jun 21, 2023, at 14:52, Andrea Glandon <andrea.glandon at icann.org>
>> wrote:
>>
>> Apologies, Ken, I didn’t realize that you were self-funded. I see now
>> that Claudio was the other EC that was supposed to be there. Okay, then
>> yes, the EC needs to decide who will be the other slot after Olga. I am
>> hoping to get clarification and see if Olga can travel using the CROP slot,
>> but that confirmation will not come until after the deadline for the 3 EC
>> slots.
>>
>>
>>
>> Thanks!
>>
>> Kind Regards,
>>
>> Andrea
>>
>>
>>
>>
>>
>> *From: *Ken Herman <ken at kherman.com>
>> *Date: *Wednesday, June 21, 2023 at 14:46
>> *To: *Andrea Glandon <andrea.glandon at icann.org>, 'Mili Semlani' <
>> milisemlani at gmail.com>, 'Olga Kyryliuk' <olga_kyryliuk at ukr.net>
>> *Cc: *"'Exec. Comm'" <ncuc-ec at lists.ncuc.org>
>> *Subject: *RE: [NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg |
>> Supported Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> Andrea, just to clarify, my attendance at ICANN77 was self-funded.
>> According to the NCUC bylaws, *ICANN funded* participants are ineligible
>> for ICANN travel funding to consecutive meetings. If there are other ICANN
>> rules that govern travel to consecutive meetings, then please let me know,
>> otherwise I believe that self-funded travelers should not be disqualified
>> for demonstrating commitment by paying their own way from time to time.
>>
>>
>>
>> Grateful if you can confirm that I remain eligible for ICANN funded
>> travel to ICANN78.
>>
>>
>>
>> Thank you.
>>
>>
>>
>> Ken
>>
>>
>>
>> *From:* NCUC-EC <ncuc-ec-bounces at lists.ncuc.org> *On Behalf Of *Andrea
>> Glandon
>> *Sent:* Wednesday, June 21, 2023 3:35 PM
>> *To:* Mili Semlani <milisemlani at gmail.com>; Olga Kyryliuk <
>> olga_kyryliuk at ukr.net>
>> *Cc:* Exec. Comm <ncuc-ec at lists.ncuc.org>
>> *Subject:* Re: [NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg |
>> Supported Travelers Database Due | Thursday, 22 June 2023
>> *Importance:* High
>>
>>
>>
>> Hello again,
>>
>>
>>
>> I have been doing some checking on my end to see if Olga qualifies for
>> the CROP slot for ICANN78. Technically, the applicant needs to be from the
>> European region as listed in the GSE list of regions here: https://drive.google.com/file/d/14seX2l_Gq5rE97gbr38i1EuUbKRZ5GHl/view
>> [drive.google.com]
>> <https://urldefense.com/v3/__https:/drive.google.com/file/d/14seX2l_Gq5rE97gbr38i1EuUbKRZ5GHl/view__;!!PtGJab4!9spitMrCo-0ClzzMdsD5LAad6Qw5REMK2pvNFhdbgmoxvXHPocH3uDWTU1jx_Sc6od-WgheDFKnOzZgnfrSmFA$>.
>> I ran this by my manager and 23 feel that she may not qualify because on
>> this list since she is in the Eastern Europe/Central Asia region. My
>> colleague who is in charge of this program is on vacation right now, but I
>> will confirm this with him when he returns. I know that sometimes Olga is
>> in Poland, so my first question is @Olga Kyryliuk <olga_kyryliuk at ukr.net>
>> where will you be traveling from to ICANN78 and back to after ICANN78? We
>> do have some time to update the travel slots that are being sent in
>> tomorrow and to apply for CROP. At this point, if it were me, I would give
>> the travel slots to those who are eligible to travel to ICANN78 (I think it
>> would be Mili & Olga since neither went to Washington D.C.) I can continue
>> to get information about CROP and if Olga is eligible, we can change the
>> names around to get another EC member to Germany. Another thing to keep in
>> mind, 2 CROP slots can be used for ICANN78 so a another member who resides
>> in Europe could go as well.
>>
>>
>>
>> Thanks!
>>
>> Kind Regards,
>>
>> Andrea
>>
>>
>>
>>
>>
>> *From: *Mili Semlani <milisemlani at gmail.com>
>> *Date: *Wednesday, June 21, 2023 at 14:09
>> *To: *Andrea Glandon <andrea.glandon at icann.org>
>> *Cc: *"Exec. Comm" <ncuc-ec at lists.ncuc.org>
>> *Subject: *Re: [NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg |
>> Supported Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> So we have to submit the EC funded travellers by Jun 22 which gives us
>> only 1 day, so we need to convene soon.
>>
>>
>>
>> --
>>
>> With gratitude
>>
>> *Mili Semlani*
>>
>> Community specialist
>>
>> Instagram [instagram.com]
>> <https://urldefense.com/v3/__https:/www.instagram.com/theuntraveller/__;!!PtGJab4!5NqIo17db_srKH1eGxmzNdcgHSx2X7EU7JymSgJTNr9vW-jL6i3XKYMVHT3YjOibpBAjRKjzy5HmM29ayMHiH62iDzW0Hw$>
>> | LinkedIn [linkedin.com]
>> <https://urldefense.com/v3/__https:/www.linkedin.com/in/milisemlani/__;!!PtGJab4!5NqIo17db_srKH1eGxmzNdcgHSx2X7EU7JymSgJTNr9vW-jL6i3XKYMVHT3YjOibpBAjRKjzy5HmM29ayMHiH6196vUmGw$>
>>
>>
>>
>>
>>
>>
>>
>> On Wed, 21 Jun 2023 at 13:57, Andrea Glandon <andrea.glandon at icann.org>
>> wrote:
>>
>> Let me make a small update as I placed a sentence in the incorrect
>> location:
>>
>>
>>
>> The date of Wednesday, 06 September is additions or replacements for the
>> ICANN78 travel slots through ICANN travel NOT CROP.
>>
>>
>>
>> ICANN78 travel slots due to GNSO Secs by Thursday, 22 June (this can go
>> to Friday if necessary)
>>
>> Additions or replacements for ICANN78 travel slots due to GNSO Secs by
>> Wednesday, 06 September.
>>
>> CROP Travel application for ICANN78 due by Friday, 01 September. An
>> Outreach Strategic plan must be completed and approved first.
>>
>>
>>
>> Thank you.
>>
>> Kind Regards,
>>
>> Andrea
>>
>>
>>
>>
>>
>> *From: *NCUC-EC <ncuc-ec-bounces at lists.ncuc.org> on behalf of Andrea
>> Glandon <andrea.glandon at icann.org>
>> *Date: *Wednesday, June 21, 2023 at 13:53
>> *To: *Mili Semlani <milisemlani at gmail.com>, Benjamin Akinmoyeje <
>> benakin at gmail.com>
>> *Cc: *"Exec. Comm" <ncuc-ec at lists.ncuc.org>
>> *Subject: *Re: [NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg |
>> Supported Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> Hello all,
>>
>>
>>
>> The deadline to submit the names for the ICANN78 funded travelers is
>> Thursday, 22 June 2023, Friday at the very latest. The deadline for the
>> CROP slot for ICANN78 is Friday, 01 September 2023. If additions or
>> replacements are needed, the last day to submit those are Wednesday, 06
>> September. *It is very important that everyone read the FY24 CROP
>> Procedures and Guidelines: **https://docs.google.com/document/d/1yRob30L_xP9ZU8AiXp-LETHfBCbnTZbiPUJCFvEsrwg/edit
>> [docs.google.com]*
>> <https://urldefense.com/v3/__https:/docs.google.com/document/d/1yRob30L_xP9ZU8AiXp-LETHfBCbnTZbiPUJCFvEsrwg/edit__;!!PtGJab4!_D03sQFmbwcWIWVyqHzHDgFUQrymiO7PiixHhXT4057I11dnwgy-rdzFB9PU6MqWm7z3XLAByGlJgpAzy_y6IBAgHLpmcDa8CHM$>
>> *.* In addition, more than one CROP slot can be used for ICANN78, but
>> the applicants need to be in Europe. Before any CROP trip applications can
>> be submitted, the NCUC Outreach Strategic plan needs to be completed and
>> approved.
>>
>>
>>
>> Thank you.
>>
>> Kind Regards,
>>
>> Andrea
>>
>>
>>
>>
>>
>> *From: *Mili Semlani <milisemlani at gmail.com>
>> *Date: *Wednesday, June 21, 2023 at 13:30
>> *To: *Benjamin Akinmoyeje <benakin at gmail.com>, Andrea Glandon <
>> andrea.glandon at icann.org>
>> *Cc: *Olga Kyryliuk <olga_kyryliuk at ukr.net>, "Exec. Comm" <
>> ncuc-ec at lists.ncuc.org>
>> *Subject: *[Ext] Re: [NCUC-EC] Fwd: REMINDER ICANN78 | Hamburg |
>> Supported Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> Hi
>>
>> Benji's suggestion to use CROP makes sense but Olgas question are valid
>> too.
>>
>>
>>
>> @Andrea Glandon <andrea.glandon at icann.org> cqn we then confirm these
>> things:
>>
>> 1. What is the deadline to submit the names for the EC funded travellers?
>>
>> 2. What is the deadline to submit the CROP funded name?
>>
>>
>>
>> Atleast then we know how much time we have to make these decisions and
>> maybe we can use whatsapp group or zoom call to work it out sooner
>> than later.
>>
>> --
>>
>> With gratitude
>>
>> *Mili Semlani*
>>
>> Community specialist
>>
>> Instagram [instagram.com]
>> <https://urldefense.com/v3/__https:/www.instagram.com/theuntraveller/__;!!PtGJab4!8INMZy5hr_i6Yi27V68uSCgysMrSh0T8Zy_7GinBsKyLiEmi5SwjU0X0WjLMLLJL9ahJLvw-PbFO82ncW8ar5iIX0npcnQ$>
>> | LinkedIn [linkedin.com]
>> <https://urldefense.com/v3/__https:/www.linkedin.com/in/milisemlani/__;!!PtGJab4!8INMZy5hr_i6Yi27V68uSCgysMrSh0T8Zy_7GinBsKyLiEmi5SwjU0X0WjLMLLJL9ahJLvw-PbFO82ncW8ar5iKJ5lV-hA$>
>>
>>
>>
>>
>>
>>
>>
>> On Wed, 21 Jun 2023 at 09:01, Benjamin Akinmoyeje <benakin at gmail.com>
>> wrote:
>>
>> Dear Olga,
>>
>> Thank you for your response and I appreciate your question.
>>
>>
>>
>> As I said the only reason behind the suggestion was because of proximity
>> perspective.
>>
>>
>>
>> I agree that this trip is supposed to be officially yours. I believe we
>> need to revert to the roster to reset the rosters for the official NCUC EC
>> slots - so we do not have back and forth at every meeting.
>>
>>
>>
>> There is a need to also get people to the meeting to work on policies.-
>> our community is demanding more individuals in the meeting supporting our
>> PDPs.
>>
>>
>>
>> We can have a quick Zoom call to agree on who to enlist for ICANN78
>> officially and tasks involved as required by the bylaws.
>>
>>
>>
>>
>>
>> Kind regards,
>>
>> Benjamin
>>
>>
>>
>> On Wed, Jun 21, 2023 at 1:42 PM Olga Kyryliuk <olga_kyryliuk at ukr.net>
>> wrote:
>>
>> Hi Ben and All!
>>
>>
>>
>> First of all, before we make a decision let’s clarify a couple of issues.
>>
>>
>>
>> What is the deadline to apply for CROP? Is application round still open
>> for Hamburg meeting?
>>
>>
>>
>> If we decide to move ahead with me getting CROP funding, and not the EC
>> funding slot, can you confirm that CROP slot will be mine or you will still
>> make open call and say afterwards that you’d prefer a community member to
>> use it? Because if this is a case I don’t think it’s fair, I haven’t been
>> using travel slot for the last two meetings, with all rotation logic now is
>> my turn. However, if we agree that I use CROP then I’m happy that we can
>> secure two other EC members to attend.
>>
>>
>>
>> Best,
>>
>> Olga
>>
>>
>>
>> *21 червня 2023 р. о 00:33:48,від "Benjamin Akinmoyeje" <*
>> *benakin at gmail.com* <benakin at gmail.com>*>: *
>>
>>
>>
>> The reason I recommended Olga for the CROP funding is that she may be
>> close to Hamburg and we may be able to easily supplement her travels but if
>> that is not the case.
>>
>>
>>
>> All ECs planning to attend Hamburg may have to share their proposed
>> activities at the meeting and we used that to select those who qualify for
>> ICANN funding and the person suitable for CROP funding.
>>
>>
>>
>> This is also a good time to review the travel schedule so that we don't
>> have to consistently be undecided about who is entitled to the travel slots.
>>
>>
>>
>> We have very limited time to decide on the official travel slots.
>>
>>
>>
>> Kind regards,
>>
>> Benjamin
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Jun 20, 2023 at 9:43 PM Ken Herman <ken at kherman.com> wrote:
>>
>> Benjamin, I have no objection to your proposal.
>>
>>
>>
>> However, my understanding is that CROP is only very limited funding and
>> not for the full time of the Annual Meeting. Perhaps there is some way that
>> we can identify additional funding so that Olga can participate fully.
>>
>>
>>
>> Also, I suggest that we all work together to organize any additional
>> events at the meeting. Along those lines, first we should clarify room
>> selection, since that appeared to be an issue that was raised at the
>> NCUC/NPOC meeting last week.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Ken
>>
>>
>>
>> *From:* NCUC-EC <ncuc-ec-bounces at lists.ncuc.org> *On Behalf Of *Benjamin
>> Akinmoyeje
>> *Sent:* Tuesday, June 20, 2023 2:46 PM
>> *To:* Mili <milisemlani at gmail.com>
>> *Cc:* Exec. Comm <ncuc-ec at lists.ncuc.org>
>> *Subject:* Re: [NCUC-EC] Fwd: REMINDER ICANN78 | Hamburg | Supported
>> Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> Dear EC,
>>
>> In order to move this conversation forward, we need to enlist those who
>> qualify to travel to the next meeting.
>>
>> We have three slots available for the EC including the chairs.
>>
>> And we have 4 ECs interested.
>>
>> Here is my recommendation - we have one of the ECs use the CROP funding
>> and have the other three ECs use the official slots.
>>
>>
>>
>> Olga since you are in Europe - we have you take the CROP fy24 and work
>> with Adam Peake to organize a side event for NCUC at ICANN 78.
>>
>>
>>
>> Mili and Ken can take the official NCUC EC slots.
>>
>>
>>
>> I like to know what you think of this suggestion.
>>
>>
>>
>>
>>
>> Kind regards,
>>
>> Benjamin
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Jun 15, 2023 at 6:50 PM Mili <milisemlani at gmail.com> wrote:
>>
>> I am interested and will be available to attend ICANN Hamburg.
>>
>> --
>>
>> With gratitude
>>
>> Mili Semlani
>>
>> Journalist & Engagement Manager
>>
>> Founder @ Youth4IG [youth4ig.asia]
>> <https://urldefense.com/v3/__http:/youth4ig.asia/__;!!PtGJab4!8INMZy5hr_i6Yi27V68uSCgysMrSh0T8Zy_7GinBsKyLiEmi5SwjU0X0WjLMLLJL9ahJLvw-PbFO82ncW8ar5iIJhOMjcw$>
>>
>> Instagram [instagram.com]
>> <https://urldefense.com/v3/__https:/www.instagram.com/theuntraveller/__;!!PtGJab4!8INMZy5hr_i6Yi27V68uSCgysMrSh0T8Zy_7GinBsKyLiEmi5SwjU0X0WjLMLLJL9ahJLvw-PbFO82ncW8ar5iIX0npcnQ$>
>> | LinkedIn [linkedin.com]
>> <https://urldefense.com/v3/__https:/www.linkedin.com/in/milisemlani/__;!!PtGJab4!8INMZy5hr_i6Yi27V68uSCgysMrSh0T8Zy_7GinBsKyLiEmi5SwjU0X0WjLMLLJL9ahJLvw-PbFO82ncW8ar5iKJ5lV-hA$>
>>
>>
>> On Jun 15, 2023, at 11:01, Olga Kyryliuk <olga_kyryliuk at ukr.net> wrote:
>>
>> Hi Team,
>>
>>
>>
>> I believe it is also my turn for travel slot as I couldn’t attend
>> previous two meetings. Given it is my region and my last meeting as EC rep
>> I would definitely be interested to go.
>>
>>
>>
>> I hope the Washington meeting was productive and brought the desired
>> results. Looking forward to your updates.
>>
>>
>>
>> Best,
>>
>> Olga
>>
>>
>>
>> *15 червня 2023 р. о 17:51:00,від "Ken Herman" <**ken at kherman.com*
>> <ken at kherman.com>*>: *
>>
>>
>>
>> Thanks Benjamin.
>>
>>
>>
>> I am certainly available and interested to attend ICANN78.
>>
>>
>>
>> Ken
>>
>>
>>
>> *From:* NCUC-EC <ncuc-ec-bounces at lists.ncuc.org> *On Behalf Of *Benjamin
>> Akinmoyeje
>> *Sent:* Thursday, June 15, 2023 11:43 AM
>> *To:* Exec. Comm <ncuc-ec at lists.ncuc.org>
>> *Subject:* [NCUC-EC] Fwd: REMINDER ICANN78 | Hamburg | Supported
>> Travelers Database Due | Thursday, 22 June 2023
>>
>>
>>
>> Dear EC,
>>
>> Good day and I hope you are doing well.
>>
>> This is the time to enlist ECs going to ICANN78.
>>
>>
>>
>> Please indicate your preference to go to ICANN78.
>>
>> Kindly respond,
>>
>> Benjamin
>>
>> ---------- Forwarded message ---------
>> From: *Terri Agnew* <terri.agnew at icann.org>
>> Date: Thu, Jun 15, 2023 at 12:13 PM
>> Subject: REMINDER ICANN78 | Hamburg | Supported Travelers Database Due |
>> Thursday, 22 June 2023
>> To: julf at julf.com <julf at julf.com>, plommer at gmail.com <plommer at gmail.com>,
>> benakin at gmail.com <benakin at gmail.com>, chair at rysg.info <chair at rysg.info>,
>> aheineman at godaddy.com <aheineman at godaddy.com>, mcole at perkinscoie.com <
>> mcole at perkinscoie.com>, lschulman at inta.org <lschulman at inta.org>,
>> philippe.fouquart at orange.com <philippe.fouquart at orange.com>,
>> sdemetriou at verisign.com <sdemetriou at verisign.com>, alan at donuts.email <
>> alan at donuts.email>
>> Cc: Brenda Brewer <brenda.brewer at icann.org>, gnso-secs at icann.org <
>> gnso-secs at icann.org>, Zoe Bonython <secretariat at icannregistrars.org>,
>> Andrea Glandon <andrea.glandon at icann.org>, Sue Schuler <
>> secretariat at rysg.info>
>>
>>
>>
>> *REMINDER: *Please submit your meeting database to gnso-secs at icann.org by
>> *Thursday, 22 June 2023*
>>
>>
>>
>> Dear all,
>>
>>
>>
>> In order to service your travel needs for ICANN78 Hamburg in a timely
>> fashion, please submit your meeting database to gnso-secs at icann.org by *Thursday,
>> 22 June 2023*
>>
>>
>>
>> 1. As a reminder, for the AGM meeting only, incoming Councilors get
>> funding, as well as the then-incumbent Councilors.
>>
>>
>>
>> A timely response would be appreciated in view of visa issues and the
>> OFAC review. The deadline for submissions is critical to allow for
>> confirmed reservation numbers as required for visa and travel arrangements.
>>
>> *TRAVEL BOOKING PROCESS*
>>
>>
>>
>> In order for Funded Travelers to start booking travel, they MUST complete
>> Steps 1, 2, and 3.
>>
>>
>>
>> *WHO*
>>
>> *WHAT*
>>
>> 1
>>
>> Funded Traveler
>>
>> Register for meeting using the Funded Traveler Registration Link provided
>> by ICANN Travel Support
>>
>> 2
>>
>> Funded Traveler
>>
>> Approved for Trade Regulations Review
>>
>> 3
>>
>> Funded Traveler
>>
>> Receive Travel Funding Confirmation Email from ICANN Travel Support
>>
>> 4
>>
>> *Funded Traveler*
>>
>> *Book Air Travel for meeting*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Approved dates of Arrival and Departure*
>>
>> *ARRIVAL DATE*
>>
>> *DEPARTURE DATE*
>>
>> *Friday, 20 October*
>>
>> *Friday, 27 October*
>>
>>
>>
>> For air, this must be booked using either via our online booking platform
>> (Concur) or official travel agency (FCM). ICANN org does not allow
>> self-booking
>>
>>
>>
>> Here is a short video: https://schedule.icann.org/bookingintro
>> [schedule.icann.org]
>> <https://urldefense.com/v3/__https:/schedule.icann.org/bookingintro__;!!PtGJab4!6pW1_pdlgZAWc4plnfVraHDns0K10hlcwttUG1zqaysd4w_HDu0y08J0oYf_hLGNbh5C576I-YmA6W8p2ai-bkNqjA$> which
>> may be helpful and explains the basic.
>>
>>
>>
>> Please note that when requesting travel support, in the interest of
>> fairness and in light of budget restrictions we would like you to take the
>> following into consideration:
>>
>>
>>
>> 1. Respond timely to ICANN Travel regarding your upcoming
>> travel and book by deadline given in email.
>>
>> 2. If you require a visa to enter the country, please make
>> sure to acquire your visa immediately. Please contact the ICANN travel
>> team to let them know you will need a visa.
>>
>> 3. *06 September 2023 (45 days before travel)* is the last
>> day to submit additions/replacements.
>>
>> 4. Requests past the deadline will be handled on a case by
>> case basis by ICANN. All additional travelers added after the 90-day
>> deadline are subject to availability, may NOT be placed in the same hotel
>> as their funded traveler groups, and may not be able to attend due to visa
>> issues.
>>
>> 5. If possible please book direct travel requests. Detours
>> and multi-stop trips are unfortunately not guaranteed.
>>
>> 6. If travelers want to extend their stay this must be done
>> at their own expense and should contact the hotel directly once the ICANN
>> hotel confirmation has be sent to them.
>>
>> 7. *Privately Booked Reservations*: ICANN will not refund
>> or take over accommodations directly booked by the funded traveler. If a
>> replacement has an existing hotel reservation, they will need to cancel
>> their reservation and ICANN will not be able to take over their reservation.
>>
>>
>>
>> Reminder:
>>
>> 1. GNSO supported traveler with a designated hotel accommodation
>> funding, a hotel room is automatically secured for you, please *DO
>> NOT* book your own hotel as it is un-reimbursable.
>> 2. All personal data provided to ICANN org in for purposes of
>> providing travel support for participants related to ICANN events will be
>> processed in accordance with the ICANN Privacy Policy [icann.org]
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=A_rkvV7hcBAIOU12pQX6fSkWBC6-P-bPaQDowX2oR_A&s=WwqcPGGS1mvkGHO5BjVc3E9ewPva_WoF-Snq25kq0OM&e=>.
>> Should you have any questions or concerns about this Privacy Policy and our
>> privacy practices, you may contact us at privacy at icann.org.
>> 3. As a reminder, for the AGM meeting only, incoming Councilors get
>> funding, as well as the then-incumbent Councilors.
>>
>>
>>
>> Many thanks for your cooperation!
>>
>> Thank you.
>>
>>
>>
>> With kind regards,
>>
>> *Terri*
>>
>> * ---*
>>
>> *Terri Agnew*
>>
>> Policy Operations Specialist (GNSO)
>>
>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>
>> *Skype ID:* terri.agnew.icann
>>
>>
>>
>> Find out more about the GNSO by visiting: https://learn.icann.org/
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=o7Auz997kA-HPv9PHJCjFVZw7Pgo8krw4MxfqCwBrIU&e=>
>>
>> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNSO&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=kWw4fQPNjw2lVKy1UjTxS2F0BmjEAzaDFWNmsYywbmE&e=>
>>
>> Transcripts and recordings of GNSO Working Group and Council events are
>> located on the GNSO Master Calendar
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org]
>> <https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!8INMZy5hr_i6Yi27V68uSCgysMrSh0T8Zy_7GinBsKyLiEmi5SwjU0X0WjLMLLJL9ahJLvw-PbFO82ncW8ar5iIH7DUd_A$>
>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org]
>> <https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!8INMZy5hr_i6Yi27V68uSCgysMrSh0T8Zy_7GinBsKyLiEmi5SwjU0X0WjLMLLJL9ahJLvw-PbFO82ncW8ar5iIH7DUd_A$>
>>
>> _______________________________________________
>>
>> NCUC-EC mailing list
>>
>> NCUC-EC at lists.ncuc.org
>>
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org] <https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!8INMZy5hr_i6Yi27V68uSCgysMrSh0T8Zy_7GinBsKyLiEmi5SwjU0X0WjLMLLJL9ahJLvw-PbFO82ncW8ar5iIH7DUd_A$>
>>
>>
>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org]
>> <https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!8INMZy5hr_i6Yi27V68uSCgysMrSh0T8Zy_7GinBsKyLiEmi5SwjU0X0WjLMLLJL9ahJLvw-PbFO82ncW8ar5iIH7DUd_A$>
>>
>>
>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec [lists.ncuc.org]
>> <https://urldefense.com/v3/__https:/lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec__;!!PtGJab4!_B2Uc6c3Bb8eWTCZo8ehpOUHGto_O1hvzYdPc-1n4rgLWrhlWg1G6IQKKcHF1-fNGC_gx7eJXMt2riFp1-Lr6Cwc$>
>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20230627/0a0e5d3d/attachment-0001.htm>
More information about the NCUC-EC
mailing list