[NCUC-EC] [Ext] Re: Fwd: REMINDER ICANN78 | Hamburg | Supported Travelers Database Due | Thursday, 22 June 2023

[Benjamin Akinmoyeje]

Dear Olga,
Good day and I appreciate your feedback.

However, I do not appreciate the consistent insinuations that you keep
throwing up. I made genuine recommendations based on the available
information and understanding that I have of the situation, (by the way it
is just a recommendation I made).

In this conversation, you have used the term "unfair" and now you are using
the word "mess".

I did not delay the selection, if I may bring it to your attention that
ICANN 78 travel slot was supposed to be discussed in the last EC meeting
that no one showed interest in.

If my memory serves me, during the discussion of the travel slots
discussion toward ICANN76, you informed the group that this was your last
opportunity to attend the ICANN meeting, so it came to my surprise when you
indicated an interest in the Hamburg meeting.

The most important thing to select who to submit their names would be the
proposal for the meeting.

We had an EC member who got a travel slot at ICANN77 and refused to show up.

I will encourage everyone to develop their plan and submit it and let all
of us review them, We need to be accountable to our community and they are
demanding our active participation and input.

Kind regards,
Benjamin

On Thu, Jun 22, 2023 at 12:37 PM Olga Kyryliuk <olga_kyryliuk at ukr.net>
wrote:

> Hi Andrea!
>
> Many thanks for checking all those details. I will be traveling from
> Poland. So when your colleague is back to office, let me know whether I can
> be qualified for CROP.
>
> Meanwhile, you can proceed with Mili and Ken as EC funded travelers to
> meet today’s deadline.
>
> Ben, I must also admit this is absolutely not ok that every time we need
> to submit names for travel slots, the whole mess starts around this and we
> are always late with deadlines. Last time Mili could easily use CROP for
> Washington but we just wasted opportunity cos of missed deadline. This
> shouldn’t be a case. There should be a clear predictable rotation calendar
> and I created one some time ago but it was never properly discussed and
> same story repeats before every meeting.
>
> Best,
> Olga
>
>
> * 21 червня 2023 р. о 22:35:20,від "Andrea Glandon"
> <andrea.glandon at icann.org <andrea.glandon at icann.org>>: *
>
> 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. 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*
>
>
>
>
>    - 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:
>
>
>    - 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.
>
>    - 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.
>
>    - 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20230622/b93ae410/attachment-0001.htm>