[NCUC-EC] REMINDER-NCUC ICANN79 Travel Database

[Hfaiedh Ines]

Thank you Amin for this.
I have suggested to Benjamin that we collect all the suggestions in a doc
as a way forward for ECs attending meetings in general, and the upcoming
one in particular, and populate it each time there are updates and a
clearer idea about hot topics.

On Sun, Nov 5, 2023, 20:04 Amin Hacha <aminhacha at gmail.com> wrote:

> Thank you, Ken. Also for the mentioned points which I agree with.
> I would like to suggest a point that I believe could be beneficial for us.
> Typically the staff of the ICANN regional office organize special meetings
> with the participants from their region. For that, I see engaging with such
> meetings allows us the opportunity to introduce NCUC works to the
> participants.
> Regarding availability for ICANN 80 and/or 81, It is challenging for me to
> know from now. However, I lean towards my interest in the subject of Policy
> meetings/Forum.
>
> On Fri, Nov 3, 2023 at 3:40 PM Ken Herman <ken at kherman.com> wrote:
>
>> Good choices, Benjamin. I feel sure Inez and Amin will represent the
>> NCUC very well.
>>
>>
>>
>> Below are some of my thoughts from ICANN78 regarding participation by
>> ICANN-funded EC members. As they prepare their plans, I suggest that EC
>> members should be prepared to:
>>
>> a.     Attend, in-person, all NCSG and NCUC scheduled events.
>>
>> b.     Agree to follow a specific issue during the meeting and prepare a
>> brief summary of the discussions of those meetings.
>>
>> c.     Attend the Fellows Non-Commercial introduction session (the NCUC
>> Chair will introduce all attending regional reps) and the Fellows social to
>> meet the Fellows and explain the NCUC (as long as it does not conflict with
>> other required sessions).
>>
>> d.     Deliver a summary of general observations at the following
>> Readout.
>>
>>
>>
>> As a member of the Transfer Policy Review working group, I followed that
>> discussion and will prepare my summary before our Readout as well as
>> deliver some overall observations at the Readout on Monday.
>>
>>
>>
>> I recommend that we come to an agreement by our next EC meeting of which
>> EC members are willing and able to attend ICANN80 (Policy Forum) and 81
>> (AGM). I know it can be difficult to know far ahead of time our ability to
>> travel, but at the same time sometimes it can be helpful to know that
>> travel is coming, and we can plan accordingly. The Travel Policy provides
>> some guidelines, such as ICANN-funded EC members may not be ICANN-funded
>> for following meeting. Exceptions have been made if there are no other
>> eligible EC members available to attend.
>>
>>
>>
>> For my part, I will likely be most available for ICANN81 (although it may
>> depend on location, which has yet to be announced).
>>
>>
>>
>> Ken
>>
>>
>>
>> *From:* NCUC-EC <ncuc-ec-bounces at lists.ncuc.org> *On Behalf Of *Benjamin
>> Akinmoyeje
>> *Sent:* Thursday, November 2, 2023 5:05 PM
>> *To:* Mili <milisemlani at gmail.com>
>> *Cc:* ncuc-ec at lists.ncuc.org
>> *Subject:* Re: [NCUC-EC] REMINDER-NCUC ICANN79 Travel Database
>>
>>
>>
>> Dear All,
>>
>> Good day, and I hope you are all doing well.
>>
>>
>>
>> The list of ECs with interest to attend the next meeting is
>>
>> 1. Hfaiedh Ines
>> 2. Amin Hacha
>>
>>
>>
>> It would be great to have both of you share a draft plan of your ICANN79
>> activities to support the NCUC outreach and policy engagement in San Juan,
>> Puerto Rico.
>>
>>
>>
>> Apologies for the delay; I have been traveling.
>>
>>
>>
>> Kind regards,
>>
>> Benjamin
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Nov 1, 2023 at 11:25 AM Mili <milisemlani at gmail.com> wrote:
>>
>> Noted.
>>
>>
>>
>> I think Benji in his first email mentioned something about an extra one.
>> Anyway never mind.
>>
>>
>>
>>
>>
>> --
>>
>> 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 Nov 1, 2023, at 14:49, Johan Helsingius <julf at julf.com> wrote:
>>
>> Unfortunately the only NCSG slot is the one for one of the NCSG EC reps.
>>
>>    Julf
>>
>> On 01/11/2023 09:59, Mili wrote:
>>
>> If there is an additional NCSG slot, I would like to pitch my name for
>> that.
>>
>> --
>>
>> 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 Nov 1, 2023, at 14:03, Hfaiedh Ines <hfaiedh.ines2 at gmail.com> wrote:
>>
>> 
>>
>> Hello Andrea
>>
>> As expressed on the initial ncuc-ec email thread on this topic days ago.
>> I reconfirm my availibility to attend ICANN 79.
>>
>> On Wed, Nov 1, 2023, 09:29 Amin Hacha <aminhacha at gmail.com <mailto:
>> aminhacha at gmail.com>> wrote:
>>
>>    Hello Benjamin,
>>
>>    As for my availability, I confirm that I am available to travel and
>>
>>    participate in ICANN79. I am committed as usual to actively engaging
>>
>>    in the meetings and contributing meaningfully to our discussions and
>>
>>    endeavors.
>>
>>    Kind regards,
>>
>>    Amin
>>
>>        *From: *NCUC-EC <ncuc-ec-bounces at lists.ncuc.org
>>
>>        <mailto:ncuc-ec-bounces at lists.ncuc.org>> on behalf of Andrea
>>
>>        Glandon <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org
>> >>
>>
>>        *Date: *Monday, October 16, 2023 at 19:52
>>
>>        *To: *Amin Hacha <aminhacha at gmail.com <mailto:aminhacha at gmail.com
>> >>
>>
>>        *Cc: *"'Exec. Comm'" <ncuc-ec at lists.ncuc.org
>>
>>        <mailto:ncuc-ec at lists.ncuc.org>>
>>
>>        *Subject: *[NCUC-EC] FW: [Ext] Fwd: NCUC ICANN79 Travel
>> Database____
>>
>>        __ __
>>
>>        Hello Amin, ____
>>
>>        __ __
>>
>>        I am forwarding the email from Benjamin to the EC about travel
>>
>>        to ICANN79. ____
>>
>>        __ __
>>
>>        I will add you to the EC list after ICANN78.____
>>
>>        __ __
>>
>>        Thanks!____
>>
>>        Kind Regards,____
>>
>>        Andrea____
>>
>>        __ __
>>
>>        __ __
>>
>>        *From: *NCUC-EC <ncuc-ec-bounces at lists.ncuc.org
>>
>>        <mailto:ncuc-ec-bounces at lists.ncuc.org>> on behalf of Benjamin
>>
>>        Akinmoyeje <benakin at gmail.com <mailto:benakin at gmail.com>>
>>
>>        *Date: *Friday, October 13, 2023 at 08:14
>>
>>        *To: *"Exec. Comm" <ncuc-ec at lists.ncuc.org
>>
>>        <mailto:ncuc-ec at lists.ncuc.org>>
>>
>>        *Subject: *[Ext] [NCUC-EC] Fwd: NCUC ICANN79 Travel Database____
>>
>>        __ __
>>
>>        Dear NCUC Leaders, ____
>>
>>        Good day and I hope you are doing well.____
>>
>>        __ __
>>
>>        It is another time to select members going to attend ICANN79.
>>
>>        Please indicate your availability to travel and also your plan
>>
>>        for participation at the meeting.____
>>
>>        __ __
>>
>>        There is an additional travel  slot from NCSG as well.____
>>
>>        __ __
>>
>>        Looking forward to hearing from you soon.____
>>
>>        __ __
>>
>>        Kind regards,____
>>
>>        Benjamin____
>>
>>        ---------- Forwarded message ---------
>>
>>        From: *Andrea Glandon* <andrea.glandon at icann.org
>>
>>        <mailto:andrea.glandon at icann.org>>
>>
>>        Date: Fri, Oct 6, 2023 at 10:59 PM
>>
>>        Subject: NCUC ICANN79 Travel Database
>>
>>        To: Benjamin Akinmoyeje <benakin at gmail.com
>>
>>        <mailto:benakin at gmail.com>>
>>
>>        Cc: Andrea Glandon <andrea.glandon at icann.org
>>
>>        <mailto:andrea.glandon at icann.org>>____
>>
>>        __ __
>>
>>        Hello Benjamin, ____
>>
>>        ____
>>
>>        I know this is hard to believe, but we already need to think
>>
>>        about the ICANN79 travel database. I need your names by
>>
>>        Thursday, 02 November 2023.____
>>
>>        ____
>>
>>        You have 3 slots, one of which belongs to you.____
>>
>>        ____
>>
>>        Thanks!____
>>
>>        *Andrea Glandon*____
>>
>>        Policy Operations Coordinator____
>>
>>        Internet Corporation for Assigned Names and Numbers (ICANN)____
>>
>>        *Skype ID:*  acglandon76____
>>
>>        ____
>>
>>        ____
>>
>>        ____
>>
>>    _______________________________________________
>>
>>    NCUC-EC mailing list
>>
>>    NCUC-EC at lists.ncuc.org <mailto:NCUC-EC at lists.ncuc.org>
>>
>>    https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>>
>>    <https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec>
>>
>> _______________________________________________
>>
>> NCUC-EC mailing list
>>
>> NCUC-EC at lists.ncuc.org
>>
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>>
>> _______________________________________________
>>
>> NCUC-EC mailing list
>>
>> NCUC-EC at lists.ncuc.org
>>
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>>
>> _______________________________________________
>> NCUC-EC mailing list
>> NCUC-EC at lists.ncuc.org
>> https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>>
> _______________________________________________
> 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/20231105/9785b74d/attachment-0001.htm>