From julf at julf.com  Sun Jun  2 08:53:39 2024
From: julf at julf.com (Johan Helsingius)
Date: Sun, 2 Jun 2024 07:53:39 +0200
Subject: [NCSG-EC] Fwd: NomCom changes
In-Reply-To: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
Message-ID: <26b91959-5c8a-4674-a49d-d54e24049b6e@julf.com>

The deadline has been amended to 5 June 2024.

	Julf


-------- Forwarded Message --------
Subject: 	NomCom changes
Date: 	Fri, 31 May 2024 14:41:19 +0000
From: 	DiBiase, Gregory <dibiase at amazon.com>
To: 	aheineman at godaddy.com <aheineman at godaddy.com>, Lori Schulman 
<lschulman at inta.org>, Cole, Mason (POR) <MCole at perkinscoie.com>, Johan 
Helsingius <julf at Julf.com>, sdemetriou at verisign.com 
<sdemetriou at verisign.com>, philippe.fouquart at orange.com 
<philippe.fouquart at orange.com>
CC: 	Steve Chan <steve.chan at icann.org>, gnso-secs at icann.org 
<gnso-secs at icann.org>



Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,

I am writing to you all in your roles as Chairs of Stakeholder Groups or 
Constituencies that appoint delegates to ICANN?s Nominating Committee 
(NomCom).

You may recall that the NomCom2 Review produced 27 recommendations, 
several of which relate to the composition and terms of the NomCom. In 
order to effectuate these particular recommendations, the ICANN Board 
approved Standard Bylaws Amendments in Articles 8, 12, and 27.

The Bylaws amendments made no change to the number and nature of 
delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC, 
NCSG, and 2 from the BC), though the length of terms were extended to 
two years (see Section 8.3 of the Bylaws). However, from Article 27, in 
order to, ?effectuate the introduction of the two-year terms and support 
the goal of staggering delegate terms??, three of the GNSO delegates 
shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE states that 
the GNSO is responsible for determining which three of the seven 
delegates shall initially serve one-year terms.

Unfortunately, no guidance was provided on how to identify the three of 
seven GNSO delegates to serve one-year terms. For reference, the ALAC 
was also in the position of having to identify a subset of delegates to 
serve one-year terms. They elected to rely on random selection during a 
live call.

The GNSO may want to rely on a similarly simple approach. An important 
point in considering the approach is that the level of representation on 
the NomCom is not affected by the term-length. However, the SG/Cs with 
one-year terms will have to replace those delegates after one year 
rather than two.

*Question: Do you believe there would be any objections from your 
groups, and potentially delegates that you have already identified, to 
proceeding with a simple path forward in which we randomly select three 
of seven GNSO delegates to serve one-year terms?*

If you believe that there may be concerns (e.g., we may want to avoid 
having the one-year terms concentrated in particular areas), please 
share them with Council leadership no later than 31 May 2024.

If however there are no concerns, Council leadership can perform the 
random selection process with staff or if you prefer, on a Zoom call 
with all of you.

Thanks,

Greg DiBiase, GNSO Chair



From farzaneh.badii at gmail.com  Sun Jun  2 09:03:02 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Sun, 2 Jun 2024 02:03:02 -0400
Subject: [NCSG-EC] Fwd: NomCom changes
In-Reply-To: <26b91959-5c8a-4674-a49d-d54e24049b6e@julf.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <26b91959-5c8a-4674-a49d-d54e24049b6e@julf.com>
Message-ID: <CAN1qJvAnVHo1=gBuzcGfuQF7jMhhnbOzpyGyQUnh5fBx42BVSg@mail.gmail.com>

Julf,
They are doing the bylaws amendment change and they didn't give us a simple
equal number of delegates on NomCom? We need to have a meeting with the
CPH, describe the issue to them and ask them to reconsider this at the GNSO
council.

As to how we should have a one year term for some delegates, I am so
surprised what is the point of this recommendation??... this has always
been in the mandate of each stakeholder group? We have issued calls for
delegates every year since I think at least 2017 or 2018.  Whatever the
decision, it should NOT undermine the noncommercial delegation on nomcom
any further.



Farzaneh


On Sun, Jun 2, 2024 at 1:53?AM Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> The deadline has been amended to 5 June 2024.
>
>         Julf
>
>
> -------- Forwarded Message --------
> Subject:        NomCom changes
> Date:   Fri, 31 May 2024 14:41:19 +0000
> From:   DiBiase, Gregory <dibiase at amazon.com>
> To:     aheineman at godaddy.com <aheineman at godaddy.com>, Lori Schulman
> <lschulman at inta.org>, Cole, Mason (POR) <MCole at perkinscoie.com>, Johan
> Helsingius <julf at Julf.com>, sdemetriou at verisign.com
> <sdemetriou at verisign.com>, philippe.fouquart at orange.com
> <philippe.fouquart at orange.com>
> CC:     Steve Chan <steve.chan at icann.org>, gnso-secs at icann.org
> <gnso-secs at icann.org>
>
>
>
> Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
>
> I am writing to you all in your roles as Chairs of Stakeholder Groups or
> Constituencies that appoint delegates to ICANN?s Nominating Committee
> (NomCom).
>
> You may recall that the NomCom2 Review produced 27 recommendations,
> several of which relate to the composition and terms of the NomCom. In
> order to effectuate these particular recommendations, the ICANN Board
> approved Standard Bylaws Amendments in Articles 8, 12, and 27.
>
> The Bylaws amendments made no change to the number and nature of
> delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC,
> NCSG, and 2 from the BC), though the length of terms were extended to
> two years (see Section 8.3 of the Bylaws). However, from Article 27, in
> order to, ?effectuate the introduction of the two-year terms and support
> the goal of staggering delegate terms??, three of the GNSO delegates
> shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE states that
> the GNSO is responsible for determining which three of the seven
> delegates shall initially serve one-year terms.
>
> Unfortunately, no guidance was provided on how to identify the three of
> seven GNSO delegates to serve one-year terms. For reference, the ALAC
> was also in the position of having to identify a subset of delegates to
> serve one-year terms. They elected to rely on random selection during a
> live call.
>
> The GNSO may want to rely on a similarly simple approach. An important
> point in considering the approach is that the level of representation on
> the NomCom is not affected by the term-length. However, the SG/Cs with
> one-year terms will have to replace those delegates after one year
> rather than two.
>
> *Question: Do you believe there would be any objections from your
> groups, and potentially delegates that you have already identified, to
> proceeding with a simple path forward in which we randomly select three
> of seven GNSO delegates to serve one-year terms?*
>
> If you believe that there may be concerns (e.g., we may want to avoid
> having the one-year terms concentrated in particular areas), please
> share them with Council leadership no later than 31 May 2024.
>
> If however there are no concerns, Council leadership can perform the
> random selection process with staff or if you prefer, on a Zoom call
> with all of you.
>
> Thanks,
>
> Greg DiBiase, GNSO Chair
>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240602/e307f43a/attachment.htm>

From julf at julf.com  Sun Jun  2 09:28:45 2024
From: julf at julf.com (Johan Helsingius)
Date: Sun, 2 Jun 2024 08:28:45 +0200
Subject: [NCSG-EC] Fwd: NomCom changes
In-Reply-To: <CAN1qJvAnVHo1=gBuzcGfuQF7jMhhnbOzpyGyQUnh5fBx42BVSg@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <26b91959-5c8a-4674-a49d-d54e24049b6e@julf.com>
 <CAN1qJvAnVHo1=gBuzcGfuQF7jMhhnbOzpyGyQUnh5fBx42BVSg@mail.gmail.com>
Message-ID: <f223a561-a72f-4f88-ac6e-e9a78c8fe7ff@julf.com>

When the changes were voted on in the WG our rep was missing in action.
When the council discussed reopening it, we didn't get support from
the CPH. We have been discussing it with them, as well as with the
board governance committee, but so far little progress.

	Julf

On 02/06/2024 08:03, farzaneh badii wrote:
> Julf,
> They are doing?the bylaws amendment change and they didn't give us a 
> simple equal number of delegates on NomCom? We need to have a meeting 
> with the CPH, describe the issue to them and ask them to reconsider this 
> at the GNSO council.
> 
> As to how we should have a one year term for some delegates, I am so 
> surprised what is the point of this recommendation??... this has always 
> been in the mandate of each stakeholder group? We have issued calls for 
> delegates every year since I think at least 2017 or 2018.? Whatever the 
> decision, it should NOT undermine the noncommercial delegation on nomcom 
> any further.
> 
> 
> 
> Farzaneh
> 
> 
> On Sun, Jun 2, 2024 at 1:53?AM Johan Helsingius via NCSG-EC 
> <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> 
>     The deadline has been amended to 5 June 2024.
> 
>      ? ? ? ? Julf
> 
> 
>     -------- Forwarded Message --------
>     Subject:? ? ? ? NomCom changes
>     Date:? ?Fri, 31 May 2024 14:41:19 +0000
>     From:? ?DiBiase, Gregory <dibiase at amazon.com
>     <mailto:dibiase at amazon.com>>
>     To: aheineman at godaddy.com <mailto:aheineman at godaddy.com>
>     <aheineman at godaddy.com <mailto:aheineman at godaddy.com>>, Lori Schulman
>     <lschulman at inta.org <mailto:lschulman at inta.org>>, Cole, Mason (POR)
>     <MCole at perkinscoie.com <mailto:MCole at perkinscoie.com>>, Johan
>     Helsingius <julf at Julf.com>, sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>
>     <sdemetriou at verisign.com <mailto:sdemetriou at verisign.com>>,
>     philippe.fouquart at orange.com <mailto:philippe.fouquart at orange.com>
>     <philippe.fouquart at orange.com <mailto:philippe.fouquart at orange.com>>
>     CC:? ? ?Steve Chan <steve.chan at icann.org
>     <mailto:steve.chan at icann.org>>, gnso-secs at icann.org
>     <mailto:gnso-secs at icann.org>
>     <gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
> 
> 
> 
>     Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
> 
>     I am writing to you all in your roles as Chairs of Stakeholder
>     Groups or
>     Constituencies that appoint delegates to ICANN?s Nominating Committee
>     (NomCom).
> 
>     You may recall that the NomCom2 Review produced 27 recommendations,
>     several of which relate to the composition and terms of the NomCom. In
>     order to effectuate these particular recommendations, the ICANN Board
>     approved Standard Bylaws Amendments in Articles 8, 12, and 27.
> 
>     The Bylaws amendments made no change to the number and nature of
>     delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP, IPC,
>     NCSG, and 2 from the BC), though the length of terms were extended to
>     two years (see Section 8.3 of the Bylaws). However, from Article 27, in
>     order to, ?effectuate the introduction of the two-year terms and
>     support
>     the goal of staggering delegate terms??, three of the GNSO delegates
>     shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE states that
>     the GNSO is responsible for determining which three of the seven
>     delegates shall initially serve one-year terms.
> 
>     Unfortunately, no guidance was provided on how to identify the three of
>     seven GNSO delegates to serve one-year terms. For reference, the ALAC
>     was also in the position of having to identify a subset of delegates to
>     serve one-year terms. They elected to rely on random selection during a
>     live call.
> 
>     The GNSO may want to rely on a similarly simple approach. An important
>     point in considering the approach is that the level of
>     representation on
>     the NomCom is not affected by the term-length. However, the SG/Cs with
>     one-year terms will have to replace those delegates after one year
>     rather than two.
> 
>     *Question: Do you believe there would be any objections from your
>     groups, and potentially delegates that you have already identified, to
>     proceeding with a simple path forward in which we randomly select three
>     of seven GNSO delegates to serve one-year terms?*
> 
>     If you believe that there may be concerns (e.g., we may want to avoid
>     having the one-year terms concentrated in particular areas), please
>     share them with Council leadership no later than 31 May 2024.
> 
>     If however there are no concerns, Council leadership can perform the
>     random selection process with staff or if you prefer, on a Zoom call
>     with all of you.
> 
>     Thanks,
> 
>     Greg DiBiase, GNSO Chair
> 
>     _______________________________________________
>     NCSG-EC mailing list
>     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> 


From muyiwacaleb at gmail.com  Sun Jun  2 14:31:28 2024
From: muyiwacaleb at gmail.com (Caleb Olumuyiwa Ogundele)
Date: Sun, 2 Jun 2024 06:31:28 -0500
Subject: [NCSG-EC] Fwd: NomCom changes
In-Reply-To: <f223a561-a72f-4f88-ac6e-e9a78c8fe7ff@julf.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <26b91959-5c8a-4674-a49d-d54e24049b6e@julf.com>
 <CAN1qJvAnVHo1=gBuzcGfuQF7jMhhnbOzpyGyQUnh5fBx42BVSg@mail.gmail.com>
 <f223a561-a72f-4f88-ac6e-e9a78c8fe7ff@julf.com>
Message-ID: <CAL_ZvK6_+Q-EoADWonuuFDzgL=mcgUQz8ZtYpmL5gBgkCSOzag@mail.gmail.com>

I think we should still press for the equal distribution.  Two seats for
the BC???


On Sun, Jun 2, 2024, 1:28?AM Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> When the changes were voted on in the WG our rep was missing in action.
> When the council discussed reopening it, we didn't get support from
> the CPH. We have been discussing it with them, as well as with the
> board governance committee, but so far little progress.
>
>         Julf
>
> On 02/06/2024 08:03, farzaneh badii wrote:
> > Julf,
> > They are doing the bylaws amendment change and they didn't give us a
> > simple equal number of delegates on NomCom? We need to have a meeting
> > with the CPH, describe the issue to them and ask them to reconsider this
> > at the GNSO council.
> >
> > As to how we should have a one year term for some delegates, I am so
> > surprised what is the point of this recommendation??... this has always
> > been in the mandate of each stakeholder group? We have issued calls for
> > delegates every year since I think at least 2017 or 2018.  Whatever the
> > decision, it should NOT undermine the noncommercial delegation on nomcom
> > any further.
> >
> >
> >
> > Farzaneh
> >
> >
> > On Sun, Jun 2, 2024 at 1:53?AM Johan Helsingius via NCSG-EC
> > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> >
> >     The deadline has been amended to 5 June 2024.
> >
> >              Julf
> >
> >
> >     -------- Forwarded Message --------
> >     Subject:        NomCom changes
> >     Date:   Fri, 31 May 2024 14:41:19 +0000
> >     From:   DiBiase, Gregory <dibiase at amazon.com
> >     <mailto:dibiase at amazon.com>>
> >     To: aheineman at godaddy.com <mailto:aheineman at godaddy.com>
> >     <aheineman at godaddy.com <mailto:aheineman at godaddy.com>>, Lori
> Schulman
> >     <lschulman at inta.org <mailto:lschulman at inta.org>>, Cole, Mason (POR)
> >     <MCole at perkinscoie.com <mailto:MCole at perkinscoie.com>>, Johan
> >     Helsingius <julf at Julf.com>, sdemetriou at verisign.com
> >     <mailto:sdemetriou at verisign.com>
> >     <sdemetriou at verisign.com <mailto:sdemetriou at verisign.com>>,
> >     philippe.fouquart at orange.com <mailto:philippe.fouquart at orange.com>
> >     <philippe.fouquart at orange.com <mailto:philippe.fouquart at orange.com>>
> >     CC:     Steve Chan <steve.chan at icann.org
> >     <mailto:steve.chan at icann.org>>, gnso-secs at icann.org
> >     <mailto:gnso-secs at icann.org>
> >     <gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
> >
> >
> >
> >     Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
> >
> >     I am writing to you all in your roles as Chairs of Stakeholder
> >     Groups or
> >     Constituencies that appoint delegates to ICANN?s Nominating Committee
> >     (NomCom).
> >
> >     You may recall that the NomCom2 Review produced 27 recommendations,
> >     several of which relate to the composition and terms of the NomCom.
> In
> >     order to effectuate these particular recommendations, the ICANN Board
> >     approved Standard Bylaws Amendments in Articles 8, 12, and 27.
> >
> >     The Bylaws amendments made no change to the number and nature of
> >     delegates from the GNSO (i.e., 1 each from the RySG, RrSG, ISPCP,
> IPC,
> >     NCSG, and 2 from the BC), though the length of terms were extended to
> >     two years (see Section 8.3 of the Bylaws). However, from Article 27,
> in
> >     order to, ?effectuate the introduction of the two-year terms and
> >     support
> >     the goal of staggering delegate terms??, three of the GNSO delegates
> >     shall serve a one-year term. ARTICLE 27 TRANSITION ARTICLE states
> that
> >     the GNSO is responsible for determining which three of the seven
> >     delegates shall initially serve one-year terms.
> >
> >     Unfortunately, no guidance was provided on how to identify the three
> of
> >     seven GNSO delegates to serve one-year terms. For reference, the ALAC
> >     was also in the position of having to identify a subset of delegates
> to
> >     serve one-year terms. They elected to rely on random selection
> during a
> >     live call.
> >
> >     The GNSO may want to rely on a similarly simple approach. An
> important
> >     point in considering the approach is that the level of
> >     representation on
> >     the NomCom is not affected by the term-length. However, the SG/Cs
> with
> >     one-year terms will have to replace those delegates after one year
> >     rather than two.
> >
> >     *Question: Do you believe there would be any objections from your
> >     groups, and potentially delegates that you have already identified,
> to
> >     proceeding with a simple path forward in which we randomly select
> three
> >     of seven GNSO delegates to serve one-year terms?*
> >
> >     If you believe that there may be concerns (e.g., we may want to avoid
> >     having the one-year terms concentrated in particular areas), please
> >     share them with Council leadership no later than 31 May 2024.
> >
> >     If however there are no concerns, Council leadership can perform the
> >     random selection process with staff or if you prefer, on a Zoom call
> >     with all of you.
> >
> >     Thanks,
> >
> >     Greg DiBiase, GNSO Chair
> >
> >     _______________________________________________
> >     NCSG-EC mailing list
> >     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240602/59c89baa/attachment.htm>

From julf at julf.com  Sun Jun  2 15:07:22 2024
From: julf at julf.com (Johan Helsingius)
Date: Sun, 2 Jun 2024 14:07:22 +0200
Subject: [NCSG-EC] Fwd: NomCom changes
In-Reply-To: <CAL_ZvK6_+Q-EoADWonuuFDzgL=mcgUQz8ZtYpmL5gBgkCSOzag@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <26b91959-5c8a-4674-a49d-d54e24049b6e@julf.com>
 <CAN1qJvAnVHo1=gBuzcGfuQF7jMhhnbOzpyGyQUnh5fBx42BVSg@mail.gmail.com>
 <f223a561-a72f-4f88-ac6e-e9a78c8fe7ff@julf.com>
 <CAL_ZvK6_+Q-EoADWonuuFDzgL=mcgUQz8ZtYpmL5gBgkCSOzag@mail.gmail.com>
Message-ID: <9930b4ab-d4e3-4094-9392-b8bb2f094bb5@julf.com>

On 02/06/2024 13:31, Caleb Olumuyiwa Ogundele wrote:
> I think we should still press for the equal distribution.? Two seats for 
> the BC???

We have been (and keep on) pressing. Yes, the two BC seats don't make
any sense. It was classic Marilyn Cade.

	Julf



From farzaneh.badii at gmail.com  Mon Jun  3 03:34:35 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Sun, 2 Jun 2024 20:34:35 -0400
Subject: [NCSG-EC] Fwd: NomCom changes
In-Reply-To: <9930b4ab-d4e3-4094-9392-b8bb2f094bb5@julf.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <26b91959-5c8a-4674-a49d-d54e24049b6e@julf.com>
 <CAN1qJvAnVHo1=gBuzcGfuQF7jMhhnbOzpyGyQUnh5fBx42BVSg@mail.gmail.com>
 <f223a561-a72f-4f88-ac6e-e9a78c8fe7ff@julf.com>
 <CAL_ZvK6_+Q-EoADWonuuFDzgL=mcgUQz8ZtYpmL5gBgkCSOzag@mail.gmail.com>
 <9930b4ab-d4e3-4094-9392-b8bb2f094bb5@julf.com>
Message-ID: <CAN1qJvBJwNO4jrqw7KrP95Dv1cMCzMY_PsYiijJ_VodAwRM_Uw@mail.gmail.com>

I wonder if we should do it in a more effective way:
1) write a letter to the board
2) set up meetings with the cph to specifically talk about this
3) talk to ISPCP

And highlight the issue and make it public. It?s just that somebody needs
to volunteer to do those things and I don?t have the bandwidth to follow
up. Can somebody volunteer?

Farzaneh


On Sun, Jun 2, 2024 at 8:07?AM Johan Helsingius <julf at julf.com> wrote:

> On 02/06/2024 13:31, Caleb Olumuyiwa Ogundele wrote:
> > I think we should still press for the equal distribution.  Two seats for
> > the BC???
>
> We have been (and keep on) pressing. Yes, the two BC seats don't make
> any sense. It was classic Marilyn Cade.
>
>         Julf
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240602/8c981a51/attachment.htm>

From julf at Julf.com  Mon Jun  3 12:51:22 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 3 Jun 2024 11:51:22 +0200
Subject: [NCSG-EC] Fwd: NomCom changes
In-Reply-To: <CAN1qJvBJwNO4jrqw7KrP95Dv1cMCzMY_PsYiijJ_VodAwRM_Uw@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <26b91959-5c8a-4674-a49d-d54e24049b6e@julf.com>
 <CAN1qJvAnVHo1=gBuzcGfuQF7jMhhnbOzpyGyQUnh5fBx42BVSg@mail.gmail.com>
 <f223a561-a72f-4f88-ac6e-e9a78c8fe7ff@julf.com>
 <CAL_ZvK6_+Q-EoADWonuuFDzgL=mcgUQz8ZtYpmL5gBgkCSOzag@mail.gmail.com>
 <9930b4ab-d4e3-4094-9392-b8bb2f094bb5@julf.com>
 <CAN1qJvBJwNO4jrqw7KrP95Dv1cMCzMY_PsYiijJ_VodAwRM_Uw@mail.gmail.com>
Message-ID: <4fae0a76-6169-4eae-978a-6eb8c05b1b8c@Julf.com>

Of those, the only one we haven't done is the letter to the
board, but we have met multiple times with people from the
board governance committee (that according to the board is
the appropriate people to talk to). They understand the issue,
but it is the usual "it is up to the community".

The CPH is ready to support us in a vote, but won't do anything
active. That is at least an improvement compared to the
earlier situation when they didn't support us in the council
vote on this matter.

ISPCP don't want to go against CPH "consensus".

What everyone is saying is "you had your chance with the
review team" - unfortunately our reps let us down, and we
didn't check on them. We had a second chance when the
council voted to approve the team recommendations, but
that was an uphill struggle and we failed to do enough
to convince people in the period leading up to the vote.

Now the response I get is often "you will have to wait
for the holistic review that will probably rehash the
whole GNSO structure", but that will take forever.

	Julf

On 03/06/2024 02:34, farzaneh badii wrote:
> I wonder if we should do it in a more effective way:
> 1) write a letter to the board
> 2) set up meetings with the cph to specifically talk about this
> 3) talk to ISPCP
> 
> And highlight the issue and make it public. It?s just that somebody 
> needs to volunteer to do those things and I don?t have the bandwidth to 
> follow up. Can somebody volunteer?
> 
> Farzaneh
> 
> 
> On Sun, Jun 2, 2024 at 8:07?AM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     On 02/06/2024 13:31, Caleb Olumuyiwa Ogundele wrote:
>      > I think we should still press for the equal distribution.? Two
>     seats for
>      > the BC???
> 
>     We have been (and keep on) pressing. Yes, the two BC seats don't make
>     any sense. It was classic Marilyn Cade.
> 
>      ? ? ? ? Julf
> 


From andrea.glandon at icann.org  Mon Jun  3 15:34:39 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Mon, 3 Jun 2024 12:34:39 +0000
Subject: [NCSG-EC] ICANN80 NCSG EC Sign-up Room
Message-ID: <1ce828d9eb1b413097b06af6af6642a9@icann.org>

Dear all,

Your ICANN80 sign-up room has been scheduled with the following information.

Title: NCSG EC
Date: Thurday, 13 June 2024
Time: 13:45 ? 15:00 CAT
Room: AD1

IMPORTANT NOTE:

NO AUDIO VISUAL OR TECHNICAL SERVICES ARE AVAILABLE FOR SIGN-UP ROOMS.

No projection, microphones, audio system phone calls, or technical assistance is available for this meeting.

To get these services in the future, a session request must be submitted in advance of the ICANN meeting.

Thank you.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240603/25537bcb/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1797 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240603/25537bcb/attachment.ics>

From julf at Julf.com  Wed Jun  5 12:41:42 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 5 Jun 2024 11:41:42 +0200
Subject: [NCSG-EC] [NCUC-EC] NomCom changes
In-Reply-To: <CAOMFwikCq0qSrL_7pC9bjeuOc3f1_K2VbYfGydC3t9WgfEPozg@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <491d2a86-1b99-41ec-8c3e-e6feeed33f43@julf.com>
 <CAJR4JuFBDoXi47rF+9cBh4iyTBF4hvjTcit+5+TpCZayfvgdAw@mail.gmail.com>
 <df81596f-3e26-4d5a-ac95-ca59064cfc24@Julf.com>
 <CAJR4JuEq=MrSM_n=cxhoddj5uMUwF0jxyX9yUx_P_fHNcZtSWQ@mail.gmail.com>
 <CAOMFwikCq0qSrL_7pC9bjeuOc3f1_K2VbYfGydC3t9WgfEPozg@mail.gmail.com>
Message-ID: <18b4ef3c-cc40-46f2-bb58-9f225718f684@Julf.com>

Thanks Ines!

There is a reference to a "transition article" (Article 27) that seems
to be pretty crucial. Do you have any documents describing the
transition article?

I am also curious about the recommendation 10, "Representation on
the NomCom should be rebalanced immediately and then be reviewed
every 5 years." that was withdrawn. Can you help shed some light
on the discussion that led to the withdrawal of the recommendation?

	Julf


On 05/06/2024 11:08, Hfaiedh Ines wrote:
> Hi Julf
> 
> Regarding membership I reached out to staff and here s the answer
> 
> Hello Ines,
> 
> 
> Thank you for reaching out - the work of the NomCom Review 
> Implementation Working Group (NomComRIWG) completed in June 2022, with 
> the submission?of the final report 
> <https://www.icann.org/en/system/files/files/nomcom2-review-final-report-30jun22-en.pdf>. The ICANN Board took action on 16 March 2023 <https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.b>to accept the status of the NomCom2 Review implementation and initiate an ICANN Bylaws Amendment process. On 10 September 2023 <https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-10-09-2023-en#section2.b>the Board took action on next steps in Bylaws Amendment Process. If you would like more information, please feel free to review the NomCom Review workspace or reach out to me for further updates.
> 
> 
> Thank you again for reaching out.
> 
> 
> Basically the nomcom review team finshed their work in June 2022 so 
> exactly two years ago.
> 
> To answer your question on NCSG or NCUC I? attached the final report 
> where there is no mention of either.? So we are speaking here of a board 
> resolution and my understanding is that they are leaving the floor open 
> to all constituencies to decide on how to proceed.
> 
> 
> On Tue, Jun 4, 2024, 21:31 Benjamin Akinmoyeje <benakin at gmail.com 
> <mailto:benakin at gmail.com>> wrote:
> 
>     I got your email. It was just that the GNSO chair , did not copy
>     NCUC chair.
> 
> 
>     That it is worthwhile noting for future, although in his email he
>     made references to stakeholder group an constituencies.
> 
>     I hope you see my point.
> 
>     Kind regards,
>     Benjamin
> 
> 
> 
> 
>     On Tue, Jun 4, 2024, 9:35?PM Johan Helsingius <julf at julf.com
>     <mailto:julf at julf.com>> wrote:
> 
>         I did copy ncuc-ec, assuming the chair would be part of it.
> 
>          ? ? ? ? Julf
> 
>         On 04/06/2024 18:59, Benjamin Akinmoyeje wrote:
>          >? ? Hi Julf,
>          > Thank you for this email....but it is strange that the?GNSO
>         chair has
>          > chosen not to copy the? NCUC Chair in this?email.
>          >
>          > NCUC appointed Pascal, our current Nomcom representative if I
>         am correct.
>          >
>          > It would be great if the GNSO chair could be pointed to this
>         omission.
>          >
>          > Just checking if things have changed.
>          >
>          >
>          > Kind regards,
>          > Benjamin
>          >
>          > On Sat, Jun 1, 2024 at 9:32?AM Johan Helsingius
>         <julf at julf.com <mailto:julf at julf.com>
>          > <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
>          >
>          >
>          >
>          >
>          >? ? ?-------- Forwarded Message --------
>          >? ? ?Subject:? ? ? ? NomCom changes
>          >? ? ?Date:? ?Fri, 31 May 2024 14:41:19 +0000
>          >? ? ?From:? ?DiBiase, Gregory <dibiase at amazon.com
>         <mailto:dibiase at amazon.com>
>          >? ? ?<mailto:dibiase at amazon.com <mailto:dibiase at amazon.com>>>
>          >? ? ?To: aheineman at godaddy.com <mailto:aheineman at godaddy.com>
>         <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>
>          >? ? ?<aheineman at godaddy.com <mailto:aheineman at godaddy.com>
>         <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>>,
>         Lori Schulman
>          >? ? ?<lschulman at inta.org <mailto:lschulman at inta.org>
>         <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>>, Cole,
>         Mason (POR)
>          >? ? ?<MCole at perkinscoie.com <mailto:MCole at perkinscoie.com>
>         <mailto:MCole at perkinscoie.com <mailto:MCole at perkinscoie.com>>>,
>         Johan
>          >? ? ?Helsingius <julf at Julf.com>, sdemetriou at verisign.com
>         <mailto:sdemetriou at verisign.com>
>          >? ? ?<mailto:sdemetriou at verisign.com
>         <mailto:sdemetriou at verisign.com>>
>          >? ? ?<sdemetriou at verisign.com <mailto:sdemetriou at verisign.com>
>         <mailto:sdemetriou at verisign.com <mailto:sdemetriou at verisign.com>>>,
>          > philippe.fouquart at orange.com
>         <mailto:philippe.fouquart at orange.com>
>         <mailto:philippe.fouquart at orange.com
>         <mailto:philippe.fouquart at orange.com>>
>          >? ? ?<philippe.fouquart at orange.com
>         <mailto:philippe.fouquart at orange.com>
>         <mailto:philippe.fouquart at orange.com
>         <mailto:philippe.fouquart at orange.com>>>
>          >? ? ?CC:? ? ?Steve Chan <steve.chan at icann.org
>         <mailto:steve.chan at icann.org>
>          >? ? ?<mailto:steve.chan at icann.org
>         <mailto:steve.chan at icann.org>>>, gnso-secs at icann.org
>         <mailto:gnso-secs at icann.org>
>          >? ? ?<mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
>          >? ? ?<gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>         <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>>
>          >
>          >
>          >
>          >? ? ?Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
>          >
>          >? ? ?I am writing to you all in your roles as Chairs of
>         Stakeholder
>          >? ? ?Groups or
>          >? ? ?Constituencies that appoint delegates to ICANN?s
>         Nominating Committee
>          >? ? ?(NomCom).
>          >
>          >? ? ?You may recall that the NomCom2 Review produced 27
>         recommendations,
>          >? ? ?several of which relate to the composition and terms of
>         the NomCom. In
>          >? ? ?order to effectuate these particular recommendations, the
>         ICANN Board
>          >? ? ?approved Standard Bylaws Amendments in Articles 8, 12,
>         and 27.
>          >
>          >? ? ?The Bylaws amendments made no change to the number and
>         nature of
>          >? ? ?delegates from the GNSO (i.e., 1 each from the RySG,
>         RrSG, ISPCP, IPC,
>          >? ? ?NCSG, and 2 from the BC), though the length of terms were
>         extended to
>          >? ? ?two years (see Section 8.3 of the Bylaws). However, from
>         Article 27, in
>          >? ? ?order to, ?effectuate the introduction of the two-year
>         terms and
>          >? ? ?support
>          >? ? ?the goal of staggering delegate terms??, three of the
>         GNSO delegates
>          >? ? ?shall serve a one-year term. ARTICLE 27 TRANSITION
>         ARTICLE states that
>          >? ? ?the GNSO is responsible for determining which three of
>         the seven
>          >? ? ?delegates shall initially serve one-year terms.
>          >
>          >? ? ?Unfortunately, no guidance was provided on how to
>         identify the three of
>          >? ? ?seven GNSO delegates to serve one-year terms. For
>         reference, the ALAC
>          >? ? ?was also in the position of having to identify a subset
>         of delegates to
>          >? ? ?serve one-year terms. They elected to rely on random
>         selection during a
>          >? ? ?live call.
>          >
>          >? ? ?The GNSO may want to rely on a similarly simple approach.
>         An important
>          >? ? ?point in considering the approach is that the level of
>          >? ? ?representation on
>          >? ? ?the NomCom is not affected by the term-length. However,
>         the SG/Cs with
>          >? ? ?one-year terms will have to replace those delegates after
>         one year
>          >? ? ?rather than two.
>          >
>          >? ? ?*Question: Do you believe there would be any objections
>         from your
>          >? ? ?groups, and potentially delegates that you have already
>         identified, to
>          >? ? ?proceeding with a simple path forward in which we
>         randomly select three
>          >? ? ?of seven GNSO delegates to serve one-year terms?*
>          >
>          >? ? ?If you believe that there may be concerns (e.g., we may
>         want to avoid
>          >? ? ?having the one-year terms concentrated in particular
>         areas), please
>          >? ? ?share them with Council leadership no later than 31 May 2024.
>          >
>          >? ? ?If however there are no concerns, Council leadership can
>         perform the
>          >? ? ?random selection process with staff or if you prefer, on
>         a Zoom call
>          >? ? ?with all of you.
>          >
>          >? ? ?Thanks,
>          >
>          >? ? ?Greg DiBiase, GNSO Chair
>          >
> 
>     _______________________________________________
>     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>
> 


From mesumbeslin at gmail.com  Wed Jun  5 15:50:53 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Wed, 5 Jun 2024 22:50:53 +1000
Subject: [NCSG-EC] Call for meeting topics for our Policy meeting in Kigali
Message-ID: <CAM8DdeXNQ2NXno0=Zs1Ms-srEHon=JKm+msaeEDfasNxHCnR=A@mail.gmail.com>

Hello team,

I am currently putting together the agenda for the policy meeting in
Kigali, so I am checking with you to know whether there are topics that you
would either like us to discuss or a topic you'd like to present to the
group? Some potential ones are:
1. The board's Urgent Request letter to the council
2. Singulars/Plurals

Warmly,
Tomslin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240605/9bd78610/attachment.htm>

From pedrodeperdigaolana at gmail.com  Wed Jun  5 19:44:00 2024
From: pedrodeperdigaolana at gmail.com (=?UTF-8?Q?Pedro_de_Perdig=C3=A3o_Lana?=)
Date: Wed, 5 Jun 2024 13:44:00 -0300
Subject: [NCSG-EC] [NCUC-EC] NomCom changes
In-Reply-To: <18b4ef3c-cc40-46f2-bb58-9f225718f684@Julf.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <491d2a86-1b99-41ec-8c3e-e6feeed33f43@julf.com>
 <CAJR4JuFBDoXi47rF+9cBh4iyTBF4hvjTcit+5+TpCZayfvgdAw@mail.gmail.com>
 <df81596f-3e26-4d5a-ac95-ca59064cfc24@Julf.com>
 <CAJR4JuEq=MrSM_n=cxhoddj5uMUwF0jxyX9yUx_P_fHNcZtSWQ@mail.gmail.com>
 <CAOMFwikCq0qSrL_7pC9bjeuOc3f1_K2VbYfGydC3t9WgfEPozg@mail.gmail.com>
 <18b4ef3c-cc40-46f2-bb58-9f225718f684@Julf.com>
Message-ID: <CAGSP6RQ=NtPV=Kq8QYHvhkawnTF6uKBVprPsuQTBaHvHEU0Nww@mail.gmail.com>

Hi,

I also got curious about the whole situation, so I went through transcripts
and the wiki. Here is a summary of the last relevant movements, which may
be useful for others:

Decision Reached
<https://community.icann.org/display/OR/Decisions+Reached+%7C+Action+Items%3A+Tracking+Tool>#87:

10 #87 <https://community.icann.org/x/xwEuCg>

23/09/2021

*The NomComRIWG considered its extensive efforts toward Rec. 10*, noting
that their proposed solution provided a streamlined approach as compared to
a more fundamental restructuring of the NomCom. Recognizing that the GNSO
continues to express strong opposition to the NomComRIWG proposal, rather
considering a more fundamental assessment of the NomCom as more
appropriate, the NomComRIWG plans to withdraw its proposed Bylaws changes
on Rec.10 rebalancing. This will help progress the package of proposed
Bylaws changes and other important implementation work.
There was a Webinar about it in mid-2022 (Closed Action Items
<https://community.icann.org/display/OR/Decisions+Reached+%7C+Action+Items%3A+Tracking+Tool>
):

127 #92 <https://community.icann.org/x/4oH3Cg>

10/02/2022
*ICANN73 Prep Week Webinar
<https://icann.zoom.us/rec/play/ljUiLGnJAFgDh-ObO9kka40ITzfxuvCAsUvxUv_jNtlhSzRnVJB_8O5FUXTkCjBtgpthLreSnxbWtMs.8ltosWFdyUaM_Pe1?canPlayFromShare=true&from=share_recording_detail&continueMode=true&componentName=rec-play&originRequestUrl=https%3A%2F%2Ficann.zoom.us%2Frec%2Fshare%2FpnqvveOxGt05WU5JqT6W5B7mI5VxuwYtdpkTAEtwOf4VrI0pYsszs76SsDA6zNgZ.GlFYZ6OZlV-WX6_H>*
Q&A Slides to be added in between agenda items.
Work plan slide to be added under agenda item 6.
Additional slide on Rec. 10 to be added.  NomCom Support Staff NA

23/02/2022

23/02/2022

Two people from the Non-Commercial were apparently responsible for Rec.10
in this Webinar
<https://community.icann.org/display/OR/Webinar+-+ICANN73+Prep+Week+NomCom+Review+Update+%7C+Thursday%2C+24+February+2022+ at +18%3A30+UTC>
(see 18m20 until 23m51 for a short summary of the reasoning behind the
decision), as per the Feb. 17th meeting
<https://community.icann.org/pages/viewpage.action?pageId=186780719>, but
the record shows Cheryl and Tom doing this part.

Maybe the most relevant explanation is in the transcripts of the September
23rd Meeting of 2021
<https://community.icann.org/pages/viewpage.action?pageId=170787271>, where
the above-mentioned decision was taken, in which only Remmy participated.
Cheryl said some interesting things there (there is a comment from her that
looks like a good summary of the whole thing "But because we thought we?d
leave the GNSO alone and give it as much absolute autonomy as possible, we
went down this particular and obviously failed and faulted pathway"). At
that meeting, however, it looks like the doors were already closed because
there was resistance from GNSO SGs *[it baffles me that the process was
planned in such a way that the opinion of those who benefitted from the
lack of balance determined the final decision]* and the OEC was, for some
reason, deeply against this change - this is a topic I think it is useful
to dig deeper to better understand what was going on. Another important
insight from the transcript is that they were not withdrawing the proposal
until the specific below, when Tom, who apparently wanted to proceed with
the Recommendation even if it had no chance of going through, had a change
of mind after a conversation between Cheryl and Larissa:

TOM BARRETT: Yes. I understand the optics more?so you?re saying the OEC
doesn?t want to make the decision. Absolutely. But we can certainly be open
to withdrawing our proposal for Rec 10. I want to know if I speak for
everyone. Can I have a thumbs up? Tracy, Jay, Dave, you all agree with
that? Cheryl and I do. Okay. All right, so that?s fine. Let?s go ahead and
withdraw the bylaw change for Rec 10. It?s just a matter of how we explain
our rationale for doing that.

There were apparently no votes against the withdrawal, but, as far as one
can understand from the documentation, the real battle was already lost in
the GNSO consultations

However, there were many indications through the documents and webinars
that the WG did not believe this ended the debate, so we may keep an eye up
for our next window of opportunity. I would already like to volunteer to
participate when the moment arrives.

Cordially,

*Pedro de Perdig?o Lana*
Lawyer <https://www.nic.br/>, GEDAI/UFPR <https://www.gedai.com.br/>
Researcher
PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
Board Member @ NCUC (ICANN) <https://www.ncuc.org/>, ISOC BR
<https://isoc.org.br/>, CC Brasil <https://br.creativecommons.net/> and IODA
<https://ioda.org.br/>
This message is restricted to the sender and recipient(s). If received by
mistake, please reply informing it.


Em qua., 5 de jun. de 2024 ?s 06:41, Johan Helsingius via NCUC-EC <
ncuc-ec at lists.ncuc.org> escreveu:

> Thanks Ines!
>
> There is a reference to a "transition article" (Article 27) that seems
> to be pretty crucial. Do you have any documents describing the
> transition article?
>
> I am also curious about the recommendation 10, "Representation on
> the NomCom should be rebalanced immediately and then be reviewed
> every 5 years." that was withdrawn. Can you help shed some light
> on the discussion that led to the withdrawal of the recommendation?
>
>         Julf
>
>
> On 05/06/2024 11:08, Hfaiedh Ines wrote:
> > Hi Julf
> >
> > Regarding membership I reached out to staff and here s the answer
> >
> > Hello Ines,
> >
> >
> > Thank you for reaching out - the work of the NomCom Review
> > Implementation Working Group (NomComRIWG) completed in June 2022, with
> > the submission of the final report
> > <
> https://www.icann.org/en/system/files/files/nomcom2-review-final-report-30jun22-en.pdf>.
> The ICANN Board took action on 16 March 2023 <
> https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-16-03-2023-en#section2.b>to
> accept the status of the NomCom2 Review implementation and initiate an
> ICANN Bylaws Amendment process. On 10 September 2023 <
> https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-10-09-2023-en#section2.b>the
> Board took action on next steps in Bylaws Amendment Process. If you would
> like more information, please feel free to review the NomCom Review
> workspace or reach out to me for further updates.
> >
> >
> > Thank you again for reaching out.
> >
> >
> > Basically the nomcom review team finshed their work in June 2022 so
> > exactly two years ago.
> >
> > To answer your question on NCSG or NCUC I  attached the final report
> > where there is no mention of either.  So we are speaking here of a board
> > resolution and my understanding is that they are leaving the floor open
> > to all constituencies to decide on how to proceed.
> >
> >
> > On Tue, Jun 4, 2024, 21:31 Benjamin Akinmoyeje <benakin at gmail.com
> > <mailto:benakin at gmail.com>> wrote:
> >
> >     I got your email. It was just that the GNSO chair , did not copy
> >     NCUC chair.
> >
> >
> >     That it is worthwhile noting for future, although in his email he
> >     made references to stakeholder group an constituencies.
> >
> >     I hope you see my point.
> >
> >     Kind regards,
> >     Benjamin
> >
> >
> >
> >
> >     On Tue, Jun 4, 2024, 9:35?PM Johan Helsingius <julf at julf.com
> >     <mailto:julf at julf.com>> wrote:
> >
> >         I did copy ncuc-ec, assuming the chair would be part of it.
> >
> >                  Julf
> >
> >         On 04/06/2024 18:59, Benjamin Akinmoyeje wrote:
> >          >    Hi Julf,
> >          > Thank you for this email....but it is strange that the GNSO
> >         chair has
> >          > chosen not to copy the  NCUC Chair in this email.
> >          >
> >          > NCUC appointed Pascal, our current Nomcom representative if I
> >         am correct.
> >          >
> >          > It would be great if the GNSO chair could be pointed to this
> >         omission.
> >          >
> >          > Just checking if things have changed.
> >          >
> >          >
> >          > Kind regards,
> >          > Benjamin
> >          >
> >          > On Sat, Jun 1, 2024 at 9:32?AM Johan Helsingius
> >         <julf at julf.com <mailto:julf at julf.com>
> >          > <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
> >          >
> >          >
> >          >
> >          >
> >          >     -------- Forwarded Message --------
> >          >     Subject:        NomCom changes
> >          >     Date:   Fri, 31 May 2024 14:41:19 +0000
> >          >     From:   DiBiase, Gregory <dibiase at amazon.com
> >         <mailto:dibiase at amazon.com>
> >          >     <mailto:dibiase at amazon.com <mailto:dibiase at amazon.com>>>
> >          >     To: aheineman at godaddy.com <mailto:aheineman at godaddy.com>
> >         <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>
> >          >     <aheineman at godaddy.com <mailto:aheineman at godaddy.com>
> >         <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>>,
> >         Lori Schulman
> >          >     <lschulman at inta.org <mailto:lschulman at inta.org>
> >         <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>>, Cole,
> >         Mason (POR)
> >          >     <MCole at perkinscoie.com <mailto:MCole at perkinscoie.com>
> >         <mailto:MCole at perkinscoie.com <mailto:MCole at perkinscoie.com>>>,
> >         Johan
> >          >     Helsingius <julf at Julf.com>, sdemetriou at verisign.com
> >         <mailto:sdemetriou at verisign.com>
> >          >     <mailto:sdemetriou at verisign.com
> >         <mailto:sdemetriou at verisign.com>>
> >          >     <sdemetriou at verisign.com <mailto:sdemetriou at verisign.com>
> >         <mailto:sdemetriou at verisign.com <mailto:sdemetriou at verisign.com
> >>>,
> >          > philippe.fouquart at orange.com
> >         <mailto:philippe.fouquart at orange.com>
> >         <mailto:philippe.fouquart at orange.com
> >         <mailto:philippe.fouquart at orange.com>>
> >          >     <philippe.fouquart at orange.com
> >         <mailto:philippe.fouquart at orange.com>
> >         <mailto:philippe.fouquart at orange.com
> >         <mailto:philippe.fouquart at orange.com>>>
> >          >     CC:     Steve Chan <steve.chan at icann.org
> >         <mailto:steve.chan at icann.org>
> >          >     <mailto:steve.chan at icann.org
> >         <mailto:steve.chan at icann.org>>>, gnso-secs at icann.org
> >         <mailto:gnso-secs at icann.org>
> >          >     <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
> >          >     <gnso-secs at icann.org <mailto:gnso-secs at icann.org>
> >         <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>>
> >          >
> >          >
> >          >
> >          >     Dear Ashley, Julf, Lori, Mason, Philippe, and Samantha,
> >          >
> >          >     I am writing to you all in your roles as Chairs of
> >         Stakeholder
> >          >     Groups or
> >          >     Constituencies that appoint delegates to ICANN?s
> >         Nominating Committee
> >          >     (NomCom).
> >          >
> >          >     You may recall that the NomCom2 Review produced 27
> >         recommendations,
> >          >     several of which relate to the composition and terms of
> >         the NomCom. In
> >          >     order to effectuate these particular recommendations, the
> >         ICANN Board
> >          >     approved Standard Bylaws Amendments in Articles 8, 12,
> >         and 27.
> >          >
> >          >     The Bylaws amendments made no change to the number and
> >         nature of
> >          >     delegates from the GNSO (i.e., 1 each from the RySG,
> >         RrSG, ISPCP, IPC,
> >          >     NCSG, and 2 from the BC), though the length of terms were
> >         extended to
> >          >     two years (see Section 8.3 of the Bylaws). However, from
> >         Article 27, in
> >          >     order to, ?effectuate the introduction of the two-year
> >         terms and
> >          >     support
> >          >     the goal of staggering delegate terms??, three of the
> >         GNSO delegates
> >          >     shall serve a one-year term. ARTICLE 27 TRANSITION
> >         ARTICLE states that
> >          >     the GNSO is responsible for determining which three of
> >         the seven
> >          >     delegates shall initially serve one-year terms.
> >          >
> >          >     Unfortunately, no guidance was provided on how to
> >         identify the three of
> >          >     seven GNSO delegates to serve one-year terms. For
> >         reference, the ALAC
> >          >     was also in the position of having to identify a subset
> >         of delegates to
> >          >     serve one-year terms. They elected to rely on random
> >         selection during a
> >          >     live call.
> >          >
> >          >     The GNSO may want to rely on a similarly simple approach.
> >         An important
> >          >     point in considering the approach is that the level of
> >          >     representation on
> >          >     the NomCom is not affected by the term-length. However,
> >         the SG/Cs with
> >          >     one-year terms will have to replace those delegates after
> >         one year
> >          >     rather than two.
> >          >
> >          >     *Question: Do you believe there would be any objections
> >         from your
> >          >     groups, and potentially delegates that you have already
> >         identified, to
> >          >     proceeding with a simple path forward in which we
> >         randomly select three
> >          >     of seven GNSO delegates to serve one-year terms?*
> >          >
> >          >     If you believe that there may be concerns (e.g., we may
> >         want to avoid
> >          >     having the one-year terms concentrated in particular
> >         areas), please
> >          >     share them with Council leadership no later than 31 May
> 2024.
> >          >
> >          >     If however there are no concerns, Council leadership can
> >         perform the
> >          >     random selection process with staff or if you prefer, on
> >         a Zoom call
> >          >     with all of you.
> >          >
> >          >     Thanks,
> >          >
> >          >     Greg DiBiase, GNSO Chair
> >          >
> >
> >     _______________________________________________
> >     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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240605/b0fb8b1d/attachment.htm>

From julf at Julf.com  Wed Jun  5 21:39:11 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 5 Jun 2024 20:39:11 +0200
Subject: [NCSG-EC] [NCUC-EC] NomCom changes
In-Reply-To: <CAGSP6RQ=NtPV=Kq8QYHvhkawnTF6uKBVprPsuQTBaHvHEU0Nww@mail.gmail.com>
References: <c98b1bec82dd4d599bed292064f0711c@amazon.com>
 <491d2a86-1b99-41ec-8c3e-e6feeed33f43@julf.com>
 <CAJR4JuFBDoXi47rF+9cBh4iyTBF4hvjTcit+5+TpCZayfvgdAw@mail.gmail.com>
 <df81596f-3e26-4d5a-ac95-ca59064cfc24@Julf.com>
 <CAJR4JuEq=MrSM_n=cxhoddj5uMUwF0jxyX9yUx_P_fHNcZtSWQ@mail.gmail.com>
 <CAOMFwikCq0qSrL_7pC9bjeuOc3f1_K2VbYfGydC3t9WgfEPozg@mail.gmail.com>
 <18b4ef3c-cc40-46f2-bb58-9f225718f684@Julf.com>
 <CAGSP6RQ=NtPV=Kq8QYHvhkawnTF6uKBVprPsuQTBaHvHEU0Nww@mail.gmail.com>
Message-ID: <782e7fcf-dd2d-4ead-add2-1af7b0a480f4@Julf.com>

On 05/06/2024 18:44, Pedro de Perdig?o Lana wrote:
> I also got curious about the whole situation, so I went through 
> transcripts and the wiki. Here is a summary of the last relevant 
> movements, which may be useful for others:

Thank you - very helpful!

> There were apparently no votes against the withdrawal, but, as far as 
> one can understand from the documentation, the real battle was already 
> lost in the GNSO consultations

So we failed on two points - both in Council (and corridor discussions)
where we failed to convince the CPH to support us, and in the working
group vote.

> However, there were many indications through the documents and webinars 
> that the WG did not believe this ended the debate, so we may keep an eye 
> up for our next window of opportunity. I would already like to volunteer 
> to participate when the moment arrives.

Problem is that nobody wants to revisit the issues now that
implementation has progressed this far. We do have the (passive)
support of the CPH now, and the Board is not against it but
as usual punts it to a "community decision". NomCom review 3
is far away in the future, and all eyes are on the holistic
review.

	Julf



From farzaneh.badii at gmail.com  Thu Jun  6 06:14:45 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Wed, 5 Jun 2024 23:14:45 -0400
Subject: [NCSG-EC] We fixed one issue
Message-ID: <CAN1qJvAJKCavSP3DqN1xB+KaLF2PyGj1QJ0XDPLpDkmpfH2x+A@mail.gmail.com>

Hello EC,

I am thrilled to tell you that we can now see both individuals and
organizations statements when clicking on the view button. This was not the
case for organizations which was a headache. And we got it done for free!

Please from time to time try and test the form. We need to gradually fix
these issues.


Farzaneh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240605/71eb810b/attachment.htm>

From muyiwacaleb at gmail.com  Thu Jun  6 08:22:36 2024
From: muyiwacaleb at gmail.com (Caleb Olumuyiwa Ogundele)
Date: Thu, 6 Jun 2024 00:22:36 -0500
Subject: [NCSG-EC] We fixed one issue
In-Reply-To: <CAN1qJvAJKCavSP3DqN1xB+KaLF2PyGj1QJ0XDPLpDkmpfH2x+A@mail.gmail.com>
References: <CAN1qJvAJKCavSP3DqN1xB+KaLF2PyGj1QJ0XDPLpDkmpfH2x+A@mail.gmail.com>
Message-ID: <CAL_ZvK7TY2cwxwjOv4L2iPzq70cn_uuAMDM7iDaAXVWXWQrvXw@mail.gmail.com>

Thank you for taking the lead on this Farzii

On Wed, Jun 5, 2024, 10:15?PM farzaneh badii via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Hello EC,
>
> I am thrilled to tell you that we can now see both individuals and
> organizations statements when clicking on the view button. This was not the
> case for organizations which was a headache. And we got it done for free!
>
> Please from time to time try and test the form. We need to gradually fix
> these issues.
>
>
> Farzaneh
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240606/bf0331d0/attachment.htm>

From farzaneh.badii at gmail.com  Thu Jun  6 08:26:31 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Thu, 6 Jun 2024 01:26:31 -0400
Subject: [NCSG-EC] We fixed one issue
In-Reply-To: <CAL_ZvK7TY2cwxwjOv4L2iPzq70cn_uuAMDM7iDaAXVWXWQrvXw@mail.gmail.com>
References: <CAN1qJvAJKCavSP3DqN1xB+KaLF2PyGj1QJ0XDPLpDkmpfH2x+A@mail.gmail.com>
 <CAL_ZvK7TY2cwxwjOv4L2iPzq70cn_uuAMDM7iDaAXVWXWQrvXw@mail.gmail.com>
Message-ID: <CAN1qJvCcmLBD8zXmWsRCkfaZHnPoK8PkKvEuw-axUydN4WDYsQ@mail.gmail.com>

Thank you too Caleb! We did it together, thanks for attending the calls
too.


Farzaneh


On Thu, Jun 6, 2024 at 1:22?AM Caleb Olumuyiwa Ogundele <
muyiwacaleb at gmail.com> wrote:

> Thank you for taking the lead on this Farzii
>
> On Wed, Jun 5, 2024, 10:15?PM farzaneh badii via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
>> Hello EC,
>>
>> I am thrilled to tell you that we can now see both individuals and
>> organizations statements when clicking on the view button. This was not the
>> case for organizations which was a headache. And we got it done for free!
>>
>> Please from time to time try and test the form. We need to gradually fix
>> these issues.
>>
>>
>> Farzaneh
>>
> _______________________________________________
>> NCSG-EC mailing list
>> NCSG-EC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240606/11c93a41/attachment.htm>

From julf at julf.com  Thu Jun  6 11:51:08 2024
From: julf at julf.com (Johan Helsingius)
Date: Thu, 6 Jun 2024 10:51:08 +0200
Subject: [NCSG-EC] We fixed one issue
In-Reply-To: <CAN1qJvCcmLBD8zXmWsRCkfaZHnPoK8PkKvEuw-axUydN4WDYsQ@mail.gmail.com>
References: <CAN1qJvAJKCavSP3DqN1xB+KaLF2PyGj1QJ0XDPLpDkmpfH2x+A@mail.gmail.com>
 <CAL_ZvK7TY2cwxwjOv4L2iPzq70cn_uuAMDM7iDaAXVWXWQrvXw@mail.gmail.com>
 <CAN1qJvCcmLBD8zXmWsRCkfaZHnPoK8PkKvEuw-axUydN4WDYsQ@mail.gmail.com>
Message-ID: <6265a213-f1de-4bf1-a6be-088684cf1023@julf.com>

Thank you both!!

	Julf


On 06/06/2024 07:26, farzaneh badii via NCSG-EC wrote:
> Thank you too Caleb! We did it together, thanks for attending the calls 
> too.
> 
> 
> Farzaneh
> 
> 
> On Thu, Jun 6, 2024 at 1:22?AM Caleb Olumuyiwa Ogundele 
> <muyiwacaleb at gmail.com <mailto:muyiwacaleb at gmail.com>> wrote:
> 
>     Thank you for taking the lead?on this Farzii
> 
>     On Wed, Jun 5, 2024, 10:15?PM farzaneh badii via NCSG-EC
>     <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> 
>         Hello EC,
> 
>         I am thrilled to tell you that we can now see both individuals
>         and organizations statements when clicking on the view button.
>         This was not the case for organizations which was a headache.
>         And we got it done for free!
> 
>         Please from time to time try and test the form. We need to
>         gradually fix these issues.
> 
> 
>         Farzaneh 
> 
>         _______________________________________________
>         NCSG-EC mailing list
>         NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>         https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>         <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> 
> 
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec


From andrea.glandon at icann.org  Thu Jun  6 18:30:35 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Thu, 6 Jun 2024 15:30:35 +0000
Subject: [NCSG-EC] Agenda-ICANN NCPH Membership Session
In-Reply-To: <D6678324-231B-46B4-A462-A771F420CB4C@icann.org>
References: <D6678324-231B-46B4-A462-A771F420CB4C@icann.org>
Message-ID: <A96FADFA-9A54-417C-B0C0-3E7C9CC12E9C@icann.org>

Hello all!

Just sending the agenda around again for folks to take a look. This session is 90 minutes long.

Thanks!
Kind Regards,
Andrea


From: Andrea Glandon <andrea.glandon at icann.org>
Date: Tuesday, May 14, 2024 at 12:40
To: "csg-excomm at icann.org" <csg-excomm at icann.org>, "ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>
Cc: Andrea Glandon <andrea.glandon at icann.org>, Brenda Brewer <brenda.brewer at icann.org>
Subject: Agenda-ICANN NCPH Membership Session

Hello all,

It?s time to start working on  the agenda for ICANN80. Please find below a link for the NCPH Membership session. The schedule will be available on Monday, 20 May 2024.

NCPH Membership Session<https://docs.google.com/document/d/1_ez9vaJwX6VIliX-xN36Uv0mrbAur4s0imuNym7RT2o/edit?usp=sharing>

Thanks!
Andrea Glandon
Policy Operations Coordinator
Internet Corporation for Assigned Names and Numbers (ICANN)
Skype ID:  acglandon76



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240606/639f33aa/attachment.htm>

From julf at Julf.com  Fri Jun  7 10:42:11 2024
From: julf at Julf.com (Johan Helsingius)
Date: Fri, 7 Jun 2024 09:42:11 +0200
Subject: [NCSG-EC] Welcome Rafik
Message-ID: <93e8815f-4af4-4c24-993d-132908983807@Julf.com>

In order to facilitate a smooth transition, I have added
Rafik to the EC mailing list. Welcome, Rafik!

	Julf


From muyiwacaleb at gmail.com  Fri Jun  7 13:26:09 2024
From: muyiwacaleb at gmail.com (Caleb Olumuyiwa Ogundele)
Date: Fri, 7 Jun 2024 05:26:09 -0500
Subject: [NCSG-EC] Welcome Rafik
In-Reply-To: <93e8815f-4af4-4c24-993d-132908983807@Julf.com>
References: <93e8815f-4af4-4c24-993d-132908983807@Julf.com>
Message-ID: <CAL_ZvK4VuJwbFoQN7LrOMAW11PH4oObbzCwX7tU1wPezCbg2ag@mail.gmail.com>

Welcome on board

On Fri, Jun 7, 2024, 2:42?AM Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> In order to facilitate a smooth transition, I have added
> Rafik to the EC mailing list. Welcome, Rafik!
>
>         Julf
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240607/5768e4e3/attachment.htm>

From rafik.dammak at gmail.com  Sat Jun  8 03:22:38 2024
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Sat, 8 Jun 2024 09:22:38 +0900
Subject: [NCSG-EC] Welcome Rafik
In-Reply-To: <93e8815f-4af4-4c24-993d-132908983807@Julf.com>
References: <93e8815f-4af4-4c24-993d-132908983807@Julf.com>
Message-ID: <CAH5sThmhNO8ViryngNMt8BtK4rempurc5jiC-XoGaYta8uh3Yg@mail.gmail.com>

Thanks Julf and everyone, looking forward  the transition  in coming months.

Rafik

On Fri, Jun 7, 2024, 16:42 Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> In order to facilitate a smooth transition, I have added
> Rafik to the EC mailing list. Welcome, Rafik!
>
>         Julf
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240608/3e6c2c5a/attachment.htm>

From julf at julf.com  Tue Jun 11 12:11:00 2024
From: julf at julf.com (Johan Helsingius)
Date: Tue, 11 Jun 2024 11:11:00 +0200
Subject: [NCSG-EC] NCPH session Wednesday, 12 June 10:45-12:15
Message-ID: <ccabb864-1027-4b3b-bc2d-a4d24317df52@julf.com>

Just a reminder that we have the NCPH session on Wednesday.

The agenda is here:

https://docs.google.com/document/d/1_ez9vaJwX6VIliX-xN36Uv0mrbAur4s0imuNym7RT2o/

We should at least have the EC members present, but it would be
good to have PC members there too. In particular, we need the
Team 14 members and people familiar with the IPC Request for
Reconsideration to be in the room.

	Julf


From philippe.fouquart at orange.com  Tue Jun 11 21:10:40 2024
From: philippe.fouquart at orange.com (philippe.fouquart at orange.com)
Date: Tue, 11 Jun 2024 18:10:40 +0000
Subject: [NCSG-EC] Agenda-ICANN NCPH Membership Session
In-Reply-To: <A96FADFA-9A54-417C-B0C0-3E7C9CC12E9C@icann.org>
References: <D6678324-231B-46B4-A462-A771F420CB4C@icann.org>
 <A96FADFA-9A54-417C-B0C0-3E7C9CC12E9C@icann.org>
Message-ID: <PAVPR02MB9961D3929AE9E223411A619785C72@PAVPR02MB9961.eurprd02.prod.outlook.com>

Hi Julf, everyone,

Again apologies for not making the meeting tomorrow. One additional item that you may want to address is consideration for a day 0 at the next icann meeting in lieu of an intersessional.

Regards,
Philippe





Orange Restricted

________________________________
From: Csg-excomm <csg-excomm-bounces at icann.org> on behalf of Andrea Glandon via Csg-excomm <csg-excomm at icann.org>
Sent: Thursday, June 6, 2024 5:30:35 PM
To: csg-excomm at icann.org <csg-excomm at icann.org>; ncsg-ec at lists.ncsg.is <ncsg-ec at lists.ncsg.is>
Subject: Re: [Csg-excomm] Agenda-ICANN NCPH Membership Session

CAUTION : This email originated outside the company. Do not click on any links or open attachments unless you are expecting them from the sender.
ATTENTION : Cet e-mail provient de l'ext?rieur de l'entreprise. Ne cliquez pas sur les liens ou n'ouvrez pas les pi?ces jointes ? moins de connaitre l'exp?diteur.



Hello all!



Just sending the agenda around again for folks to take a look. This session is 90 minutes long.



Thanks!

Kind Regards,

Andrea





From: Andrea Glandon <andrea.glandon at icann.org>
Date: Tuesday, May 14, 2024 at 12:40
To: "csg-excomm at icann.org" <csg-excomm at icann.org>, "ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>
Cc: Andrea Glandon <andrea.glandon at icann.org>, Brenda Brewer <brenda.brewer at icann.org>
Subject: Agenda-ICANN NCPH Membership Session



Hello all,



It?s time to start working on  the agenda for ICANN80. Please find below a link for the NCPH Membership session. The schedule will be available on Monday, 20 May 2024.



NCPH Membership Session<https://docs.google.com/document/d/1_ez9vaJwX6VIliX-xN36Uv0mrbAur4s0imuNym7RT2o/edit?usp=sharing>



Thanks!

Andrea Glandon

Policy Operations Coordinator

Internet Corporation for Assigned Names and Numbers (ICANN)

Skype ID:  acglandon76






____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240611/c2439bea/attachment.htm>

From julf at julf.com  Wed Jun 12 10:46:59 2024
From: julf at julf.com (Johan Helsingius)
Date: Wed, 12 Jun 2024 09:46:59 +0200
Subject: [NCSG-EC] Agenda-ICANN NCPH Membership Session
In-Reply-To: <PAVPR02MB9961D3929AE9E223411A619785C72@PAVPR02MB9961.eurprd02.prod.outlook.com>
References: <D6678324-231B-46B4-A462-A771F420CB4C@icann.org>
 <A96FADFA-9A54-417C-B0C0-3E7C9CC12E9C@icann.org>
 <PAVPR02MB9961D3929AE9E223411A619785C72@PAVPR02MB9961.eurprd02.prod.outlook.com>
Message-ID: <ad41b300-43cb-4115-8ca3-e856be56a227@julf.com>

Noted! Thanks!

	Julf


On 11/06/2024 20:10, philippe.fouquart--- via NCSG-EC wrote:
> Hi Julf, everyone,
> 
> Again apologies for not making the meeting tomorrow. One additional item 
> that you may want to address is consideration for a day 0 at the next 
> icann meeting in lieu of an intersessional.
> 
> Regards,
> Philippe
> 
> 
> 
> 
> Orange Restricted
> 
> ------------------------------------------------------------------------
> *From:* Csg-excomm <csg-excomm-bounces at icann.org> on behalf of Andrea 
> Glandon via Csg-excomm <csg-excomm at icann.org>
> *Sent:* Thursday, June 6, 2024 5:30:35 PM
> *To:* csg-excomm at icann.org <csg-excomm at icann.org>; ncsg-ec at lists.ncsg.is 
> <ncsg-ec at lists.ncsg.is>
> *Subject:* Re: [Csg-excomm] Agenda-ICANN NCPH Membership Session
> *CAUTION* : This email originated outside the company. Do not click on 
> any links or open attachments unless you are expecting them from the 
> sender.
> *ATTENTION* : Cet e-mail provient de l'ext?rieur de l'entreprise. Ne 
> cliquez pas sur les liens ou n'ouvrez pas les pi?ces jointes ? moins de 
> connaitre l'exp?diteur.
> 
> 
> 
> Hello all!
> 
> Just sending the agenda around again for folks to take a look. This 
> session is 90 minutes long.
> 
> Thanks!
> 
> Kind Regards,
> 
> Andrea
> 
> *From: *Andrea Glandon <andrea.glandon at icann.org>
> *Date: *Tuesday, May 14, 2024 at 12:40
> *To: *"csg-excomm at icann.org" <csg-excomm at icann.org>, 
> "ncsg-ec at lists.ncsg.is" <ncsg-ec at lists.ncsg.is>
> *Cc: *Andrea Glandon <andrea.glandon at icann.org>, Brenda Brewer 
> <brenda.brewer at icann.org>
> *Subject: *Agenda-ICANN NCPH Membership Session
> 
> Hello all,
> 
> It?s time to start working on? the agenda for ICANN80. Please find below 
> a link for the NCPH Membership session. The schedule will be available 
> on Monday, 20 May 2024.
> 
> NCPH Membership Session 
> <https://docs.google.com/document/d/1_ez9vaJwX6VIliX-xN36Uv0mrbAur4s0imuNym7RT2o/edit?usp=sharing>
> 
> Thanks!
> 
> *Andrea Glandon*
> 
> Policy Operations Coordinator
> 
> Internet Corporation for Assigned Names and Numbers (ICANN)
> 
> *Skype ID:*? acglandon76
> 
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 
> 
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec


From andrea.glandon at icann.org  Wed Jun 12 15:01:29 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Wed, 12 Jun 2024 12:01:29 +0000
Subject: [NCSG-EC] REMINDER-ICANN80 NCSG EC Sign-up Room
Message-ID: <7eba67c8f3174236a08ecfb9dd5e5b0f@icann.org>

Dear all,

Your ICANN80 sign-up room has been scheduled with the following information.

Title: NCSG EC
Date: Thurday, 13 June 2024
Time: 13:45 ? 15:00 CAT
Room: AD1

IMPORTANT NOTE:

NO AUDIO VISUAL OR TECHNICAL SERVICES ARE AVAILABLE FOR SIGN-UP ROOMS.

No projection, microphones, audio system phone calls, or technical assistance is available for this meeting.

To get these services in the future, a session request must be submitted in advance of the ICANN meeting.

Thank you.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240612/673a03b0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 1806 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240612/673a03b0/attachment.ics>

From julf at Julf.com  Sat Jun 15 14:31:33 2024
From: julf at Julf.com (Johan Helsingius)
Date: Sat, 15 Jun 2024 13:31:33 +0200
Subject: [NCSG-EC] Fwd: ICANN81 Block Schedule, Production Timeline
In-Reply-To: <F5145518-D39A-42C2-910C-9DE778A8AE07@icann.org>
References: <F5145518-D39A-42C2-910C-9DE778A8AE07@icann.org>
Message-ID: <8f18ce87-c963-4510-9b9d-09001f363242@Julf.com>

FYI

	Julf

-------- Forwarded Message --------
Subject: 	[SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Block Schedule, 
Production Timeline
From: 	Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning 
<soac-leaders-icannmeeting-planning at icann.org>
Reply-To: 	Nathalie Peregrine <nathalie.peregrine at icann.org>
To: 	soac-leaders-icannmeeting-planning at icann.org 
<soac-leaders-icannmeeting-planning at icann.org>



Dear all,

Whilst you are all busy planning for ICANN80, staff support thought it 
might be helpful for you to have access to the ICANN81 draft block 
schedule and production timeline ahead of time. ICANN81 will take place 
in Istanbul from the 9 ? 14 November 2024.

As most of you know, planning for an ICANN meeting would traditionally 
start at the end of the previous ICANN meeting for the next one. There 
are many benefits to starting planning earlier, this allows for more 
discussions about topics, new session formats and ought to make outreach 
and engagement efforts easier.

Holding ICANN81 Production Calls prior to ICANN80 may be confusing, but 
having access to a proposed block schedule and production timeline could 
trigger discussions within your own groups but also on this ICANN 
meeting planning mailing list. It may also assist with session agenda 
planning for ICANN80.

Please bear in mind the following:

   * The draft block schedule follows a thought process stemming from
     what worked at previous AGMs and equally other ICANN meetings. It
     can however be modified and tweaked according to your collective input
   * The production timeline shows an estimate of the deadlines by which
     scheduling steps should have taken place. If we can be ahead of the
     production timeline (for instance, the sharing of the block schedule
     and timeline before ICANN80), this will free up more Production Call
     time for discussion.

Please do not hesitate to provide your input here, your questions, your 
ideas for ICANN81.

We look forward to working with you on the AGM!

Kind regards,

The Schedule Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN81 Production Timeline.pdf
Type: application/pdf
Size: 75225 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240615/3b3259dc/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN81- AGM Istanbul DRAFT v.1 15 May 2024 - Sheet1.pdf
Type: application/pdf
Size: 57478 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240615/3b3259dc/attachment-0001.pdf>

From stephanie.perrin at mail.utoronto.ca  Sat Jun 15 14:58:06 2024
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Sat, 15 Jun 2024 11:58:06 +0000
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 Block Schedule,
 Production Timeline
In-Reply-To: <8f18ce87-c963-4510-9b9d-09001f363242@Julf.com>
References: <F5145518-D39A-42C2-910C-9DE778A8AE07@icann.org>
 <8f18ce87-c963-4510-9b9d-09001f363242@Julf.com>
Message-ID: <987705AC-E42F-4692-8CC9-AF6122C8C323@mail.utoronto.ca>

We should focus on this at the next pc meeting.  in the meantime, get the request for a day zero meeting for NCPH  submitted.  Manju convinced me that additional travel fir a short ncph  meeting was a pain.  Plus this meeting maximizes the presence of our councillors because of transition
Stephanie

Sent from my iPhone

> On Jun 15, 2024, at 07:32, Johan Helsingius via NCSG-PC <ncsg-pc at lists.ncsg.is> wrote:
> 
> ?FYI
> 
>    Julf
> 
> -------- Forwarded Message --------
> Subject:    [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Block Schedule, Production Timeline
> From:    Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning at icann.org>
> Reply-To:    Nathalie Peregrine <nathalie.peregrine at icann.org>
> To:    soac-leaders-icannmeeting-planning at icann.org <soac-leaders-icannmeeting-planning at icann.org>
> 
> 
> 
> Dear all,
> 
> Whilst you are all busy planning for ICANN80, staff support thought it might be helpful for you to have access to the ICANN81 draft block schedule and production timeline ahead of time. ICANN81 will take place in Istanbul from the 9 ? 14 November 2024.
> 
> As most of you know, planning for an ICANN meeting would traditionally start at the end of the previous ICANN meeting for the next one. There are many benefits to starting planning earlier, this allows for more discussions about topics, new session formats and ought to make outreach and engagement efforts easier.
> 
> Holding ICANN81 Production Calls prior to ICANN80 may be confusing, but having access to a proposed block schedule and production timeline could trigger discussions within your own groups but also on this ICANN meeting planning mailing list. It may also assist with session agenda planning for ICANN80.
> 
> Please bear in mind the following:
> 
>  * The draft block schedule follows a thought process stemming from
>    what worked at previous AGMs and equally other ICANN meetings. It
>    can however be modified and tweaked according to your collective input
>  * The production timeline shows an estimate of the deadlines by which
>    scheduling steps should have taken place. If we can be ahead of the
>    production timeline (for instance, the sharing of the block schedule
>    and timeline before ICANN80), this will free up more Production Call
>    time for discussion.
> 
> Please do not hesitate to provide your input here, your questions, your ideas for ICANN81.
> 
> We look forward to working with you on the AGM!
> 
> Kind regards,
> 
> The Schedule Team
> <ICANN81 Production Timeline.pdf>
> <ICANN81- AGM Istanbul DRAFT v.1 15 May 2024 - Sheet1.pdf>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc

From julf at Julf.com  Tue Jun 18 17:31:41 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 18 Jun 2024 16:31:41 +0200
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 Block Schedule,
 Production Timeline
In-Reply-To: <987705AC-E42F-4692-8CC9-AF6122C8C323@mail.utoronto.ca>
References: <F5145518-D39A-42C2-910C-9DE778A8AE07@icann.org>
 <8f18ce87-c963-4510-9b9d-09001f363242@Julf.com>
 <987705AC-E42F-4692-8CC9-AF6122C8C323@mail.utoronto.ca>
Message-ID: <2e116845-c881-41b9-b6f6-9720f335430b@Julf.com>

We are on the case!

	Julf

On 15/06/2024 13:58, Stephanie Perrin wrote:
> We should focus on this at the next pc meeting.  in the meantime, get the request for a day zero meeting for NCPH  submitted.  Manju convinced me that additional travel fir a short ncph  meeting was a pain.  Plus this meeting maximizes the presence of our councillors because of transition
> Stephanie
> 
> Sent from my iPhone
> 
>> On Jun 15, 2024, at 07:32, Johan Helsingius via NCSG-PC <ncsg-pc at lists.ncsg.is> wrote:
>>
>> ?FYI
>>
>>     Julf
>>
>> -------- Forwarded Message --------
>> Subject:    [SOAC-Leaders-ICANNMeeting-Planning] ICANN81 Block Schedule, Production Timeline
>> From:    Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning at icann.org>
>> Reply-To:    Nathalie Peregrine <nathalie.peregrine at icann.org>
>> To:    soac-leaders-icannmeeting-planning at icann.org <soac-leaders-icannmeeting-planning at icann.org>
>>
>>
>>
>> Dear all,
>>
>> Whilst you are all busy planning for ICANN80, staff support thought it might be helpful for you to have access to the ICANN81 draft block schedule and production timeline ahead of time. ICANN81 will take place in Istanbul from the 9 ? 14 November 2024.
>>
>> As most of you know, planning for an ICANN meeting would traditionally start at the end of the previous ICANN meeting for the next one. There are many benefits to starting planning earlier, this allows for more discussions about topics, new session formats and ought to make outreach and engagement efforts easier.
>>
>> Holding ICANN81 Production Calls prior to ICANN80 may be confusing, but having access to a proposed block schedule and production timeline could trigger discussions within your own groups but also on this ICANN meeting planning mailing list. It may also assist with session agenda planning for ICANN80.
>>
>> Please bear in mind the following:
>>
>>   * The draft block schedule follows a thought process stemming from
>>     what worked at previous AGMs and equally other ICANN meetings. It
>>     can however be modified and tweaked according to your collective input
>>   * The production timeline shows an estimate of the deadlines by which
>>     scheduling steps should have taken place. If we can be ahead of the
>>     production timeline (for instance, the sharing of the block schedule
>>     and timeline before ICANN80), this will free up more Production Call
>>     time for discussion.
>>
>> Please do not hesitate to provide your input here, your questions, your ideas for ICANN81.
>>
>> We look forward to working with you on the AGM!
>>
>> Kind regards,
>>
>> The Schedule Team
>> <ICANN81 Production Timeline.pdf>
>> <ICANN81- AGM Istanbul DRAFT v.1 15 May 2024 - Sheet1.pdf>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc


From julf at Julf.com  Thu Jun 20 18:02:04 2024
From: julf at Julf.com (Johan Helsingius)
Date: Thu, 20 Jun 2024 17:02:04 +0200
Subject: [NCSG-EC] Fwd: ICANN81 | Istanbul | Supported Travelers Database
 Due | Thursday, 11 July 2024
In-Reply-To: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
Message-ID: <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>

Here we go again...

Please let me know if you intend to be in Istanbul in person or not.

	Julf



-------- Forwarded Message --------
Subject: 	ICANN81 | Istanbul | Supported Travelers Database Due | 
Thursday, 11 July 2024
Date: 	Thu, 20 Jun 2024 14:02:02 +0000
From: 	Terri Agnew <terri.agnew at icann.org>
To: 	julf at julf.com <julf at julf.com>, jumaropi at yahoo.com 
<jumaropi at yahoo.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>, John McElwaine 
<john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
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>



Dear all,

In order to service your travel needs for ICANN81Istanbulin a timely 
fashion, please submit your meeting database tognso-secs at icann.org 
<mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important 
all funded travel air booking is completed by due date given in ICANN 
Travel emails.

Please share with all funded travelers, the travel support guidelines 
wiki space: https://community.icann.org/x/lgvxAg 
<https://community.icann.org/x/lgvxAg> and highlight the communications 
responsibilities section:

ICANN Travel Support attempts to reach a supported traveler four times 
before deeming the supported traveler unresponsive:

  1. ICANN Travel Support sends ?welcome email.?
  2. If there is no response after seven business days, ICANN Travel
     Support sends a second email, copying ICANN support staff.
  3. If there is no response five business days after the second email,
     ICANN Travel Support sends a third email, copying ICANN support
     staff and the community group chair.
  4. If there is no response five business days after the third email,
     ICANN Travel Support sends a fourth email, copying ICANN support
     staff and the community group chair.

If there is no response three days after the fourth attempt to reach the 
supported traveler, the community group may substitute another traveler.

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, 08 November *

	

*Friday, 15 November*

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.

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.Follow link here 
<https://community.icann.org/x/fSfxAg> for assistance.

3.Wednesday, 25 September 2024*(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
     <mailto: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.

Kind regards,

Terri

Policy Team Supporting the GNSO



From bruna.mrtns at gmail.com  Thu Jun 20 18:06:14 2024
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Thu, 20 Jun 2024 17:06:14 +0200
Subject: [NCSG-EC] Fwd: ICANN81 | Istanbul | Supported Travelers
 Database Due | Thursday, 11 July 2024
In-Reply-To: <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
Message-ID: <CADAEEV0Ppw-V2FzP+qT+S_nF9btvK7wgQc3BL_rdvgW_wEZBcA@mail.gmail.com>

Am coming !

On Thu, Jun 20, 2024 at 5:02?PM Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Here we go again...
>
> Please let me know if you intend to be in Istanbul in person or not.
>
>         Julf
>
>
>
> -------- Forwarded Message --------
> Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
> Thursday, 11 July 2024
> Date:   Thu, 20 Jun 2024 14:02:02 +0000
> From:   Terri Agnew <terri.agnew at icann.org>
> To:     julf at julf.com <julf at julf.com>, jumaropi at yahoo.com
> <jumaropi at yahoo.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>, John McElwaine
> <john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
> 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>
>
>
>
> Dear all,
>
> In order to service your travel needs for ICANN81Istanbulin a timely
> fashion, please submit your meeting database tognso-secs at icann.org
> <mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important
> all funded travel air booking is completed by due date given in ICANN
> Travel emails.
>
> Please share with all funded travelers, the travel support guidelines
> wiki space: https://community.icann.org/x/lgvxAg
> <https://community.icann.org/x/lgvxAg> and highlight the communications
> responsibilities section:
>
> ICANN Travel Support attempts to reach a supported traveler four times
> before deeming the supported traveler unresponsive:
>
>   1. ICANN Travel Support sends ?welcome email.?
>   2. If there is no response after seven business days, ICANN Travel
>      Support sends a second email, copying ICANN support staff.
>   3. If there is no response five business days after the second email,
>      ICANN Travel Support sends a third email, copying ICANN support
>      staff and the community group chair.
>   4. If there is no response five business days after the third email,
>      ICANN Travel Support sends a fourth email, copying ICANN support
>      staff and the community group chair.
>
> If there is no response three days after the fourth attempt to reach the
> supported traveler, the community group may substitute another traveler.
>
> 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, 08 November *
>
>
>
> *Friday, 15 November*
>
> 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.
>
> 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.Follow link here
> <https://community.icann.org/x/fSfxAg> for assistance.
>
> 3.Wednesday, 25 September 2024*(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
>      <mailto: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.
>
> Kind regards,
>
> Terri
>
> Policy Team Supporting the GNSO
>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>


-- 

*Bruna Martins dos Santos *

Global Campaigns Manager | Digital Action <http://digitalaction.co>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
Humboldt Foundation <https://www.humboldt-foundation.de/>

Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>

Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
bruna.martinsantos
Email: bruna.mrtns at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240620/d74ca4ac/attachment.htm>

From farell at benin2point0.org  Thu Jun 20 18:34:46 2024
From: farell at benin2point0.org (farell at benin2point0.org)
Date: Thu, 20 Jun 2024 16:34:46 +0100
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
Message-ID: <1718897686081.7.39804@webmail-backend-production-8555699db7-rmp5m>

Hello Julf,


Yes, I would like to attend in person.

Le 20 juin 2024 ? 16:02 UTC+01:00, Johan Helsingius via NCSG-PC?<ncsg-pc at lists.ncsg.is> a ?crit?:

> Here we go again...
> 
> Please let me know if you intend to be in Istanbul in person or not.
> 
> Julf
> 
> 
> 
> -------- Forwarded Message --------
> Subject: ICANN81 | Istanbul | Supported Travelers Database Due | Thursday, 11 July 2024
> Date: Thu, 20 Jun 2024 14:02:02 +0000
> From: Terri Agnew <<terri.agnew at icann.org>>
> To: julf at julf.com <<julf at julf.com>>, <jumaropi at yahoo.com> <<jumaropi at yahoo.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>>, John McElwaine <<john.mcelwaine at nelsonmullins.com>>, Karen Day <Karen.Day at sas.com>
> 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>>
> 
> 
> 
> Dear all,
> 
> In order to service your travel needs for ICANN81Istanbulin a timely fashion, please submit your meeting database <tognso-secs at icann.org> <mailto:<gnso-secs at icann.org>>by*Thursday, 11 July 2024. *It is important all funded travel air booking is completed by due date given in ICANN Travel emails.
> 
> Please share with all funded travelers, the travel support guidelines wiki space: <https://community.icann.org/x/lgvxAg> <<https://community.icann.org/x/lgvxAg>> and highlight the communications responsibilities section:
> 
> ICANN Travel Support attempts to reach a supported traveler four times before deeming the supported traveler unresponsive:
> 
> 1. ICANN Travel Support sends ?welcome email.?
> 2. If there is no response after seven business days, ICANN Travel
> Support sends a second email, copying ICANN support staff.
> 3. If there is no response five business days after the second email,
> ICANN Travel Support sends a third email, copying ICANN support
> staff and the community group chair.
> 4. If there is no response five business days after the third email,
> ICANN Travel Support sends a fourth email, copying ICANN support
> staff and the community group chair.
> 
> If there is no response three days after the fourth attempt to reach the supported traveler, the community group may substitute another traveler.
> 
> 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, 08 November *
> 
> 
> 
> 
> *Friday, 15 November*
> 
> 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.
> 
> 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.Follow link here <<https://community.icann.org/x/fSfxAg>> for assistance.
> 
> 3.Wednesday, 25 September 2024*(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>
> <mailto:<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.
> 
> Kind regards,
> 
> Terri
> 
> Policy Team Supporting the GNSO
> 
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240620/b8b8e550/attachment.htm>

From julf at Julf.com  Thu Jun 20 18:59:43 2024
From: julf at Julf.com (Johan Helsingius)
Date: Thu, 20 Jun 2024 17:59:43 +0200
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <1718897686081.7.39804@webmail-backend-production-8555699db7-rmp5m>
References: <1718897686081.7.39804@webmail-backend-production-8555699db7-rmp5m>
Message-ID: <268728ef-23c0-4974-bfe4-dd0d5f1867cd@Julf.com>

Hi Farell,

I am afraid the ICANN travel funding is only available to councilors
(incoming and outgoing) and 2 EC members. If some of them can't attend,
there might be travel slots available to suitable volunteers.

	Julf

On 20/06/2024 17:34, farell at benin2point0.org wrote:
> Hello Julf,
> 
> Yes, I would like to attend in person.
> 
> 
> Le 20 juin 2024 ? 16:02 UTC+01:00, Johan Helsingius via 
> NCSG-PC?<ncsg-pc at lists.ncsg.is> a ?crit?:
> 
>     Here we go again...
> 
>     Please let me know if you intend to be in Istanbul in person or not.
> 
>     Julf
> 
> 
> 
>     -------- Forwarded Message --------
>     Subject: ICANN81 | Istanbul | Supported Travelers Database Due |
>     Thursday, 11 July 2024
>     Date: Thu, 20 Jun 2024 14:02:02 +0000
>     From: Terri Agnew <terri.agnew at icann.org <mailto:terri.agnew at icann.org>>
>     To: julf at julf.com <julf at julf.com <mailto:julf at julf.com>>,
>     jumaropi at yahoo.com <mailto:jumaropi at yahoo.com> <jumaropi at yahoo.com
>     <mailto:jumaropi at yahoo.com>>, benakin at gmail.com
>     <mailto:benakin at gmail.com> <benakin at gmail.com
>     <mailto:benakin at gmail.com>>, chair at rysg.info
>     <mailto:chair at rysg.info> <chair at rysg.info <mailto:chair at rysg.info>>,
>     aheineman at godaddy.com <mailto:aheineman at godaddy.com>
>     <aheineman at godaddy.com <mailto:aheineman at godaddy.com>>,
>     mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>
>     <mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>>,
>     lschulman at inta.org <mailto:lschulman at inta.org> <lschulman at inta.org
>     <mailto:lschulman at inta.org>>, philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com> <philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com>>, sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com> <sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>>, John McElwaine
>     <john.mcelwaine at nelsonmullins.com
>     <mailto:john.mcelwaine at nelsonmullins.com>>, Karen Day
>     <Karen.Day at sas.com>
>     CC: Brenda Brewer <brenda.brewer at icann.org
>     <mailto:brenda.brewer at icann.org>>, gnso-secs at icann.org
>     <mailto:gnso-secs at icann.org> <gnso-secs at icann.org
>     <mailto:gnso-secs at icann.org>>, Zoe Bonython
>     <secretariat at icannregistrars.org
>     <mailto:secretariat at icannregistrars.org>>, Andrea Glandon
>     <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org>>, Sue
>     Schuler <secretariat at rysg.info <mailto:secretariat at rysg.info>>
> 
> 
> 
>     Dear all,
> 
>     In order to service your travel needs for ICANN81Istanbulin a timely
>     fashion, please submit your meeting database tognso-secs at icann.org
>     <mailto:tognso-secs at icann.org> <mailto:gnso-secs at icann.org
>     <mailto:gnso-secs at icann.org>>by*Thursday, 11 July 2024. *It is
>     important all funded travel air booking is completed by due date
>     given in ICANN Travel emails.
> 
>     Please share with all funded travelers, the travel support
>     guidelines wiki space: https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>
>     <https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>> and highlight the
>     communications responsibilities section:
> 
>     ICANN Travel Support attempts to reach a supported traveler four
>     times before deeming the supported traveler unresponsive:
> 
>     1. ICANN Travel Support sends ?welcome email.?
>     2. If there is no response after seven business days, ICANN Travel
>     Support sends a second email, copying ICANN support staff.
>     3. If there is no response five business days after the second email,
>     ICANN Travel Support sends a third email, copying ICANN support
>     staff and the community group chair.
>     4. If there is no response five business days after the third email,
>     ICANN Travel Support sends a fourth email, copying ICANN support
>     staff and the community group chair.
> 
>     If there is no response three days after the fourth attempt to reach
>     the supported traveler, the community group may substitute another
>     traveler.
> 
>     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, 08 November *
> 
> 
> 
>     *Friday, 15 November*
> 
>     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.
> 
>     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.Follow link here
>     <https://community.icann.org/x/fSfxAg
>     <https://community.icann.org/x/fSfxAg>> for assistance.
> 
>     3.Wednesday, 25 September 2024*(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= <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
>     <mailto:privacy at icann.org>
>     <mailto:privacy at icann.org <mailto: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.
> 
>     Kind regards,
> 
>     Terri
> 
>     Policy Team Supporting the GNSO
> 
>     _______________________________________________
>     NCSG-PC mailing list
>     NCSG-PC at lists.ncsg.is
>     https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> 


From stephanie.perrin at mail.utoronto.ca  Thu Jun 20 19:52:24 2024
From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin)
Date: Thu, 20 Jun 2024 16:52:24 +0000
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <CADAEEV0Ppw-V2FzP+qT+S_nF9btvK7wgQc3BL_rdvgW_wEZBcA@mail.gmail.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
 <CADAEEV0Ppw-V2FzP+qT+S_nF9btvK7wgQc3BL_rdvgW_wEZBcA@mail.gmail.com>
Message-ID: <1FD565A1-3505-47C8-983E-A6F67CBC24CA@mail.utoronto.ca>

I intend to be there, this will be my last meeting.  Looking forward to seeing you all one last time!
Cheers Stephanie

On Jun 20, 2024, at 11:06?AM, Bruna Martins dos Santos <bruna.mrtns at gmail.com> wrote:

Am coming !

On Thu, Jun 20, 2024 at 5:02?PM Johan Helsingius via NCSG-EC <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>> wrote:
Here we go again...

Please let me know if you intend to be in Istanbul in person or not.

        Julf



-------- Forwarded Message --------
Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
Thursday, 11 July 2024
Date:   Thu, 20 Jun 2024 14:02:02 +0000
From:   Terri Agnew <terri.agnew at icann.org<mailto:terri.agnew at icann.org>>
To:     julf at julf.com<mailto:julf at julf.com> <julf at julf.com<mailto:julf at julf.com>>, jumaropi at yahoo.com<mailto:jumaropi at yahoo.com>
<jumaropi at yahoo.com<mailto:jumaropi at yahoo.com>>, benakin at gmail.com<mailto:benakin at gmail.com> <benakin at gmail.com<mailto:benakin at gmail.com>>,
chair at rysg.info<mailto:chair at rysg.info> <chair at rysg.info<mailto:chair at rysg.info>>, aheineman at godaddy.com<mailto:aheineman at godaddy.com>
<aheineman at godaddy.com<mailto:aheineman at godaddy.com>>, mcole at perkinscoie.com<mailto:mcole at perkinscoie.com> <mcole at perkinscoie.com<mailto:mcole at perkinscoie.com>>,
lschulman at inta.org<mailto:lschulman at inta.org> <lschulman at inta.org<mailto:lschulman at inta.org>>, philippe.fouquart at orange.com<mailto:philippe.fouquart at orange.com>
<philippe.fouquart at orange.com<mailto:philippe.fouquart at orange.com>>, sdemetriou at verisign.com<mailto:sdemetriou at verisign.com>
<sdemetriou at verisign.com<mailto:sdemetriou at verisign.com>>, John McElwaine
<john.mcelwaine at nelsonmullins.com<mailto:john.mcelwaine at nelsonmullins.com>>, Karen Day <Karen.Day at sas.com<mailto:Karen.Day at sas.com>>
CC:     Brenda Brewer <brenda.brewer at icann.org<mailto:brenda.brewer at icann.org>>, gnso-secs at icann.org<mailto:gnso-secs at icann.org>
<gnso-secs at icann.org<mailto:gnso-secs at icann.org>>, Zoe Bonython <secretariat at icannregistrars.org<mailto:secretariat at icannregistrars.org>>,
Andrea Glandon <andrea.glandon at icann.org<mailto:andrea.glandon at icann.org>>, Sue Schuler
<secretariat at rysg.info<mailto:secretariat at rysg.info>>



Dear all,

In order to service your travel needs for ICANN81Istanbulin a timely
fashion, please submit your meeting database tognso-secs at icann.org<mailto:tognso-secs at icann.org>
<mailto:gnso-secs at icann.org<mailto:gnso-secs at icann.org>>by*Thursday, 11 July 2024. *It is important
all funded travel air booking is completed by due date given in ICANN
Travel emails.

Please share with all funded travelers, the travel support guidelines
wiki space: https://community.icann.org/x/lgvxAg
<https://community.icann.org/x/lgvxAg> and highlight the communications
responsibilities section:

ICANN Travel Support attempts to reach a supported traveler four times
before deeming the supported traveler unresponsive:

  1. ICANN Travel Support sends ?welcome email.?
  2. If there is no response after seven business days, ICANN Travel
     Support sends a second email, copying ICANN support staff.
  3. If there is no response five business days after the second email,
     ICANN Travel Support sends a third email, copying ICANN support
     staff and the community group chair.
  4. If there is no response five business days after the third email,
     ICANN Travel Support sends a fourth email, copying ICANN support
     staff and the community group chair.

If there is no response three days after the fourth attempt to reach the
supported traveler, the community group may substitute another traveler.

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, 08 November *



*Friday, 15 November*

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.

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.Follow link here
<https://community.icann.org/x/fSfxAg> for assistance.

3.Wednesday, 25 September 2024*(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<http://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<mailto:privacy at icann.org>
     <mailto:privacy at icann.org<mailto: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.

Kind regards,

Terri

Policy Team Supporting the GNSO

_______________________________________________
NCSG-EC mailing list
NCSG-EC at lists.ncsg.is<mailto:NCSG-EC at lists.ncsg.is>
https://lists.ncsg.is/mailman/listinfo/ncsg-ec


--
Bruna Martins dos Santos

Global Campaigns Manager | Digital Action<http://digitalaction.co/>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation<https://www.humboldt-foundation.de/>
Member | Coaliz?o Direitos na Rede<https://direitosnarede.org.br/>
Co-Coordinator | Internet Governance Caucus <https://igcaucus.org/>

Twitter: @boomartins<https://twitter.com/boomartins> // Skype: bruna.martinsantos
Email: bruna.mrtns at gmail.com<mailto:bruna.mrtns at gmail.com>
_______________________________________________
NCSG-PC mailing list
NCSG-PC at lists.ncsg.is<mailto:NCSG-PC at lists.ncsg.is>
https://lists.ncsg.is/mailman/listinfo/ncsg-pc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240620/eaf22816/attachment.htm>

From farell at benin2point0.org  Thu Jun 20 20:51:40 2024
From: farell at benin2point0.org (farell at benin2point0.org)
Date: Thu, 20 Jun 2024 18:51:40 +0100
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
Message-ID: <1718905900833.7.45650@webmail-backend-production-8555699db7-rmp5m>

Yes I totally understand,


As a vice chair for the EPDP on IDN which would be presenting the final report, I intend to be there. If there is no funding available I would be there at my own expenses. It's in Europe and it won't cost that much.
I replied to the mail just FYI and in case there is an opportunity.


Thanks.

Le 20 juin 2024 ? 16:59 UTC+01:00, Johan Helsingius?<julf at Julf.com> a ?crit?:

> Hi Farell,
> 
> I am afraid the ICANN travel funding is only available to councilors
> (incoming and outgoing) and 2 EC members. If some of them can't attend,
> there might be travel slots available to suitable volunteers.
> 
> Julf
> 
> On 20/06/2024 17:34, <farell at benin2point0.org> wrote:
> 
> > Hello Julf,
> > Yes, I would like to attend in person.
> > Le 20 juin 2024 ? 16:02 UTC+01:00, Johan Helsingius via NCSG-PC?<<ncsg-pc at lists.ncsg.is>> a ?crit?:
> > Here we go again...
> > Please let me know if you intend to be in Istanbul in person or not.
> > Julf
> > -------- Forwarded Message --------
> > Subject: ICANN81 | Istanbul | Supported Travelers Database Due |
> > Thursday, 11 July 2024
> > Date: Thu, 20 Jun 2024 14:02:02 +0000
> > From: Terri Agnew <<terri.agnew at icann.org> <mailto:<terri.agnew at icann.org>>>
> > To: <julf at julf.com> <<julf at julf.com> <mailto:<julf at julf.com>>>,
> > <jumaropi at yahoo.com> <mailto:<jumaropi at yahoo.com>> <<jumaropi at yahoo.com>
> > <mailto:<jumaropi at yahoo.com>>>, <benakin at gmail.com>
> > <mailto:<benakin at gmail.com>> <<benakin at gmail.com>
> > <mailto:<benakin at gmail.com>>>, <chair at rysg.info>
> > <mailto:<chair at rysg.info>> <<chair at rysg.info> <mailto:<chair at rysg.info>>>,
> > <aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>
> > <<aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>>,
> > <mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>
> > <<mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>>,
> > <lschulman at inta.org> <mailto:<lschulman at inta.org>> <<lschulman at inta.org>
> > <mailto:<lschulman at inta.org>>>, <philippe.fouquart at orange.com>
> > <mailto:<philippe.fouquart at orange.com>> <<philippe.fouquart at orange.com>
> > <mailto:<philippe.fouquart at orange.com>>>, <sdemetriou at verisign.com>
> > <mailto:<sdemetriou at verisign.com>> <<sdemetriou at verisign.com>
> > <mailto:<sdemetriou at verisign.com>>>, John McElwaine
> > <<john.mcelwaine at nelsonmullins.com>
> > <mailto:<john.mcelwaine at nelsonmullins.com>>>, Karen Day
> > <Karen.Day at sas.com>
> > CC: Brenda Brewer <<brenda.brewer at icann.org>
> > <mailto:<brenda.brewer at icann.org>>>, <gnso-secs at icann.org>
> > <mailto:<gnso-secs at icann.org>> <<gnso-secs at icann.org>
> > <mailto:<gnso-secs at icann.org>>>, Zoe Bonython
> > <<secretariat at icannregistrars.org>
> > <mailto:<secretariat at icannregistrars.org>>>, Andrea Glandon
> > <<andrea.glandon at icann.org> <mailto:<andrea.glandon at icann.org>>>, Sue
> > Schuler <<secretariat at rysg.info> <mailto:<secretariat at rysg.info>>>
> > Dear all,
> > In order to service your travel needs for ICANN81Istanbulin a timely
> > fashion, please submit your meeting database <tognso-secs at icann.org>
> > <mailto:<tognso-secs at icann.org>> <mailto:<gnso-secs at icann.org>
> > <mailto:<gnso-secs at icann.org>>>by*Thursday, 11 July 2024. *It is
> > important all funded travel air booking is completed by due date
> > given in ICANN Travel emails.
> > Please share with all funded travelers, the travel support
> > guidelines wiki space: <https://community.icann.org/x/lgvxAg>
> > <<https://community.icann.org/x/lgvxAg>>
> > <<https://community.icann.org/x/lgvxAg>
> > <<https://community.icann.org/x/lgvxAg>>> and highlight the
> > communications responsibilities section:
> > ICANN Travel Support attempts to reach a supported traveler four
> > times before deeming the supported traveler unresponsive:
> > 1. ICANN Travel Support sends ?welcome email.?
> > 2. If there is no response after seven business days, ICANN Travel
> > Support sends a second email, copying ICANN support staff.
> > 3. If there is no response five business days after the second email,
> > ICANN Travel Support sends a third email, copying ICANN support
> > staff and the community group chair.
> > 4. If there is no response five business days after the third email,
> > ICANN Travel Support sends a fourth email, copying ICANN support
> > staff and the community group chair.
> > If there is no response three days after the fourth attempt to reach
> > the supported traveler, the community group may substitute another
> > traveler.
> > 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, 08 November *
> > *Friday, 15 November*
> > 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.
> > 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.Follow link here
> > <<https://community.icann.org/x/fSfxAg>
> > <<https://community.icann.org/x/fSfxAg>>> for assistance.
> > 3.Wednesday, 25 September 2024*(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=> <<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>
> > <mailto:<privacy at icann.org>>
> > <mailto:<privacy at icann.org> <mailto:<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.
> > Kind regards,
> > Terri
> > Policy Team Supporting the GNSO
> > _______________________________________________
> > NCSG-PC mailing list
> > NCSG-PC at lists.ncsg.is
> > <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> > <<https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
> > 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240620/f2ca4452/attachment.htm>

From julf at Julf.com  Thu Jun 20 22:24:38 2024
From: julf at Julf.com (Johan Helsingius)
Date: Thu, 20 Jun 2024 21:24:38 +0200
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <1718905900833.7.45650@webmail-backend-production-8555699db7-rmp5m>
References: <1718905900833.7.45650@webmail-backend-production-8555699db7-rmp5m>
Message-ID: <0eb83518-a4ae-4ed7-80c2-15be9faaa23b@Julf.com>

Noted - ICANN should really pay for travel for WG chairs, but
with the current budget climate that is not going to happen. :(

	Julf

On 20/06/2024 19:51, farell at benin2point0.org wrote:
> Yes I totally understand,
> 
> 
> As a vice chair for the EPDP on IDN which would be presenting the final 
> report, I intend to be there. If there is no funding available I would 
> be there at my own expenses. It's in Europe and it won't cost that much.
> I replied to the mail just FYI and in case there is an opportunity.
> 
> Thanks.
> 
> 
> Le 20 juin 2024 ? 16:59 UTC+01:00, Johan Helsingius?<julf at Julf.com> a 
> ?crit?:
> 
>     Hi Farell,
> 
>     I am afraid the ICANN travel funding is only available to councilors
>     (incoming and outgoing) and 2 EC members. If some of them can't attend,
>     there might be travel slots available to suitable volunteers.
> 
>     Julf
> 
>     On 20/06/2024 17:34, farell at benin2point0.org
>     <mailto:farell at benin2point0.org> wrote:
> 
>         Hello Julf,
>         Yes, I would like to attend in person.
>         Le 20 juin 2024 ? 16:02 UTC+01:00, Johan Helsingius via
>         NCSG-PC?<ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> a
>         ?crit?:
>         Here we go again...
>         Please let me know if you intend to be in Istanbul in person or not.
>         Julf
>         -------- Forwarded Message --------
>         Subject: ICANN81 | Istanbul | Supported Travelers Database Due |
>         Thursday, 11 July 2024
>         Date: Thu, 20 Jun 2024 14:02:02 +0000
>         From: Terri Agnew <terri.agnew at icann.org
>         <mailto:terri.agnew at icann.org> <mailto:terri.agnew at icann.org
>         <mailto:terri.agnew at icann.org>>>
>         To: julf at julf.com <mailto:julf at julf.com> <julf at julf.com
>         <mailto:julf at julf.com> <mailto:julf at julf.com
>         <mailto:julf at julf.com>>>,
>         jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>
>         <mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>>
>         <jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>
>         <mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>>>,
>         benakin at gmail.com <mailto:benakin at gmail.com>
>         <mailto:benakin at gmail.com <mailto:benakin at gmail.com>>
>         <benakin at gmail.com <mailto:benakin at gmail.com>
>         <mailto:benakin at gmail.com <mailto:benakin at gmail.com>>>,
>         chair at rysg.info <mailto:chair at rysg.info>
>         <mailto:chair at rysg.info <mailto:chair at rysg.info>>
>         <chair at rysg.info <mailto:chair at rysg.info>
>         <mailto:chair at rysg.info <mailto:chair at rysg.info>>>,
>         aheineman at godaddy.com <mailto:aheineman at godaddy.com>
>         <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>
>         <aheineman at godaddy.com <mailto:aheineman at godaddy.com>
>         <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>>,
>         mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>
>         <mailto:mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>>
>         <mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>
>         <mailto:mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>>>,
>         lschulman at inta.org <mailto:lschulman at inta.org>
>         <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>
>         <lschulman at inta.org <mailto:lschulman at inta.org>
>         <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>>,
>         philippe.fouquart at orange.com <mailto:philippe.fouquart at orange.com>
>         <mailto:philippe.fouquart at orange.com
>         <mailto:philippe.fouquart at orange.com>>
>         <philippe.fouquart at orange.com <mailto:philippe.fouquart at orange.com>
>         <mailto:philippe.fouquart at orange.com
>         <mailto:philippe.fouquart at orange.com>>>, sdemetriou at verisign.com
>         <mailto:sdemetriou at verisign.com>
>         <mailto:sdemetriou at verisign.com
>         <mailto:sdemetriou at verisign.com>> <sdemetriou at verisign.com
>         <mailto:sdemetriou at verisign.com>
>         <mailto:sdemetriou at verisign.com
>         <mailto:sdemetriou at verisign.com>>>, John McElwaine
>         <john.mcelwaine at nelsonmullins.com
>         <mailto:john.mcelwaine at nelsonmullins.com>
>         <mailto:john.mcelwaine at nelsonmullins.com
>         <mailto:john.mcelwaine at nelsonmullins.com>>>, Karen Day
>         <Karen.Day at sas.com>
>         CC: Brenda Brewer <brenda.brewer at icann.org
>         <mailto:brenda.brewer at icann.org>
>         <mailto:brenda.brewer at icann.org
>         <mailto:brenda.brewer at icann.org>>>, gnso-secs at icann.org
>         <mailto:gnso-secs at icann.org>
>         <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
>         <gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>         <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>>, Zoe
>         Bonython
>         <secretariat at icannregistrars.org
>         <mailto:secretariat at icannregistrars.org>
>         <mailto:secretariat at icannregistrars.org
>         <mailto:secretariat at icannregistrars.org>>>, Andrea Glandon
>         <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org>
>         <mailto:andrea.glandon at icann.org
>         <mailto:andrea.glandon at icann.org>>>, Sue
>         Schuler <secretariat at rysg.info <mailto:secretariat at rysg.info>
>         <mailto:secretariat at rysg.info <mailto:secretariat at rysg.info>>>
>         Dear all,
>         In order to service your travel needs for ICANN81Istanbulin a timely
>         fashion, please submit your meeting database
>         tognso-secs at icann.org <mailto:tognso-secs at icann.org>
>         <mailto:tognso-secs at icann.org <mailto:tognso-secs at icann.org>>
>         <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>         <mailto:gnso-secs at icann.org
>         <mailto:gnso-secs at icann.org>>>by*Thursday, 11 July 2024. *It is
>         important all funded travel air booking is completed by due date
>         given in ICANN Travel emails.
>         Please share with all funded travelers, the travel support
>         guidelines wiki space: https://community.icann.org/x/lgvxAg
>         <https://community.icann.org/x/lgvxAg>
>         <https://community.icann.org/x/lgvxAg
>         <https://community.icann.org/x/lgvxAg>>
>         <https://community.icann.org/x/lgvxAg
>         <https://community.icann.org/x/lgvxAg>
>         <https://community.icann.org/x/lgvxAg
>         <https://community.icann.org/x/lgvxAg>>> and highlight the
>         communications responsibilities section:
>         ICANN Travel Support attempts to reach a supported traveler four
>         times before deeming the supported traveler unresponsive:
>         1. ICANN Travel Support sends ?welcome email.?
>         2. If there is no response after seven business days, ICANN Travel
>         Support sends a second email, copying ICANN support staff.
>         3. If there is no response five business days after the second
>         email,
>         ICANN Travel Support sends a third email, copying ICANN support
>         staff and the community group chair.
>         4. If there is no response five business days after the third email,
>         ICANN Travel Support sends a fourth email, copying ICANN support
>         staff and the community group chair.
>         If there is no response three days after the fourth attempt to reach
>         the supported traveler, the community group may substitute another
>         traveler.
>         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, 08 November *
>         *Friday, 15 November*
>         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.
>         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.Follow link here
>         <https://community.icann.org/x/fSfxAg
>         <https://community.icann.org/x/fSfxAg>
>         <https://community.icann.org/x/fSfxAg
>         <https://community.icann.org/x/fSfxAg>>> for assistance.
>         3.Wednesday, 25 September 2024*(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= <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=> <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= <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 <mailto:privacy at icann.org>
>         <mailto:privacy at icann.org <mailto:privacy at icann.org>>
>         <mailto:privacy at icann.org <mailto:privacy at icann.org>
>         <mailto:privacy at icann.org <mailto: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.
>         Kind regards,
>         Terri
>         Policy Team Supporting the GNSO
>         _______________________________________________
>         NCSG-PC mailing list
>         NCSG-PC at lists.ncsg.is
>         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
> 

From wisdom.dk at gmail.com  Thu Jun 20 21:59:14 2024
From: wisdom.dk at gmail.com (Wisdom Donkor)
Date: Thu, 20 Jun 2024 20:59:14 +0200
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <d26f4c15-afc5-4661-957a-cb5149d290c7@Julf.com>
Message-ID: <CAAU+vPGR+whO5fTJph8GCbB=JGtGnvOwFeXzAhmSTHZrVjG39Q@mail.gmail.com>

I will attend in person.

On Thu, 20 Jun 2024, 5:02?pm Johan Helsingius via NCSG-PC, <
ncsg-pc at lists.ncsg.is> wrote:

> Here we go again...
>
> Please let me know if you intend to be in Istanbul in person or not.
>
>         Julf
>
>
>
> -------- Forwarded Message --------
> Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
> Thursday, 11 July 2024
> Date:   Thu, 20 Jun 2024 14:02:02 +0000
> From:   Terri Agnew <terri.agnew at icann.org>
> To:     julf at julf.com <julf at julf.com>, jumaropi at yahoo.com
> <jumaropi at yahoo.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>, John McElwaine
> <john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
> 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>
>
>
>
> Dear all,
>
> In order to service your travel needs for ICANN81Istanbulin a timely
> fashion, please submit your meeting database tognso-secs at icann.org
> <mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important
> all funded travel air booking is completed by due date given in ICANN
> Travel emails.
>
> Please share with all funded travelers, the travel support guidelines
> wiki space: https://community.icann.org/x/lgvxAg
> <https://community.icann.org/x/lgvxAg> and highlight the communications
> responsibilities section:
>
> ICANN Travel Support attempts to reach a supported traveler four times
> before deeming the supported traveler unresponsive:
>
>   1. ICANN Travel Support sends ?welcome email.?
>   2. If there is no response after seven business days, ICANN Travel
>      Support sends a second email, copying ICANN support staff.
>   3. If there is no response five business days after the second email,
>      ICANN Travel Support sends a third email, copying ICANN support
>      staff and the community group chair.
>   4. If there is no response five business days after the third email,
>      ICANN Travel Support sends a fourth email, copying ICANN support
>      staff and the community group chair.
>
> If there is no response three days after the fourth attempt to reach the
> supported traveler, the community group may substitute another traveler.
>
> 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, 08 November *
>
>
>
> *Friday, 15 November*
>
> 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.
>
> 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.Follow link here
> <https://community.icann.org/x/fSfxAg> for assistance.
>
> 3.Wednesday, 25 September 2024*(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
>      <mailto: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.
>
> Kind regards,
>
> Terri
>
> Policy Team Supporting the GNSO
>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240620/05c29e5c/attachment.htm>

From rafik.dammak at gmail.com  Fri Jun 21 13:23:05 2024
From: rafik.dammak at gmail.com (Rafik Dammak)
Date: Fri, 21 Jun 2024 19:23:05 +0900
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <0eb83518-a4ae-4ed7-80c2-15be9faaa23b@Julf.com>
References: <1718905900833.7.45650@webmail-backend-production-8555699db7-rmp5m>
 <0eb83518-a4ae-4ed7-80c2-15be9faaa23b@Julf.com>
Message-ID: <CAH5sThmQr=dK_k_s0YwraKcmMqZ3zsmEXc9YkD_XeUtEc+AYvA@mail.gmail.com>

Hi,

Not long ago, there was a budget previously for WG chairs and they applied
for it before. Did it stop?
maybe worthy to check with GNSO staff about its status.

Best,

Rafik


Le ven. 21 juin 2024 ? 04:24, Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> a ?crit :

> Noted - ICANN should really pay for travel for WG chairs, but
> with the current budget climate that is not going to happen. :(
>
>         Julf
>
> On 20/06/2024 19:51, farell at benin2point0.org wrote:
> > Yes I totally understand,
> >
> >
> > As a vice chair for the EPDP on IDN which would be presenting the final
> > report, I intend to be there. If there is no funding available I would
> > be there at my own expenses. It's in Europe and it won't cost that much.
> > I replied to the mail just FYI and in case there is an opportunity.
> >
> > Thanks.
> >
> >
> > Le 20 juin 2024 ? 16:59 UTC+01:00, Johan Helsingius <julf at Julf.com> a
> > ?crit :
> >
> >     Hi Farell,
> >
> >     I am afraid the ICANN travel funding is only available to councilors
> >     (incoming and outgoing) and 2 EC members. If some of them can't
> attend,
> >     there might be travel slots available to suitable volunteers.
> >
> >     Julf
> >
> >     On 20/06/2024 17:34, farell at benin2point0.org
> >     <mailto:farell at benin2point0.org> wrote:
> >
> >         Hello Julf,
> >         Yes, I would like to attend in person.
> >         Le 20 juin 2024 ? 16:02 UTC+01:00, Johan Helsingius via
> >         NCSG-PC <ncsg-pc at lists.ncsg.is <mailto:ncsg-pc at lists.ncsg.is>> a
> >         ?crit :
> >         Here we go again...
> >         Please let me know if you intend to be in Istanbul in person or
> not.
> >         Julf
> >         -------- Forwarded Message --------
> >         Subject: ICANN81 | Istanbul | Supported Travelers Database Due |
> >         Thursday, 11 July 2024
> >         Date: Thu, 20 Jun 2024 14:02:02 +0000
> >         From: Terri Agnew <terri.agnew at icann.org
> >         <mailto:terri.agnew at icann.org> <mailto:terri.agnew at icann.org
> >         <mailto:terri.agnew at icann.org>>>
> >         To: julf at julf.com <mailto:julf at julf.com> <julf at julf.com
> >         <mailto:julf at julf.com> <mailto:julf at julf.com
> >         <mailto:julf at julf.com>>>,
> >         jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>
> >         <mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>>
> >         <jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>
> >         <mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>>>,
> >         benakin at gmail.com <mailto:benakin at gmail.com>
> >         <mailto:benakin at gmail.com <mailto:benakin at gmail.com>>
> >         <benakin at gmail.com <mailto:benakin at gmail.com>
> >         <mailto:benakin at gmail.com <mailto:benakin at gmail.com>>>,
> >         chair at rysg.info <mailto:chair at rysg.info>
> >         <mailto:chair at rysg.info <mailto:chair at rysg.info>>
> >         <chair at rysg.info <mailto:chair at rysg.info>
> >         <mailto:chair at rysg.info <mailto:chair at rysg.info>>>,
> >         aheineman at godaddy.com <mailto:aheineman at godaddy.com>
> >         <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>
> >         <aheineman at godaddy.com <mailto:aheineman at godaddy.com>
> >         <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>>,
> >         mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>
> >         <mailto:mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>>
> >         <mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>
> >         <mailto:mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>>>,
> >         lschulman at inta.org <mailto:lschulman at inta.org>
> >         <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>
> >         <lschulman at inta.org <mailto:lschulman at inta.org>
> >         <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>>,
> >         philippe.fouquart at orange.com <mailto:
> philippe.fouquart at orange.com>
> >         <mailto:philippe.fouquart at orange.com
> >         <mailto:philippe.fouquart at orange.com>>
> >         <philippe.fouquart at orange.com <mailto:
> philippe.fouquart at orange.com>
> >         <mailto:philippe.fouquart at orange.com
> >         <mailto:philippe.fouquart at orange.com>>>, sdemetriou at verisign.com
> >         <mailto:sdemetriou at verisign.com>
> >         <mailto:sdemetriou at verisign.com
> >         <mailto:sdemetriou at verisign.com>> <sdemetriou at verisign.com
> >         <mailto:sdemetriou at verisign.com>
> >         <mailto:sdemetriou at verisign.com
> >         <mailto:sdemetriou at verisign.com>>>, John McElwaine
> >         <john.mcelwaine at nelsonmullins.com
> >         <mailto:john.mcelwaine at nelsonmullins.com>
> >         <mailto:john.mcelwaine at nelsonmullins.com
> >         <mailto:john.mcelwaine at nelsonmullins.com>>>, Karen Day
> >         <Karen.Day at sas.com>
> >         CC: Brenda Brewer <brenda.brewer at icann.org
> >         <mailto:brenda.brewer at icann.org>
> >         <mailto:brenda.brewer at icann.org
> >         <mailto:brenda.brewer at icann.org>>>, gnso-secs at icann.org
> >         <mailto:gnso-secs at icann.org>
> >         <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
> >         <gnso-secs at icann.org <mailto:gnso-secs at icann.org>
> >         <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>>, Zoe
> >         Bonython
> >         <secretariat at icannregistrars.org
> >         <mailto:secretariat at icannregistrars.org>
> >         <mailto:secretariat at icannregistrars.org
> >         <mailto:secretariat at icannregistrars.org>>>, Andrea Glandon
> >         <andrea.glandon at icann.org <mailto:andrea.glandon at icann.org>
> >         <mailto:andrea.glandon at icann.org
> >         <mailto:andrea.glandon at icann.org>>>, Sue
> >         Schuler <secretariat at rysg.info <mailto:secretariat at rysg.info>
> >         <mailto:secretariat at rysg.info <mailto:secretariat at rysg.info>>>
> >         Dear all,
> >         In order to service your travel needs for ICANN81Istanbulin a
> timely
> >         fashion, please submit your meeting database
> >         tognso-secs at icann.org <mailto:tognso-secs at icann.org>
> >         <mailto:tognso-secs at icann.org <mailto:tognso-secs at icann.org>>
> >         <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>
> >         <mailto:gnso-secs at icann.org
> >         <mailto:gnso-secs at icann.org>>>by*Thursday, 11 July 2024. *It is
> >         important all funded travel air booking is completed by due date
> >         given in ICANN Travel emails.
> >         Please share with all funded travelers, the travel support
> >         guidelines wiki space: https://community.icann.org/x/lgvxAg
> >         <https://community.icann.org/x/lgvxAg>
> >         <https://community.icann.org/x/lgvxAg
> >         <https://community.icann.org/x/lgvxAg>>
> >         <https://community.icann.org/x/lgvxAg
> >         <https://community.icann.org/x/lgvxAg>
> >         <https://community.icann.org/x/lgvxAg
> >         <https://community.icann.org/x/lgvxAg>>> and highlight the
> >         communications responsibilities section:
> >         ICANN Travel Support attempts to reach a supported traveler four
> >         times before deeming the supported traveler unresponsive:
> >         1. ICANN Travel Support sends ?welcome email.?
> >         2. If there is no response after seven business days, ICANN
> Travel
> >         Support sends a second email, copying ICANN support staff.
> >         3. If there is no response five business days after the second
> >         email,
> >         ICANN Travel Support sends a third email, copying ICANN support
> >         staff and the community group chair.
> >         4. If there is no response five business days after the third
> email,
> >         ICANN Travel Support sends a fourth email, copying ICANN support
> >         staff and the community group chair.
> >         If there is no response three days after the fourth attempt to
> reach
> >         the supported traveler, the community group may substitute
> another
> >         traveler.
> >         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, 08 November *
> >         *Friday, 15 November*
> >         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.
> >         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.Follow link here
> >         <https://community.icann.org/x/fSfxAg
> >         <https://community.icann.org/x/fSfxAg>
> >         <https://community.icann.org/x/fSfxAg
> >         <https://community.icann.org/x/fSfxAg>>> for assistance.
> >         3.Wednesday, 25 September 2024*(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=
> <
> 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=>
> <
> 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=
> <
> 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 <mailto:privacy at icann.org>
> >         <mailto:privacy at icann.org <mailto:privacy at icann.org>>
> >         <mailto:privacy at icann.org <mailto:privacy at icann.org>
> >         <mailto:privacy at icann.org <mailto: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.
> >         Kind regards,
> >         Terri
> >         Policy Team Supporting the GNSO
> >         _______________________________________________
> >         NCSG-PC mailing list
> >         NCSG-PC at lists.ncsg.is
> >         https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> >         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> >         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> >         <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
> >
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240621/f628de2a/attachment.htm>

From farell at benin2point0.org  Fri Jun 21 14:22:32 2024
From: farell at benin2point0.org (farell at benin2point0.org)
Date: Fri, 21 Jun 2024 13:22:32 +0200
Subject: [NCSG-EC] ICANN 81 Istanbul
Message-ID: <1718968952381.7.16104@webmail-backend-production-8555699db7-cd8gp>

Dear Terri,

I am looking for an opportunity to attend ICANN81 in-person as vice chair on the EPDN on IDN.

I remember that you told me that there are possibilities to get funded by NCSG or that ICANN can send a call for funding people in Leadership positions.

Can you please here give us more details about?

I haven't attended any meeting so far in person as Vice Chair.

I can to travel at my own expenses. Flight tickets are affordable but Hotels might too expensive for my budget.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240621/daeb6d07/attachment.htm>

From julf at Julf.com  Fri Jun 21 14:35:20 2024
From: julf at Julf.com (Johan Helsingius)
Date: Fri, 21 Jun 2024 13:35:20 +0200
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <CAH5sThmQr=dK_k_s0YwraKcmMqZ3zsmEXc9YkD_XeUtEc+AYvA@mail.gmail.com>
References: <1718905900833.7.45650@webmail-backend-production-8555699db7-rmp5m>
 <0eb83518-a4ae-4ed7-80c2-15be9faaa23b@Julf.com>
 <CAH5sThmQr=dK_k_s0YwraKcmMqZ3zsmEXc9YkD_XeUtEc+AYvA@mail.gmail.com>
Message-ID: <62a12d72-86b5-4dbb-86e6-3371c2f4453b@Julf.com>

I checked. WG chairs are funded, vice chairs are not.

	Julf

On 21/06/2024 12:23, Rafik Dammak wrote:
> 
> Hi,
> 
> Not long ago, there was a budget previously for WG chairs and they 
> applied for it before. Did it stop?
> maybe worthy to check with GNSO staff about its status.
> 
> Best,
> 
> Rafik
> 
> 
> Le?ven. 21 juin 2024 ??04:24, Johan Helsingius via NCSG-EC 
> <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> a ?crit?:
> 
>     Noted - ICANN should really pay for travel for WG chairs, but
>     with the current budget climate that is not going to happen. :(
> 
>      ? ? ? ? Julf
> 
>     On 20/06/2024 19:51, farell at benin2point0.org
>     <mailto:farell at benin2point0.org> wrote:
>      > Yes I totally understand,
>      >
>      >
>      > As a vice chair for the EPDP on IDN which would be presenting the
>     final
>      > report, I intend to be there. If there is no funding available I
>     would
>      > be there at my own expenses. It's in Europe and it won't cost
>     that much.
>      > I replied to the mail just FYI and in case there is an opportunity.
>      >
>      > Thanks.
>      >
>      >
>      > Le 20 juin 2024 ? 16:59 UTC+01:00, Johan
>     Helsingius?<julf at Julf.com> a
>      > ?crit?:
>      >
>      >? ? ?Hi Farell,
>      >
>      >? ? ?I am afraid the ICANN travel funding is only available to
>     councilors
>      >? ? ?(incoming and outgoing) and 2 EC members. If some of them
>     can't attend,
>      >? ? ?there might be travel slots available to suitable volunteers.
>      >
>      >? ? ?Julf
>      >
>      >? ? ?On 20/06/2024 17:34, farell at benin2point0.org
>     <mailto:farell at benin2point0.org>
>      >? ? ?<mailto:farell at benin2point0.org
>     <mailto:farell at benin2point0.org>> wrote:
>      >
>      >? ? ? ? ?Hello Julf,
>      >? ? ? ? ?Yes, I would like to attend in person.
>      >? ? ? ? ?Le 20 juin 2024 ? 16:02 UTC+01:00, Johan Helsingius via
>      >? ? ? ? ?NCSG-PC?<ncsg-pc at lists.ncsg.is
>     <mailto:ncsg-pc at lists.ncsg.is> <mailto:ncsg-pc at lists.ncsg.is
>     <mailto:ncsg-pc at lists.ncsg.is>>> a
>      >? ? ? ? ??crit?:
>      >? ? ? ? ?Here we go again...
>      >? ? ? ? ?Please let me know if you intend to be in Istanbul in
>     person or not.
>      >? ? ? ? ?Julf
>      >? ? ? ? ?-------- Forwarded Message --------
>      >? ? ? ? ?Subject: ICANN81 | Istanbul | Supported Travelers
>     Database Due |
>      >? ? ? ? ?Thursday, 11 July 2024
>      >? ? ? ? ?Date: Thu, 20 Jun 2024 14:02:02 +0000
>      >? ? ? ? ?From: Terri Agnew <terri.agnew at icann.org
>     <mailto:terri.agnew at icann.org>
>      >? ? ? ? ?<mailto:terri.agnew at icann.org
>     <mailto:terri.agnew at icann.org>> <mailto:terri.agnew at icann.org
>     <mailto:terri.agnew at icann.org>
>      >? ? ? ? ?<mailto:terri.agnew at icann.org
>     <mailto:terri.agnew at icann.org>>>>
>      >? ? ? ? ?To: julf at julf.com <mailto:julf at julf.com>
>     <mailto:julf at julf.com <mailto:julf at julf.com>> <julf at julf.com
>     <mailto:julf at julf.com>
>      >? ? ? ? ?<mailto:julf at julf.com <mailto:julf at julf.com>>
>     <mailto:julf at julf.com <mailto:julf at julf.com>
>      >? ? ? ? ?<mailto:julf at julf.com <mailto:julf at julf.com>>>>,
>      > jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>
>     <mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>>
>      >? ? ? ? ?<mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>
>     <mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>>>
>      >? ? ? ? ?<jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>
>     <mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>>
>      >? ? ? ? ?<mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>
>     <mailto:jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>>>>,
>      > benakin at gmail.com <mailto:benakin at gmail.com>
>     <mailto:benakin at gmail.com <mailto:benakin at gmail.com>>
>      >? ? ? ? ?<mailto:benakin at gmail.com <mailto:benakin at gmail.com>
>     <mailto:benakin at gmail.com <mailto:benakin at gmail.com>>>
>      >? ? ? ? ?<benakin at gmail.com <mailto:benakin at gmail.com>
>     <mailto:benakin at gmail.com <mailto:benakin at gmail.com>>
>      >? ? ? ? ?<mailto:benakin at gmail.com <mailto:benakin at gmail.com>
>     <mailto:benakin at gmail.com <mailto:benakin at gmail.com>>>>,
>      > chair at rysg.info <mailto:chair at rysg.info> <mailto:chair at rysg.info
>     <mailto:chair at rysg.info>>
>      >? ? ? ? ?<mailto:chair at rysg.info <mailto:chair at rysg.info>
>     <mailto:chair at rysg.info <mailto:chair at rysg.info>>>
>      >? ? ? ? ?<chair at rysg.info <mailto:chair at rysg.info>
>     <mailto:chair at rysg.info <mailto:chair at rysg.info>>
>      >? ? ? ? ?<mailto:chair at rysg.info <mailto:chair at rysg.info>
>     <mailto:chair at rysg.info <mailto:chair at rysg.info>>>>,
>      > aheineman at godaddy.com <mailto:aheineman at godaddy.com>
>     <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>
>      >? ? ? ? ?<mailto:aheineman at godaddy.com
>     <mailto:aheineman at godaddy.com> <mailto:aheineman at godaddy.com
>     <mailto:aheineman at godaddy.com>>>
>      >? ? ? ? ?<aheineman at godaddy.com <mailto:aheineman at godaddy.com>
>     <mailto:aheineman at godaddy.com <mailto:aheineman at godaddy.com>>
>      >? ? ? ? ?<mailto:aheineman at godaddy.com
>     <mailto:aheineman at godaddy.com> <mailto:aheineman at godaddy.com
>     <mailto:aheineman at godaddy.com>>>>,
>      > mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>
>     <mailto:mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>>
>      >? ? ? ? ?<mailto:mcole at perkinscoie.com
>     <mailto:mcole at perkinscoie.com> <mailto:mcole at perkinscoie.com
>     <mailto:mcole at perkinscoie.com>>>
>      >? ? ? ? ?<mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>
>     <mailto:mcole at perkinscoie.com <mailto:mcole at perkinscoie.com>>
>      >? ? ? ? ?<mailto:mcole at perkinscoie.com
>     <mailto:mcole at perkinscoie.com> <mailto:mcole at perkinscoie.com
>     <mailto:mcole at perkinscoie.com>>>>,
>      > lschulman at inta.org <mailto:lschulman at inta.org>
>     <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>
>      >? ? ? ? ?<mailto:lschulman at inta.org <mailto:lschulman at inta.org>
>     <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>>
>      >? ? ? ? ?<lschulman at inta.org <mailto:lschulman at inta.org>
>     <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>
>      >? ? ? ? ?<mailto:lschulman at inta.org <mailto:lschulman at inta.org>
>     <mailto:lschulman at inta.org <mailto:lschulman at inta.org>>>>,
>      > philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com>
>     <mailto:philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com>>
>      >? ? ? ? ?<mailto:philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com>
>      >? ? ? ? ?<mailto:philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com>>>
>      >? ? ? ? ?<philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com>
>     <mailto:philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com>>
>      >? ? ? ? ?<mailto:philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com>
>      >? ? ? ? ?<mailto:philippe.fouquart at orange.com
>     <mailto:philippe.fouquart at orange.com>>>>, sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>
>      >? ? ? ? ?<mailto:sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>>
>      >? ? ? ? ?<mailto:sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>
>      >? ? ? ? ?<mailto:sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>>> <sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>
>      >? ? ? ? ?<mailto:sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>>
>      >? ? ? ? ?<mailto:sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>
>      >? ? ? ? ?<mailto:sdemetriou at verisign.com
>     <mailto:sdemetriou at verisign.com>>>>, John McElwaine
>      >? ? ? ? ?<john.mcelwaine at nelsonmullins.com
>     <mailto:john.mcelwaine at nelsonmullins.com>
>      >? ? ? ? ?<mailto:john.mcelwaine at nelsonmullins.com
>     <mailto:john.mcelwaine at nelsonmullins.com>>
>      >? ? ? ? ?<mailto:john.mcelwaine at nelsonmullins.com
>     <mailto:john.mcelwaine at nelsonmullins.com>
>      >? ? ? ? ?<mailto:john.mcelwaine at nelsonmullins.com
>     <mailto:john.mcelwaine at nelsonmullins.com>>>>, Karen Day
>      >? ? ? ? ?<Karen.Day at sas.com <mailto:Karen.Day at sas.com>>
>      >? ? ? ? ?CC: Brenda Brewer <brenda.brewer at icann.org
>     <mailto:brenda.brewer at icann.org>
>      >? ? ? ? ?<mailto:brenda.brewer at icann.org
>     <mailto:brenda.brewer at icann.org>>
>      >? ? ? ? ?<mailto:brenda.brewer at icann.org
>     <mailto:brenda.brewer at icann.org>
>      >? ? ? ? ?<mailto:brenda.brewer at icann.org
>     <mailto:brenda.brewer at icann.org>>>>, gnso-secs at icann.org
>     <mailto:gnso-secs at icann.org>
>      >? ? ? ? ?<mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
>      >? ? ? ? ?<mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>     <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>>
>      >? ? ? ? ?<gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>     <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
>      >? ? ? ? ?<mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>     <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>>>, Zoe
>      >? ? ? ? ?Bonython
>      >? ? ? ? ?<secretariat at icannregistrars.org
>     <mailto:secretariat at icannregistrars.org>
>      >? ? ? ? ?<mailto:secretariat at icannregistrars.org
>     <mailto:secretariat at icannregistrars.org>>
>      >? ? ? ? ?<mailto:secretariat at icannregistrars.org
>     <mailto:secretariat at icannregistrars.org>
>      >? ? ? ? ?<mailto:secretariat at icannregistrars.org
>     <mailto:secretariat at icannregistrars.org>>>>, Andrea Glandon
>      >? ? ? ? ?<andrea.glandon at icann.org
>     <mailto:andrea.glandon at icann.org> <mailto:andrea.glandon at icann.org
>     <mailto:andrea.glandon at icann.org>>
>      >? ? ? ? ?<mailto:andrea.glandon at icann.org
>     <mailto:andrea.glandon at icann.org>
>      >? ? ? ? ?<mailto:andrea.glandon at icann.org
>     <mailto:andrea.glandon at icann.org>>>>, Sue
>      >? ? ? ? ?Schuler <secretariat at rysg.info
>     <mailto:secretariat at rysg.info> <mailto:secretariat at rysg.info
>     <mailto:secretariat at rysg.info>>
>      >? ? ? ? ?<mailto:secretariat at rysg.info
>     <mailto:secretariat at rysg.info> <mailto:secretariat at rysg.info
>     <mailto:secretariat at rysg.info>>>>
>      >? ? ? ? ?Dear all,
>      >? ? ? ? ?In order to service your travel needs for
>     ICANN81Istanbulin a timely
>      >? ? ? ? ?fashion, please submit your meeting database
>      > tognso-secs at icann.org <mailto:tognso-secs at icann.org>
>     <mailto:tognso-secs at icann.org <mailto:tognso-secs at icann.org>>
>      >? ? ? ? ?<mailto:tognso-secs at icann.org
>     <mailto:tognso-secs at icann.org> <mailto:tognso-secs at icann.org
>     <mailto:tognso-secs at icann.org>>>
>      >? ? ? ? ?<mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>     <mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
>      >? ? ? ? ?<mailto:gnso-secs at icann.org <mailto:gnso-secs at icann.org>
>      >? ? ? ? ?<mailto:gnso-secs at icann.org
>     <mailto:gnso-secs at icann.org>>>>by*Thursday, 11 July 2024. *It is
>      >? ? ? ? ?important all funded travel air booking is completed by
>     due date
>      >? ? ? ? ?given in ICANN Travel emails.
>      >? ? ? ? ?Please share with all funded travelers, the travel support
>      >? ? ? ? ?guidelines wiki space:
>     https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>
>      >? ? ? ? ?<https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>>
>      >? ? ? ? ?<https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>
>      >? ? ? ? ?<https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>>>
>      >? ? ? ? ?<https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>
>      >? ? ? ? ?<https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>>
>      >? ? ? ? ?<https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>
>      >? ? ? ? ?<https://community.icann.org/x/lgvxAg
>     <https://community.icann.org/x/lgvxAg>>>> and highlight the
>      >? ? ? ? ?communications responsibilities section:
>      >? ? ? ? ?ICANN Travel Support attempts to reach a supported
>     traveler four
>      >? ? ? ? ?times before deeming the supported traveler unresponsive:
>      >? ? ? ? ?1. ICANN Travel Support sends ?welcome email.?
>      >? ? ? ? ?2. If there is no response after seven business days,
>     ICANN Travel
>      >? ? ? ? ?Support sends a second email, copying ICANN support staff.
>      >? ? ? ? ?3. If there is no response five business days after the
>     second
>      >? ? ? ? ?email,
>      >? ? ? ? ?ICANN Travel Support sends a third email, copying ICANN
>     support
>      >? ? ? ? ?staff and the community group chair.
>      >? ? ? ? ?4. If there is no response five business days after the
>     third email,
>      >? ? ? ? ?ICANN Travel Support sends a fourth email, copying ICANN
>     support
>      >? ? ? ? ?staff and the community group chair.
>      >? ? ? ? ?If there is no response three days after the fourth
>     attempt to reach
>      >? ? ? ? ?the supported traveler, the community group may
>     substitute another
>      >? ? ? ? ?traveler.
>      >? ? ? ? ?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, 08 November *
>      >? ? ? ? ?*Friday, 15 November*
>      >? ? ? ? ?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.
>      >? ? ? ? ?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.Follow link here
>      >? ? ? ? ?<https://community.icann.org/x/fSfxAg
>     <https://community.icann.org/x/fSfxAg>
>      >? ? ? ? ?<https://community.icann.org/x/fSfxAg
>     <https://community.icann.org/x/fSfxAg>>
>      >? ? ? ? ?<https://community.icann.org/x/fSfxAg
>     <https://community.icann.org/x/fSfxAg>
>      >? ? ? ? ?<https://community.icann.org/x/fSfxAg
>     <https://community.icann.org/x/fSfxAg>>>> for assistance.
>      >? ? ? ? ?3.Wednesday, 25 September 2024*(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 <http://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= <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=> <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= <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=>> <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= <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=> <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= <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 <mailto:privacy at icann.org>
>     <mailto:privacy at icann.org <mailto:privacy at icann.org>>
>      >? ? ? ? ?<mailto:privacy at icann.org <mailto:privacy at icann.org>
>     <mailto:privacy at icann.org <mailto:privacy at icann.org>>>
>      >? ? ? ? ?<mailto:privacy at icann.org <mailto:privacy at icann.org>
>     <mailto:privacy at icann.org <mailto:privacy at icann.org>>
>      >? ? ? ? ?<mailto:privacy at icann.org <mailto:privacy at icann.org>
>     <mailto:privacy at icann.org <mailto: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.
>      >? ? ? ? ?Kind regards,
>      >? ? ? ? ?Terri
>      >? ? ? ? ?Policy Team Supporting the GNSO
>      >? ? ? ? ?_______________________________________________
>      >? ? ? ? ?NCSG-PC mailing list
>      > NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>      >? ? ? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
>      >? ? ? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
>      >? ? ? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>>
>      >
>     _______________________________________________
>     NCSG-EC mailing list
>     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> 

From farell at benin2point0.org  Fri Jun 21 14:46:11 2024
From: farell at benin2point0.org (farell at benin2point0.org)
Date: Fri, 21 Jun 2024 13:46:11 +0200
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <CAH5sThmQr=dK_k_s0YwraKcmMqZ3zsmEXc9YkD_XeUtEc+AYvA@mail.gmail.com>
References: <1718905900833.7.45650@webmail-backend-production-8555699db7-rmp5m>
 <0eb83518-a4ae-4ed7-80c2-15be9faaa23b@Julf.com>
 <CAH5sThmQr=dK_k_s0YwraKcmMqZ3zsmEXc9YkD_XeUtEc+AYvA@mail.gmail.com>
Message-ID: <1718970371364.6.25588@webmail-backend-production-8555699db7-42hfq>

Hi

thanks Rafik,

I thought it was only for chairs, not vice chairs. I will ask the staff again

Am 21. Juni 2024 um 12:23:05 +02:00, hat Rafik Dammak <rafik.dammak at gmail.com> geschrieben:

> 
> 
> Hi,
> 
> Not long ago, there was a budget previously for WG chairs and they applied for it before. Did it stop?
> maybe worthy to check with GNSO staff about its status.
> 
> Best,
> 
> Rafik
> 
> 
> 
> Le?ven. 21 juin 2024 ??04:24, Johan Helsingius via NCSG-EC <<ncsg-ec at lists.ncsg.is>> a ?crit?:
> 
> > Noted - ICANN should really pay for travel for WG chairs, but
> > with the current budget climate that is not going to happen. :(
> > 
> > Julf
> > 
> > On 20/06/2024 19:51, <farell at benin2point0.org> wrote:
> > > Yes I totally understand,
> > >
> > >
> > > As a vice chair for the EPDP on IDN which would be presenting the final
> > > report, I intend to be there. If there is no funding available I would
> > > be there at my own expenses. It's in Europe and it won't cost that much.
> > > I replied to the mail just FYI and in case there is an opportunity.
> > >
> > > Thanks.
> > >
> > >
> > > Le 20 juin 2024 ? 16:59 UTC+01:00, Johan Helsingius?<julf at Julf.com> a
> > > ?crit?:
> > >
> > > Hi Farell,
> > >
> > > I am afraid the ICANN travel funding is only available to councilors
> > > (incoming and outgoing) and 2 EC members. If some of them can't attend,
> > > there might be travel slots available to suitable volunteers.
> > >
> > > Julf
> > >
> > > On 20/06/2024 17:34, <farell at benin2point0.org>
> > > <mailto:<farell at benin2point0.org>> wrote:
> > >
> > > Hello Julf,
> > > Yes, I would like to attend in person.
> > > Le 20 juin 2024 ? 16:02 UTC+01:00, Johan Helsingius via
> > > NCSG-PC?<<ncsg-pc at lists.ncsg.is> <mailto:<ncsg-pc at lists.ncsg.is>>> a
> > > ?crit?:
> > > Here we go again...
> > > Please let me know if you intend to be in Istanbul in person or not.
> > > Julf
> > > -------- Forwarded Message --------
> > > Subject: ICANN81 | Istanbul | Supported Travelers Database Due |
> > > Thursday, 11 July 2024
> > > Date: Thu, 20 Jun 2024 14:02:02 +0000
> > > From: Terri Agnew <<terri.agnew at icann.org>
> > > <mailto:<terri.agnew at icann.org>> <mailto:<terri.agnew at icann.org>
> > > <mailto:<terri.agnew at icann.org>>>>
> > > To: <julf at julf.com> <mailto:<julf at julf.com>> <<julf at julf.com>
> > > <mailto:<julf at julf.com>> <mailto:<julf at julf.com>
> > > <mailto:<julf at julf.com>>>>,
> > > <jumaropi at yahoo.com> <mailto:<jumaropi at yahoo.com>>
> > > <mailto:<jumaropi at yahoo.com> <mailto:<jumaropi at yahoo.com>>>
> > > <<jumaropi at yahoo.com> <mailto:<jumaropi at yahoo.com>>
> > > <mailto:<jumaropi at yahoo.com> <mailto:<jumaropi at yahoo.com>>>>,
> > > <benakin at gmail.com> <mailto:<benakin at gmail.com>>
> > > <mailto:<benakin at gmail.com> <mailto:<benakin at gmail.com>>>
> > > <<benakin at gmail.com> <mailto:<benakin at gmail.com>>
> > > <mailto:<benakin at gmail.com> <mailto:<benakin at gmail.com>>>>,
> > > <chair at rysg.info> <mailto:<chair at rysg.info>>
> > > <mailto:<chair at rysg.info> <mailto:<chair at rysg.info>>>
> > > <<chair at rysg.info> <mailto:<chair at rysg.info>>
> > > <mailto:<chair at rysg.info> <mailto:<chair at rysg.info>>>>,
> > > <aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>
> > > <mailto:<aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>>
> > > <<aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>
> > > <mailto:<aheineman at godaddy.com> <mailto:<aheineman at godaddy.com>>>>,
> > > <mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>
> > > <mailto:<mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>>
> > > <<mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>
> > > <mailto:<mcole at perkinscoie.com> <mailto:<mcole at perkinscoie.com>>>>,
> > > <lschulman at inta.org> <mailto:<lschulman at inta.org>>
> > > <mailto:<lschulman at inta.org> <mailto:<lschulman at inta.org>>>
> > > <<lschulman at inta.org> <mailto:<lschulman at inta.org>>
> > > <mailto:<lschulman at inta.org> <mailto:<lschulman at inta.org>>>>,
> > > <philippe.fouquart at orange.com> <mailto:<philippe.fouquart at orange.com>>
> > > <mailto:<philippe.fouquart at orange.com>
> > > <mailto:<philippe.fouquart at orange.com>>>
> > > <<philippe.fouquart at orange.com> <mailto:<philippe.fouquart at orange.com>>
> > > <mailto:<philippe.fouquart at orange.com>
> > > <mailto:<philippe.fouquart at orange.com>>>>, <sdemetriou at verisign.com>
> > > <mailto:<sdemetriou at verisign.com>>
> > > <mailto:<sdemetriou at verisign.com>
> > > <mailto:<sdemetriou at verisign.com>>> <<sdemetriou at verisign.com>
> > > <mailto:<sdemetriou at verisign.com>>
> > > <mailto:<sdemetriou at verisign.com>
> > > <mailto:<sdemetriou at verisign.com>>>>, John McElwaine
> > > <<john.mcelwaine at nelsonmullins.com>
> > > <mailto:<john.mcelwaine at nelsonmullins.com>>
> > > <mailto:<john.mcelwaine at nelsonmullins.com>
> > > <mailto:<john.mcelwaine at nelsonmullins.com>>>>, Karen Day
> > > <<Karen.Day at sas.com>>
> > > CC: Brenda Brewer <<brenda.brewer at icann.org>
> > > <mailto:<brenda.brewer at icann.org>>
> > > <mailto:<brenda.brewer at icann.org>
> > > <mailto:<brenda.brewer at icann.org>>>>, <gnso-secs at icann.org>
> > > <mailto:<gnso-secs at icann.org>>
> > > <mailto:<gnso-secs at icann.org> <mailto:<gnso-secs at icann.org>>>
> > > <<gnso-secs at icann.org> <mailto:<gnso-secs at icann.org>>
> > > <mailto:<gnso-secs at icann.org> <mailto:<gnso-secs at icann.org>>>>, Zoe
> > > Bonython
> > > <<secretariat at icannregistrars.org>
> > > <mailto:<secretariat at icannregistrars.org>>
> > > <mailto:<secretariat at icannregistrars.org>
> > > <mailto:<secretariat at icannregistrars.org>>>>, Andrea Glandon
> > > <<andrea.glandon at icann.org> <mailto:<andrea.glandon at icann.org>>
> > > <mailto:<andrea.glandon at icann.org>
> > > <mailto:<andrea.glandon at icann.org>>>>, Sue
> > > Schuler <<secretariat at rysg.info> <mailto:<secretariat at rysg.info>>
> > > <mailto:<secretariat at rysg.info> <mailto:<secretariat at rysg.info>>>>
> > > Dear all,
> > > In order to service your travel needs for ICANN81Istanbulin a timely
> > > fashion, please submit your meeting database
> > > <tognso-secs at icann.org> <mailto:<tognso-secs at icann.org>>
> > > <mailto:<tognso-secs at icann.org> <mailto:<tognso-secs at icann.org>>>
> > > <mailto:<gnso-secs at icann.org> <mailto:<gnso-secs at icann.org>>
> > > <mailto:<gnso-secs at icann.org>
> > > <mailto:<gnso-secs at icann.org>>>>by*Thursday, 11 July 2024. *It is
> > > important all funded travel air booking is completed by due date
> > > given in ICANN Travel emails.
> > > Please share with all funded travelers, the travel support
> > > guidelines wiki space: <https://community.icann.org/x/lgvxAg>
> > > <<https://community.icann.org/x/lgvxAg>>
> > > <<https://community.icann.org/x/lgvxAg>
> > > <<https://community.icann.org/x/lgvxAg>>>
> > > <<https://community.icann.org/x/lgvxAg>
> > > <<https://community.icann.org/x/lgvxAg>>
> > > <<https://community.icann.org/x/lgvxAg>
> > > <<https://community.icann.org/x/lgvxAg>>>> and highlight the
> > > communications responsibilities section:
> > > ICANN Travel Support attempts to reach a supported traveler four
> > > times before deeming the supported traveler unresponsive:
> > > 1. ICANN Travel Support sends ?welcome email.?
> > > 2. If there is no response after seven business days, ICANN Travel
> > > Support sends a second email, copying ICANN support staff.
> > > 3. If there is no response five business days after the second
> > > email,
> > > ICANN Travel Support sends a third email, copying ICANN support
> > > staff and the community group chair.
> > > 4. If there is no response five business days after the third email,
> > > ICANN Travel Support sends a fourth email, copying ICANN support
> > > staff and the community group chair.
> > > If there is no response three days after the fourth attempt to reach
> > > the supported traveler, the community group may substitute another
> > > traveler.
> > > 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, 08 November *
> > > *Friday, 15 November*
> > > 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.
> > > 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.Follow link here
> > > <<https://community.icann.org/x/fSfxAg>
> > > <<https://community.icann.org/x/fSfxAg>>
> > > <<https://community.icann.org/x/fSfxAg>
> > > <<https://community.icann.org/x/fSfxAg>>>> for assistance.
> > > 3.Wednesday, 25 September 2024*(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 [<http://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=> <<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=>> <<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=> <<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> <mailto:<privacy at icann.org>>
> > > <mailto:<privacy at icann.org> <mailto:<privacy at icann.org>>>
> > > <mailto:<privacy at icann.org> <mailto:<privacy at icann.org>>
> > > <mailto:<privacy at icann.org> <mailto:<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.
> > > Kind regards,
> > > Terri
> > > Policy Team Supporting the GNSO
> > > _______________________________________________
> > > NCSG-PC mailing list
> > > <NCSG-PC at lists.ncsg.is>
> > > <https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> > > <<https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>
> > > <<https://lists.ncsg.is/mailman/listinfo/ncsg-pc>
> > > <<https://lists.ncsg.is/mailman/listinfo/ncsg-pc>>>
> > >
> > _______________________________________________
> > NCSG-EC mailing list
> > <NCSG-EC at lists.ncsg.is>
> > <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> > 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240621/66d87d68/attachment.htm>

From terri.agnew at icann.org  Fri Jun 21 15:32:20 2024
From: terri.agnew at icann.org (Terri Agnew)
Date: Fri, 21 Jun 2024 12:32:20 +0000
Subject: [NCSG-EC] [Ext] ICANN 81 Istanbul
In-Reply-To: <1718968952381.7.16104@webmail-backend-production-8555699db7-cd8gp>
References: <1718968952381.7.16104@webmail-backend-production-8555699db7-cd8gp>
Message-ID: <A17B22C8-D5A6-4104-BA60-97147557B597@icann.org>

Hi Farell,

Thanks for reaching out.

Please make sure to reach out to your SG/C group to see if they have any available funding. In addition, the GNSO PDP Chairs funding has two spots. The information to apply first goes to the chairs of the groups and if they decline, we open it up for vice-chairs. We are waiting to hear back from the chairs first.

It is also my understanding IDNs may be concluded by ICANN81.

All the best,

Terri

From: "farell at benin2point0.org" <farell at benin2point0.org>
Reply-To: "farell at benin2point0.org" <farell at benin2point0.org>
Date: Friday, June 21, 2024 at 6:23 AM
To: Terri Agnew <terri.agnew at icann.org>
Cc: NCSG EC <ncsg-ec at lists.ncsg.is>, Johan Helsingius <julf at julf.com>, "DonnaAustin605 at hotmail.com" <DonnaAustin605 at hotmail.com>
Subject: [Ext] ICANN 81 Istanbul

Dear Terri,

I am looking for an opportunity to attend ICANN81 in-person as vice chair on the EPDN on IDN.

I remember that you told me that there are  possibilities to get funded by NCSG or that ICANN can send a call for funding people in Leadership positions.

Can you please here give us more details about?

I haven't attended any meeting so far in person as Vice Chair.

I can to travel at my own expenses. Flight tickets are affordable but Hotels might too expensive for my budget.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240621/aa97fde4/attachment.htm>

From julf at Julf.com  Sun Jun 23 11:50:26 2024
From: julf at Julf.com (Johan Helsingius)
Date: Sun, 23 Jun 2024 10:50:26 +0200
Subject: [NCSG-EC] Fwd: ICANN81 | Istanbul | Supported Travelers Database
 Due | Thursday, 11 July 2024
In-Reply-To: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
Message-ID: <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>

Reminder...

Manju, Peter, Tomslin, Farzaneh, Tapani,

Please let me know if you intend to be in Istanbul in person or not.

	Julf



-------- Forwarded Message --------
Subject: 	ICANN81 | Istanbul | Supported Travelers Database Due | 
Thursday, 11 July 2024
Date: 	Thu, 20 Jun 2024 14:02:02 +0000
From: 	Terri Agnew <terri.agnew at icann.org>
To: 	julf at julf.com <julf at julf.com>, jumaropi at yahoo.com 
<jumaropi at yahoo.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>, John McElwaine 
<john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
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>



Dear all,

In order to service your travel needs for ICANN81Istanbulin a timely 
fashion, please submit your meeting database tognso-secs at icann.org 
<mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important 
all funded travel air booking is completed by due date given in ICANN 
Travel emails.

Please share with all funded travelers, the travel support guidelines 
wiki space: https://community.icann.org/x/lgvxAg 
<https://community.icann.org/x/lgvxAg> and highlight the communications 
responsibilities section:

ICANN Travel Support attempts to reach a supported traveler four times 
before deeming the supported traveler unresponsive:

   1. ICANN Travel Support sends ?welcome email.?
   2. If there is no response after seven business days, ICANN Travel
      Support sends a second email, copying ICANN support staff.
   3. If there is no response five business days after the second email,
      ICANN Travel Support sends a third email, copying ICANN support
      staff and the community group chair.
   4. If there is no response five business days after the third email,
      ICANN Travel Support sends a fourth email, copying ICANN support
      staff and the community group chair.

If there is no response three days after the fourth attempt to reach the 
supported traveler, the community group may substitute another traveler.

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, 08 November *

	

*Friday, 15 November*

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.

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.Follow link here 
<https://community.icann.org/x/fSfxAg> for assistance.

3.Wednesday, 25 September 2024*(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
      <mailto: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.

Kind regards,

Terri

Policy Team Supporting the GNSO



From mesumbeslin at gmail.com  Sun Jun 23 12:22:42 2024
From: mesumbeslin at gmail.com (Tomslin Samme-Nlar)
Date: Sun, 23 Jun 2024 19:22:42 +1000
Subject: [NCSG-EC] Fwd: ICANN81 | Istanbul | Supported Travelers
 Database Due | Thursday, 11 July 2024
In-Reply-To: <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>
Message-ID: <CAM8DdeV=vxM+AFEMgWp4x752wfzV76cT_+RcQTTDS4_5HgFyhQ@mail.gmail.com>

I intend to be there

Warmly,
Tomslin

On Sun, 23 June 2024, 18:50 Johan Helsingius via NCSG-EC, <
ncsg-ec at lists.ncsg.is> wrote:

> Reminder...
>
> Manju, Peter, Tomslin, Farzaneh, Tapani,
>
> Please let me know if you intend to be in Istanbul in person or not.
>
>         Julf
>
>
>
> -------- Forwarded Message --------
> Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
> Thursday, 11 July 2024
> Date:   Thu, 20 Jun 2024 14:02:02 +0000
> From:   Terri Agnew <terri.agnew at icann.org>
> To:     julf at julf.com <julf at julf.com>, jumaropi at yahoo.com
> <jumaropi at yahoo.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>, John McElwaine
> <john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
> 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>
>
>
>
> Dear all,
>
> In order to service your travel needs for ICANN81Istanbulin a timely
> fashion, please submit your meeting database tognso-secs at icann.org
> <mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important
> all funded travel air booking is completed by due date given in ICANN
> Travel emails.
>
> Please share with all funded travelers, the travel support guidelines
> wiki space: https://community.icann.org/x/lgvxAg
> <https://community.icann.org/x/lgvxAg> and highlight the communications
> responsibilities section:
>
> ICANN Travel Support attempts to reach a supported traveler four times
> before deeming the supported traveler unresponsive:
>
>    1. ICANN Travel Support sends ?welcome email.?
>    2. If there is no response after seven business days, ICANN Travel
>       Support sends a second email, copying ICANN support staff.
>    3. If there is no response five business days after the second email,
>       ICANN Travel Support sends a third email, copying ICANN support
>       staff and the community group chair.
>    4. If there is no response five business days after the third email,
>       ICANN Travel Support sends a fourth email, copying ICANN support
>       staff and the community group chair.
>
> If there is no response three days after the fourth attempt to reach the
> supported traveler, the community group may substitute another traveler.
>
> 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, 08 November *
>
>
>
> *Friday, 15 November*
>
> 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.
>
> 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.Follow link here
> <https://community.icann.org/x/fSfxAg> for assistance.
>
> 3.Wednesday, 25 September 2024*(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
>       <mailto: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.
>
> Kind regards,
>
> Terri
>
> Policy Team Supporting the GNSO
>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240623/b7dffcd4/attachment.htm>

From manju at nii.org.tw  Mon Jun 24 06:30:09 2024
From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=)
Date: Mon, 24 Jun 2024 11:30:09 +0800
Subject: [NCSG-EC] [NCSG-PC] Fwd: ICANN81 | Istanbul | Supported
 Travelers Database Due | Thursday, 11 July 2024
In-Reply-To: <CAM8DdeV=vxM+AFEMgWp4x752wfzV76cT_+RcQTTDS4_5HgFyhQ@mail.gmail.com>
References: <599CEBD6-AC19-416E-B511-3027A2B35D9C@icann.org>
 <c2ead156-97e6-4489-92d3-665b6902a04b@Julf.com>
 <CAM8DdeV=vxM+AFEMgWp4x752wfzV76cT_+RcQTTDS4_5HgFyhQ@mail.gmail.com>
Message-ID: <CAMeQZi1F+VhEmAhV1MQ81gi=tt3fN3mSxwpg00Od1S5h2Drz_A@mail.gmail.com>

Will be there in person, thank you!

Best,
Manju

On Sun, Jun 23, 2024 at 5:22?PM Tomslin Samme-Nlar <mesumbeslin at gmail.com>
wrote:

> I intend to be there
>
> Warmly,
> Tomslin
>
> On Sun, 23 June 2024, 18:50 Johan Helsingius via NCSG-EC, <
> ncsg-ec at lists.ncsg.is> wrote:
>
>> Reminder...
>>
>> Manju, Peter, Tomslin, Farzaneh, Tapani,
>>
>> Please let me know if you intend to be in Istanbul in person or not.
>>
>>         Julf
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject:        ICANN81 | Istanbul | Supported Travelers Database Due |
>> Thursday, 11 July 2024
>> Date:   Thu, 20 Jun 2024 14:02:02 +0000
>> From:   Terri Agnew <terri.agnew at icann.org>
>> To:     julf at julf.com <julf at julf.com>, jumaropi at yahoo.com
>> <jumaropi at yahoo.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>, John McElwaine
>> <john.mcelwaine at nelsonmullins.com>, Karen Day <Karen.Day at sas.com>
>> 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>
>>
>>
>>
>> Dear all,
>>
>> In order to service your travel needs for ICANN81Istanbulin a timely
>> fashion, please submit your meeting database tognso-secs at icann.org
>> <mailto:gnso-secs at icann.org>by*Thursday, 11 July 2024. *It is important
>> all funded travel air booking is completed by due date given in ICANN
>> Travel emails.
>>
>> Please share with all funded travelers, the travel support guidelines
>> wiki space: https://community.icann.org/x/lgvxAg
>> <https://community.icann.org/x/lgvxAg> and highlight the communications
>> responsibilities section:
>>
>> ICANN Travel Support attempts to reach a supported traveler four times
>> before deeming the supported traveler unresponsive:
>>
>>    1. ICANN Travel Support sends ?welcome email.?
>>    2. If there is no response after seven business days, ICANN Travel
>>       Support sends a second email, copying ICANN support staff.
>>    3. If there is no response five business days after the second email,
>>       ICANN Travel Support sends a third email, copying ICANN support
>>       staff and the community group chair.
>>    4. If there is no response five business days after the third email,
>>       ICANN Travel Support sends a fourth email, copying ICANN support
>>       staff and the community group chair.
>>
>> If there is no response three days after the fourth attempt to reach the
>> supported traveler, the community group may substitute another traveler.
>>
>> 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, 08 November *
>>
>>
>>
>> *Friday, 15 November*
>>
>> 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.
>>
>> 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.Follow link here
>> <https://community.icann.org/x/fSfxAg> for assistance.
>>
>> 3.Wednesday, 25 September 2024*(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
>>       <mailto: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.
>>
>> Kind regards,
>>
>> Terri
>>
>> Policy Team Supporting the GNSO
>>
>> _______________________________________________
>> NCSG-EC mailing list
>> NCSG-EC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>>
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240624/48104451/attachment.htm>

From julf at Julf.com  Mon Jun 24 15:15:39 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 24 Jun 2024 14:15:39 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
Message-ID: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>

NCSG has 3 travel slots for the EC - one for the (incoming) chair, and
two that are usually used for the EC reps (one for NCUC, one for NPOC).

Form what I can gather, NCUC isn't using their EC travel slot (David
is not able to travel, Farzaneh already has a slot as Councilor).

Would you be OK with using both slots for NPOC (Caleb and Tapani)
this time?

	Julf





From farzaneh.badii at gmail.com  Mon Jun 24 15:30:22 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Mon, 24 Jun 2024 13:30:22 +0100
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
Message-ID: <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>

Hi Julf,

I suggest we open the call for travel support to NCUC. Caleb and Tapani are
both NCUC members and can apply.

Farzaneh


On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> NCSG has 3 travel slots for the EC - one for the (incoming) chair, and
> two that are usually used for the EC reps (one for NCUC, one for NPOC).
>
> Form what I can gather, NCUC isn't using their EC travel slot (David
> is not able to travel, Farzaneh already has a slot as Councilor).
>
> Would you be OK with using both slots for NPOC (Caleb and Tapani)
> this time?
>
>         Julf
>
>
>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240624/d95cf118/attachment.htm>

From julf at Julf.com  Mon Jun 24 16:32:42 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 24 Jun 2024 15:32:42 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
Message-ID: <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>

i am a bit reluctant to open it up to all of NCUC at this point, as our
operating procedures state that the slots are specifically for NCSG EC
members.

	Julf

On 24/06/2024 14:30, farzaneh badii wrote:
> Hi Julf,
> 
> I suggest we open the call for travel support to NCUC. Caleb and Tapani 
> are both NCUC members and can apply.
> 
> Farzaneh
> 
> 
> On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC 
> <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> 
>     NCSG has 3 travel slots for the EC - one for the (incoming) chair, and
>     two that are usually used for the EC reps (one for NCUC, one for NPOC).
> 
>     Form what I can gather, NCUC isn't using their EC travel slot (David
>     is not able to travel, Farzaneh already has a slot as Councilor).
> 
>     Would you be OK with using both slots for NPOC (Caleb and Tapani)
>     this time?
> 
>      ? ? ? ? Julf
> 
> 
> 
>     _______________________________________________
>     NCSG-EC mailing list
>     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> 


From muyiwacaleb at gmail.com  Mon Jun 24 16:46:18 2024
From: muyiwacaleb at gmail.com (Caleb Olumuyiwa Ogundele)
Date: Mon, 24 Jun 2024 09:46:18 -0400
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
Message-ID: <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>

Hi Farzi,
This is an internal exchange of travel slots within the EC members and
would not be needed for a public announcement. I totally agree with Julf's
view here and the same respect would have been accorded vis-versa within
the EC. I believe Tapani brings value to the table and qualifies for the
slot.

On Mon, Jun 24, 2024 at 9:32?AM Johan Helsingius via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> i am a bit reluctant to open it up to all of NCUC at this point, as our
> operating procedures state that the slots are specifically for NCSG EC
> members.
>
>         Julf
>
> On 24/06/2024 14:30, farzaneh badii wrote:
> > Hi Julf,
> >
> > I suggest we open the call for travel support to NCUC. Caleb and Tapani
> > are both NCUC members and can apply.
> >
> > Farzaneh
> >
> >
> > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
> > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> >
> >     NCSG has 3 travel slots for the EC - one for the (incoming) chair,
> and
> >     two that are usually used for the EC reps (one for NCUC, one for
> NPOC).
> >
> >     Form what I can gather, NCUC isn't using their EC travel slot (David
> >     is not able to travel, Farzaneh already has a slot as Councilor).
> >
> >     Would you be OK with using both slots for NPOC (Caleb and Tapani)
> >     this time?
> >
> >              Julf
> >
> >
> >
> >     _______________________________________________
> >     NCSG-EC mailing list
> >     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>


-- 
*Caleb Ogundele*
Email: muyiwacaleb at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240624/b7dcf0f4/attachment.htm>

From farzaneh.badii at gmail.com  Mon Jun 24 16:46:54 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Mon, 24 Jun 2024 14:46:54 +0100
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
Message-ID: <CAN1qJvAZN54-ycBuupUqmRavsJ6coCb2jj3bXKGxxKD5oOqv7g@mail.gmail.com>

Oh yeah well we came up with those rules during my tenure and the idea was
to make sure each rep at ncsg ec of their respective constituencies get
their slot and then if not we open it up. And these are ncuc?s reps slots,
I don?t know how it?s gonna play out and how people are going to perceive
it.

Farzaneh


On Mon, Jun 24, 2024 at 2:32?PM Johan Helsingius <julf at julf.com> wrote:

> i am a bit reluctant to open it up to all of NCUC at this point, as our
> operating procedures state that the slots are specifically for NCSG EC
> members.
>
>         Julf
>
> On 24/06/2024 14:30, farzaneh badii wrote:
> > Hi Julf,
> >
> > I suggest we open the call for travel support to NCUC. Caleb and Tapani
> > are both NCUC members and can apply.
> >
> > Farzaneh
> >
> >
> > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
> > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> >
> >     NCSG has 3 travel slots for the EC - one for the (incoming) chair,
> and
> >     two that are usually used for the EC reps (one for NCUC, one for
> NPOC).
> >
> >     Form what I can gather, NCUC isn't using their EC travel slot (David
> >     is not able to travel, Farzaneh already has a slot as Councilor).
> >
> >     Would you be OK with using both slots for NPOC (Caleb and Tapani)
> >     this time?
> >
> >              Julf
> >
> >
> >
> >     _______________________________________________
> >     NCSG-EC mailing list
> >     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240624/0ce71c5b/attachment.htm>

From farzaneh.badii at gmail.com  Mon Jun 24 16:47:53 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Mon, 24 Jun 2024 14:47:53 +0100
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
Message-ID: <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>

Caleb

Since you potentially will be a recipient of the travel slot I suggest you
recuse yourself from the decision-making.

Farzaneh


On Mon, Jun 24, 2024 at 2:46?PM Caleb Olumuyiwa Ogundele <
muyiwacaleb at gmail.com> wrote:

> Hi Farzi,
> This is an internal exchange of travel slots within the EC members and
> would not be needed for a public announcement. I totally agree with Julf's
> view here and the same respect would have been accorded vis-versa within
> the EC. I believe Tapani brings value to the table and qualifies for the
> slot.
>
> On Mon, Jun 24, 2024 at 9:32?AM Johan Helsingius via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
>> i am a bit reluctant to open it up to all of NCUC at this point, as our
>> operating procedures state that the slots are specifically for NCSG EC
>> members.
>>
>>         Julf
>>
>> On 24/06/2024 14:30, farzaneh badii wrote:
>> > Hi Julf,
>> >
>> > I suggest we open the call for travel support to NCUC. Caleb and Tapani
>> > are both NCUC members and can apply.
>> >
>> > Farzaneh
>> >
>> >
>> > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
>> > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
>> >
>> >     NCSG has 3 travel slots for the EC - one for the (incoming) chair,
>> and
>> >     two that are usually used for the EC reps (one for NCUC, one for
>> NPOC).
>> >
>> >     Form what I can gather, NCUC isn't using their EC travel slot (David
>> >     is not able to travel, Farzaneh already has a slot as Councilor).
>> >
>> >     Would you be OK with using both slots for NPOC (Caleb and Tapani)
>> >     this time?
>> >
>> >              Julf
>> >
>> >
>> >
>> >     _______________________________________________
>> >     NCSG-EC mailing list
>> >     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>> >     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
>> >
>> _______________________________________________
>> NCSG-EC mailing list
>> NCSG-EC at lists.ncsg.is
>>
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
>
>>
>
> --
> *Caleb Ogundele*
> Email: muyiwacaleb at gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240624/bbfc9094/attachment.htm>

From andrea.glandon at icann.org  Mon Jun 24 19:05:37 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Mon, 24 Jun 2024 16:05:37 +0000
Subject: [NCSG-EC] [Ext] Re:  NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvAZN54-ycBuupUqmRavsJ6coCb2jj3bXKGxxKD5oOqv7g@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAN1qJvAZN54-ycBuupUqmRavsJ6coCb2jj3bXKGxxKD5oOqv7g@mail.gmail.com>
Message-ID: <29659D69-CF31-446C-8B96-8106873A2BAC@icann.org>

Hello all,

Just to note, Tapani sent an email that he will not be coming to ICANN81. It was being held in moderation, but was released this morning.

Kind Regards,
Andrea


From: NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of farzaneh badii via NCSG-EC <ncsg-ec at lists.ncsg.is>
Reply-To: farzaneh badii <farzaneh.badii at gmail.com>
Date: Monday, June 24, 2024 at 08:47
To: Johan Helsingius <julf at julf.com>
Cc: "benakin at gmail.com" <benakin at gmail.com>, Juan Manuel Rojas <jumaropi at yahoo.com>, NCSG EC <ncsg-ec at lists.ncsg.is>, Wisdom Donkor <wisdom.dk at gmail.com>
Subject: [Ext] Re: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)

Oh yeah well we came up with those rules during my tenure and the idea was to make sure each rep at ncsg ec of their respective constituencies get their slot and then if not we open it up. And these are ncuc?s reps slots, I don?t know how it?s gonna play out and how people are going to perceive it.

Farzaneh


On Mon, Jun 24, 2024 at 2:32?PM Johan Helsingius <julf at julf.com<mailto:julf at julf.com>> wrote:
i am a bit reluctant to open it up to all of NCUC at this point, as our
operating procedures state that the slots are specifically for NCSG EC
members.

        Julf

On 24/06/2024 14:30, farzaneh badii wrote:
> Hi Julf,
>
> I suggest we open the call for travel support to NCUC. Caleb and Tapani
> are both NCUC members and can apply.
>
> Farzaneh
>
>
> On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
> <ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is> <mailto:ncsg-ec at lists.ncsg.is<mailto:ncsg-ec at lists.ncsg.is>>> wrote:
>
>     NCSG has 3 travel slots for the EC - one for the (incoming) chair, and
>     two that are usually used for the EC reps (one for NCUC, one for NPOC).
>
>     Form what I can gather, NCUC isn't using their EC travel slot (David
>     is not able to travel, Farzaneh already has a slot as Councilor).
>
>     Would you be OK with using both slots for NPOC (Caleb and Tapani)
>     this time?
>
>              Julf
>
>
>
>     _______________________________________________
>     NCSG-EC mailing list
>     NCSG-EC at lists.ncsg.is<mailto:NCSG-EC at lists.ncsg.is> <mailto:NCSG-EC at lists.ncsg.is<mailto:NCSG-EC at lists.ncsg.is>>
>     https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is]<https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$>
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is]<https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240624/f847fc8b/attachment.htm>

From julf at Julf.com  Mon Jun 24 19:15:12 2024
From: julf at Julf.com (Johan Helsingius)
Date: Mon, 24 Jun 2024 18:15:12 +0200
Subject: [NCSG-EC] [Ext] Re:  NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <29659D69-CF31-446C-8B96-8106873A2BAC@icann.org>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAN1qJvAZN54-ycBuupUqmRavsJ6coCb2jj3bXKGxxKD5oOqv7g@mail.gmail.com>
 <29659D69-CF31-446C-8B96-8106873A2BAC@icann.org>
Message-ID: <26cee0a2-9055-4629-852a-0977582d342d@Julf.com>

Thanks Andrea!

It is my understanding that that was based on the assumption that there
was only one NPOC NCSG EC rep slot available.
	
	Julf


On 24/06/2024 18:05, Andrea Glandon wrote:
> Hello all,
> 
> Just to note, Tapani sent an email that he will not be coming to 
> ICANN81. It was being held in moderation, but was released this morning.
> 
> Kind Regards,
> 
> Andrea
> 
> *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of farzaneh 
> badii via NCSG-EC <ncsg-ec at lists.ncsg.is>
> *Reply-To: *farzaneh badii <farzaneh.badii at gmail.com>
> *Date: *Monday, June 24, 2024 at 08:47
> *To: *Johan Helsingius <julf at julf.com>
> *Cc: *"benakin at gmail.com" <benakin at gmail.com>, Juan Manuel Rojas 
> <jumaropi at yahoo.com>, NCSG EC <ncsg-ec at lists.ncsg.is>, Wisdom Donkor 
> <wisdom.dk at gmail.com>
> *Subject: *[Ext] Re: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
> 
> Oh yeah well we came up with those rules during my tenure and the idea 
> was to make sure each rep at ncsg ec of their respective constituencies 
> get their slot and then if not we open it up. And these are ncuc?s reps 
> slots, I don?t know how it?s gonna play out and how people are going to 
> perceive it.
> 
> Farzaneh
> 
> On Mon, Jun 24, 2024 at 2:32?PM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     i am a bit reluctant to open it up to all of NCUC at this point, as our
>     operating procedures state that the slots are specifically for NCSG EC
>     members.
> 
>      ? ? ? ? Julf
> 
>     On 24/06/2024 14:30, farzaneh badii wrote:
>      > Hi Julf,
>      >
>      > I suggest we open the call for travel support to NCUC. Caleb and
>     Tapani
>      > are both NCUC members and can apply.
>      >
>      > Farzaneh
>      >
>      >
>      > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
>      > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>> wrote:
>      >
>      >? ? ?NCSG has 3 travel slots for the EC - one for the (incoming)
>     chair, and
>      >? ? ?two that are usually used for the EC reps (one for NCUC, one
>     for NPOC).
>      >
>      >? ? ?Form what I can gather, NCUC isn't using their EC travel slot
>     (David
>      >? ? ?is not able to travel, Farzaneh already has a slot as Councilor).
>      >
>      >? ? ?Would you be OK with using both slots for NPOC (Caleb and Tapani)
>      >? ? ?this time?
>      >
>      >? ? ? ? ? ? ? Julf
>      >
>      >
>      >
>      >? ? ?_______________________________________________
>      >? ? ?NCSG-EC mailing list
>      > NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is]
>     <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     [lists.ncsg.is]
>     <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$>>
>      >
> 


From andrea.glandon at icann.org  Mon Jun 24 19:19:10 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Mon, 24 Jun 2024 16:19:10 +0000
Subject: [NCSG-EC] [Ext] Re:  NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <26cee0a2-9055-4629-852a-0977582d342d@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAN1qJvAZN54-ycBuupUqmRavsJ6coCb2jj3bXKGxxKD5oOqv7g@mail.gmail.com>
 <29659D69-CF31-446C-8B96-8106873A2BAC@icann.org>
 <26cee0a2-9055-4629-852a-0977582d342d@Julf.com>
Message-ID: <A3619BB1-F464-4E3A-988E-6C11A4010704@icann.org>

Ah, got it.

Kind Regards, 
Andrea 




?On 6/24/24, 11:15, "Johan Helsingius" <julf at Julf.com <mailto:julf at Julf.com>> wrote:


Thanks Andrea!


It is my understanding that that was based on the assumption that there
was only one NPOC NCSG EC rep slot available.


Julf




On 24/06/2024 18:05, Andrea Glandon wrote:
> Hello all,
> 
> Just to note, Tapani sent an email that he will not be coming to 
> ICANN81. It was being held in moderation, but was released this morning.
> 
> Kind Regards,
> 
> Andrea
> 
> *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is <mailto:ncsg-ec-bounces at lists.ncsg.is>> on behalf of farzaneh 
> badii via NCSG-EC <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>
> *Reply-To: *farzaneh badii <farzaneh.badii at gmail.com <mailto:farzaneh.badii at gmail.com>>
> *Date: *Monday, June 24, 2024 at 08:47
> *To: *Johan Helsingius <julf at julf.com <mailto:julf at julf.com>>
> *Cc: *"benakin at gmail.com <mailto:benakin at gmail.com>" <benakin at gmail.com <mailto:benakin at gmail.com>>, Juan Manuel Rojas 
> <jumaropi at yahoo.com <mailto:jumaropi at yahoo.com>>, NCSG EC <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>, Wisdom Donkor 
> <wisdom.dk at gmail.com <mailto:wisdom.dk at gmail.com>>
> *Subject: *[Ext] Re: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
> 
> Oh yeah well we came up with those rules during my tenure and the idea 
> was to make sure each rep at ncsg ec of their respective constituencies 
> get their slot and then if not we open it up. And these are ncuc?s reps 
> slots, I don?t know how it?s gonna play out and how people are going to 
> perceive it.
> 
> Farzaneh
> 
> On Mon, Jun 24, 2024 at 2:32 PM Johan Helsingius <julf at julf.com <mailto:julf at julf.com> 
> <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
> 
> i am a bit reluctant to open it up to all of NCUC at this point, as our
> operating procedures state that the slots are specifically for NCSG EC
> members.
> 
> Julf
> 
> On 24/06/2024 14:30, farzaneh badii wrote:
> > Hi Julf,
> >
> > I suggest we open the call for travel support to NCUC. Caleb and
> Tapani
> > are both NCUC members and can apply.
> >
> > Farzaneh
> >
> >
> > On Mon, Jun 24, 2024 at 1:15 PM Johan Helsingius via NCSG-EC
> > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is> <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>
> <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is> <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>>> wrote:
> >
> > NCSG has 3 travel slots for the EC - one for the (incoming)
> chair, and
> > two that are usually used for the EC reps (one for NCUC, one
> for NPOC).
> >
> > Form what I can gather, NCUC isn't using their EC travel slot
> (David
> > is not able to travel, Farzaneh already has a slot as Councilor).
> >
> > Would you be OK with using both slots for NPOC (Caleb and Tapani)
> > this time?
> >
> > Julf
> >
> >
> >
> > _______________________________________________
> > NCSG-EC mailing list
> > NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is> <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>
> <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is> <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>>
> > https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6mcsIavkX0Wf_0rtJIAsjeA-HV0ETYM5hnLl_Mh8NgPg5Gg59k0UTUU8m1TjNbuOOSA4lmW1c3-H45qT1XeI$ <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6mcsIavkX0Wf_0rtJIAsjeA-HV0ETYM5hnLl_Mh8NgPg5Gg59k0UTUU8m1TjNbuOOSA4lmW1c3-H45qT1XeI$> [lists[.]ncsg[.]is] [lists.ncsg.is]
> <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$>>
> > <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6mcsIavkX0Wf_0rtJIAsjeA-HV0ETYM5hnLl_Mh8NgPg5Gg59k0UTUU8m1TjNbuOOSA4lmW1c3-H45qT1XeI$ <https://urldefense.com/v3/__https://lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6mcsIavkX0Wf_0rtJIAsjeA-HV0ETYM5hnLl_Mh8NgPg5Gg59k0UTUU8m1TjNbuOOSA4lmW1c3-H45qT1XeI$> [lists[.]ncsg[.]is]
> [lists.ncsg.is]
> <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$ <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$>>>
> >
> 




From ncsg at tapani.tarvainen.info  Mon Jun 24 21:45:16 2024
From: ncsg at tapani.tarvainen.info (Tapani Tarvainen)
Date: Mon, 24 Jun 2024 21:45:16 +0300
Subject: [NCSG-EC] [Ext] Re:  NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <26cee0a2-9055-4629-852a-0977582d342d@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAN1qJvAZN54-ycBuupUqmRavsJ6coCb2jj3bXKGxxKD5oOqv7g@mail.gmail.com>
 <29659D69-CF31-446C-8B96-8106873A2BAC@icann.org>
 <26cee0a2-9055-4629-852a-0977582d342d@Julf.com>
Message-ID: <Znm-vIj40J8ZxgyE@saukko.tarvainen.info>

Julf is correct, I was under the impression there would not
be available travel slots. If there are, I could go.

Tapani

On Mon, Jun 24, 2024 at 06:15:12PM +0200, Johan Helsingius via NCSG-EC (ncsg-ec at lists.ncsg.is) wrote:
> 
> Thanks Andrea!
> 
> It is my understanding that that was based on the assumption that there
> was only one NPOC NCSG EC rep slot available.
> 	
> 	Julf
> 
> 
> On 24/06/2024 18:05, Andrea Glandon wrote:
> > Hello all,
> > 
> > Just to note, Tapani sent an email that he will not be coming to
> > ICANN81. It was being held in moderation, but was released this morning.
> > 
> > Kind Regards,
> > 
> > Andrea
> > 
> > *From: *NCSG-EC <ncsg-ec-bounces at lists.ncsg.is> on behalf of farzaneh
> > badii via NCSG-EC <ncsg-ec at lists.ncsg.is>
> > *Reply-To: *farzaneh badii <farzaneh.badii at gmail.com>
> > *Date: *Monday, June 24, 2024 at 08:47
> > *To: *Johan Helsingius <julf at julf.com>
> > *Cc: *"benakin at gmail.com" <benakin at gmail.com>, Juan Manuel Rojas
> > <jumaropi at yahoo.com>, NCSG EC <ncsg-ec at lists.ncsg.is>, Wisdom Donkor
> > <wisdom.dk at gmail.com>
> > *Subject: *[Ext] Re: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
> > 
> > Oh yeah well we came up with those rules during my tenure and the idea
> > was to make sure each rep at ncsg ec of their respective constituencies
> > get their slot and then if not we open it up. And these are ncuc?s reps
> > slots, I don?t know how it?s gonna play out and how people are going to
> > perceive it.
> > 
> > Farzaneh
> > 
> > On Mon, Jun 24, 2024 at 2:32?PM Johan Helsingius <julf at julf.com
> > <mailto:julf at julf.com>> wrote:
> > 
> >     i am a bit reluctant to open it up to all of NCUC at this point, as our
> >     operating procedures state that the slots are specifically for NCSG EC
> >     members.
> > 
> >      ? ? ? ? Julf
> > 
> >     On 24/06/2024 14:30, farzaneh badii wrote:
> >      > Hi Julf,
> >      >
> >      > I suggest we open the call for travel support to NCUC. Caleb and
> >     Tapani
> >      > are both NCUC members and can apply.
> >      >
> >      > Farzaneh
> >      >
> >      >
> >      > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
> >      > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
> >     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>> wrote:
> >      >
> >      >? ? ?NCSG has 3 travel slots for the EC - one for the (incoming)
> >     chair, and
> >      >? ? ?two that are usually used for the EC reps (one for NCUC, one
> >     for NPOC).
> >      >
> >      >? ? ?Form what I can gather, NCUC isn't using their EC travel slot
> >     (David
> >      >? ? ?is not able to travel, Farzaneh already has a slot as Councilor).
> >      >
> >      >? ? ?Would you be OK with using both slots for NPOC (Caleb and Tapani)
> >      >? ? ?this time?
> >      >
> >      >? ? ? ? ? ? ? Julf
> >      >
> >      >
> >      >
> >      >? ? ?_______________________________________________
> >      >? ? ?NCSG-EC mailing list
> >      > NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>
> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-ec [lists.ncsg.is]
> >     <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$>
> >      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     [lists.ncsg.is]
> >     <https://urldefense.com/v3/__https:/lists.ncsg.is/mailman/listinfo/ncsg-ec__;!!PtGJab4!6Td2WdxjIIKpUBzB9ybWcmnQoqr8XZbYYEybLeUH2xhBDiy3elpJjOjuHQCB0dbot78uy5DC7mrq6BwC-hY_VLLv6zVYhg$>>
> >      >
> > 
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec

-- 
Tapani Tarvainen


From ncsg at tapani.tarvainen.info  Tue Jun 25 08:03:18 2024
From: ncsg at tapani.tarvainen.info (Tapani Tarvainen)
Date: Tue, 25 Jun 2024 08:03:18 +0300
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
Message-ID: <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>

Hi Farzaneh,

Caleb is traveling on NPOC slot, so this decision will not affect
his travel and there's no reason for him to recuse himself.

I'm not sure if we have any rules or guidelines for recusals,
but I will recuse myself from this decision.

I won't even argue about it much, but I will add one data point:

I still administer NCUC's IT infrastructure and one reason it might be
useful for me to be in Istanbul would be talking about it with
Wisdom, Benjamin and NCUC EC (some handover stuff from Benjamin
to Wisdom, future plans).

Regards,

Tapani

On Mon, Jun 24, 2024 at 02:47:53PM +0100, farzaneh badii via NCSG-EC (ncsg-ec at lists.ncsg.is) wrote:
> 
> Caleb
> 
> Since you potentially will be a recipient of the travel slot I suggest you
> recuse yourself from the decision-making.
> 
> Farzaneh


From farzaneh.badii at gmail.com  Tue Jun 25 08:48:06 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Tue, 25 Jun 2024 06:48:06 +0100
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
Message-ID: <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>

Hello Tapani

Caleb travelled last time on the travel slot as well. Was that not on the
NPOC travel slot? Do you not rotate? If you do rotate, why not this time as
well? If I am not in a position to ask these questions, why is NPOC NCSG EC
in a position to decide on NCUC travel slots?

I believe these two travel slots belong to NCUC NCSG EC reps. I believe the
best course of action here is to provide an opportunity for NCUC members to
apply. Your reasoning is great but when we open the call for NCUC, then you
can apply with that reasoning.

Farzaneh


On Tue, Jun 25, 2024 at 7:03?AM Tapani Tarvainen <ncsg at tapani.tarvainen.info>
wrote:

> Hi Farzaneh,
>
> Caleb is traveling on NPOC slot, so this decision will not affect
> his travel and there's no reason for him to recuse himself.
>
> I'm not sure if we have any rules or guidelines for recusals,
> but I will recuse myself from this decision.
>
> I won't even argue about it much, but I will add one data point:
>
> I still administer NCUC's IT infrastructure and one reason it might be
> useful for me to be in Istanbul would be talking about it with
> Wisdom, Benjamin and NCUC EC (some handover stuff from Benjamin
> to Wisdom, future plans).
>
> Regards,
>
> Tapani
>
> On Mon, Jun 24, 2024 at 02:47:53PM +0100, farzaneh badii via NCSG-EC (
> ncsg-ec at lists.ncsg.is) wrote:
> >
> > Caleb
> >
> > Since you potentially will be a recipient of the travel slot I suggest
> you
> > recuse yourself from the decision-making.
> >
> > Farzaneh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/be734509/attachment.htm>

From julf at Julf.com  Tue Jun 25 09:54:51 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 25 Jun 2024 08:54:51 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
Message-ID: <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>

On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:

> I believe these two travel slots belong to NCUC NCSG EC reps. I believe 
> the best course of action here is to provide an opportunity for NCUC 
> members to apply.

Reading the NCSG Operating Procedures rules for NCSG
Travel Slot Transfer,
https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310

1. The NCSG receives the following travel slots per meeting:

    a. At the annual Policy Forum and the annual Community Forum,
       the NCSG receives 6 slots for Council members, and 3 slots
       for NCSG Executive Committee members, being a total of 9
       travel slots.

    b. At the Annual General Meeting, the NCSG receives travel slots
       for all incoming and outgoing Councilors (a minimum of 6 slots
       and a maximum of 9 slots, depending on whether or not new
       persons are rotating into the Council) as well as 3 travel
       slots to be allocated to the to NCSG Executive Committee.

So the 3 travel slots belong to the EC. Usually one slot is for
the (incoming) chair, and one each to a NCUC and a NPOC rep. Only
if EC members are unable to use the slots are they offered to
the wider membership. In this case two of the four EC reps
can use the slots - but they both happen to be from NPOC.

	Julf


From farzaneh.badii at gmail.com  Tue Jun 25 10:14:46 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Tue, 25 Jun 2024 09:14:46 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
Message-ID: <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>

I disagree with your interpretation Julf of the operating procedures. I
find it dangerous to allocate one constituency EC travel slot to another, I
also think as a matter of transparency we should announce the travel slot
available on the NCSG mailing list and ask NCUC members who also could be
the members of NPOC to apply. I don?t understand what the problem is with
opening this up. And no I don?t think NPOC NCSG EC reps should decide for
NCUC NCSG EC reps travel slots. We open it up, Tapani can apply.

Farzaneh


On Tue, Jun 25, 2024 at 8:54?AM Johan Helsingius <julf at julf.com> wrote:

> On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:
>
> > I believe these two travel slots belong to NCUC NCSG EC reps. I believe
> > the best course of action here is to provide an opportunity for NCUC
> > members to apply.
>
> Reading the NCSG Operating Procedures rules for NCSG
> Travel Slot Transfer,
>
> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310
>
> 1. The NCSG receives the following travel slots per meeting:
>
>     a. At the annual Policy Forum and the annual Community Forum,
>        the NCSG receives 6 slots for Council members, and 3 slots
>        for NCSG Executive Committee members, being a total of 9
>        travel slots.
>
>     b. At the Annual General Meeting, the NCSG receives travel slots
>        for all incoming and outgoing Councilors (a minimum of 6 slots
>        and a maximum of 9 slots, depending on whether or not new
>        persons are rotating into the Council) as well as 3 travel
>        slots to be allocated to the to NCSG Executive Committee.
>
> So the 3 travel slots belong to the EC. Usually one slot is for
> the (incoming) chair, and one each to a NCUC and a NPOC rep. Only
> if EC members are unable to use the slots are they offered to
> the wider membership. In this case two of the four EC reps
> can use the slots - but they both happen to be from NPOC.
>
>         Julf
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/87502e1a/attachment.htm>

From bruna.mrtns at gmail.com  Tue Jun 25 10:33:03 2024
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Tue, 25 Jun 2024 09:33:03 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
Message-ID: <CADAEEV2ETr4uGh5uE2VbAhFNiW8M7h=pNgqyyPu9tTtq6O1Www@mail.gmail.com>

Just adding my two cents to the conversation as a non-ec member: I agree
that the decision is NCSGs+NCUCs. These two slots are allocated to NCUC
reps at the EC and if they're not being used they should be open for
Members to apply and use it under certain requirements such as writing a
report about the meeting or presenting at the NCSG membership meeting.

Also agree with Farzaneh that it's problematic that the possibility of
opening a call - either to NCUC or NCSG members - for them to have the
chance of using the slot is being ruled out. Especially because that's the
precedent: whenever we didnt fill the EC travel slots we opened it up to
membership under a "fellowship" mode.

Best,
B

On Tue, Jun 25, 2024 at 9:15?AM farzaneh badii via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> I disagree with your interpretation Julf of the operating procedures. I
> find it dangerous to allocate one constituency EC travel slot to another, I
> also think as a matter of transparency we should announce the travel slot
> available on the NCSG mailing list and ask NCUC members who also could be
> the members of NPOC to apply. I don?t understand what the problem is with
> opening this up. And no I don?t think NPOC NCSG EC reps should decide for
> NCUC NCSG EC reps travel slots. We open it up, Tapani can apply.
>
> Farzaneh
>
>
> On Tue, Jun 25, 2024 at 8:54?AM Johan Helsingius <julf at julf.com> wrote:
>
>> On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:
>>
>> > I believe these two travel slots belong to NCUC NCSG EC reps. I believe
>> > the best course of action here is to provide an opportunity for NCUC
>> > members to apply.
>>
>> Reading the NCSG Operating Procedures rules for NCSG
>> Travel Slot Transfer,
>>
>> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310
>>
>> 1. The NCSG receives the following travel slots per meeting:
>>
>>     a. At the annual Policy Forum and the annual Community Forum,
>>        the NCSG receives 6 slots for Council members, and 3 slots
>>        for NCSG Executive Committee members, being a total of 9
>>        travel slots.
>>
>>     b. At the Annual General Meeting, the NCSG receives travel slots
>>        for all incoming and outgoing Councilors (a minimum of 6 slots
>>        and a maximum of 9 slots, depending on whether or not new
>>        persons are rotating into the Council) as well as 3 travel
>>        slots to be allocated to the to NCSG Executive Committee.
>>
>> So the 3 travel slots belong to the EC. Usually one slot is for
>> the (incoming) chair, and one each to a NCUC and a NPOC rep. Only
>> if EC members are unable to use the slots are they offered to
>> the wider membership. In this case two of the four EC reps
>> can use the slots - but they both happen to be from NPOC.
>>
>>         Julf
>>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>


-- 

*Bruna Martins dos Santos *

Global Campaigns Manager | Digital Action <http://digitalaction.co>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
Humboldt Foundation <https://www.humboldt-foundation.de/>

Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>

Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
bruna.martinsantos
Email: bruna.mrtns at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/c0fc819e/attachment.htm>

From julf at Julf.com  Tue Jun 25 11:14:09 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 25 Jun 2024 10:14:09 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
Message-ID: <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>

The way I see it is that the slots are intended for EC members, and once
on the EC, the members really represent NCSG, not NCUC/NPOC.

	Julf


On 25/06/2024 09:14, farzaneh badii wrote:
> I disagree with your interpretation Julf of the operating procedures. I 
> find it dangerous to allocate one constituency EC travel slot to 
> another, I also think as a matter of transparency we should announce the 
> travel slot available on the NCSG mailing list and ask NCUC members who 
> also could be the members of NPOC to apply. I don?t understand what the 
> problem is with opening this up. And no I don?t think NPOC NCSG EC reps 
> should decide for NCUC NCSG EC reps travel slots. We open it up, Tapani 
> can apply.
> 
> Farzaneh
> 
> 
> On Tue, Jun 25, 2024 at 8:54?AM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:
> 
>      > I believe these two travel slots belong to NCUC NCSG EC reps. I
>     believe
>      > the best course of action here is to provide an opportunity for NCUC
>      > members to apply.
> 
>     Reading the NCSG Operating Procedures rules for NCSG
>     Travel Slot Transfer,
>     https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310 <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310>
> 
>     1. The NCSG receives the following travel slots per meeting:
> 
>      ? ? a. At the annual Policy Forum and the annual Community Forum,
>      ? ? ? ?the NCSG receives 6 slots for Council members, and 3 slots
>      ? ? ? ?for NCSG Executive Committee members, being a total of 9
>      ? ? ? ?travel slots.
> 
>      ? ? b. At the Annual General Meeting, the NCSG receives travel slots
>      ? ? ? ?for all incoming and outgoing Councilors (a minimum of 6 slots
>      ? ? ? ?and a maximum of 9 slots, depending on whether or not new
>      ? ? ? ?persons are rotating into the Council) as well as 3 travel
>      ? ? ? ?slots to be allocated to the to NCSG Executive Committee.
> 
>     So the 3 travel slots belong to the EC. Usually one slot is for
>     the (incoming) chair, and one each to a NCUC and a NPOC rep. Only
>     if EC members are unable to use the slots are they offered to
>     the wider membership. In this case two of the four EC reps
>     can use the slots - but they both happen to be from NPOC.
> 
>      ? ? ? ? Julf
> 


From farzaneh.badii at gmail.com  Tue Jun 25 11:24:16 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Tue, 25 Jun 2024 10:24:16 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
Message-ID: <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>

If that was the case then the governance of it should have been at the NCSG
level like the council is. But it is not. Each constituency appoints their
own reps and nobody can tell them how they allocated their slots.

Farzaneh


On Tue, Jun 25, 2024 at 10:14?AM Johan Helsingius <julf at julf.com> wrote:

> The way I see it is that the slots are intended for EC members, and once
> on the EC, the members really represent NCSG, not NCUC/NPOC.
>
>         Julf
>
>
> On 25/06/2024 09:14, farzaneh badii wrote:
> > I disagree with your interpretation Julf of the operating procedures. I
> > find it dangerous to allocate one constituency EC travel slot to
> > another, I also think as a matter of transparency we should announce the
> > travel slot available on the NCSG mailing list and ask NCUC members who
> > also could be the members of NPOC to apply. I don?t understand what the
> > problem is with opening this up. And no I don?t think NPOC NCSG EC reps
> > should decide for NCUC NCSG EC reps travel slots. We open it up, Tapani
> > can apply.
> >
> > Farzaneh
> >
> >
> > On Tue, Jun 25, 2024 at 8:54?AM Johan Helsingius <julf at julf.com
> > <mailto:julf at julf.com>> wrote:
> >
> >     On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:
> >
> >      > I believe these two travel slots belong to NCUC NCSG EC reps. I
> >     believe
> >      > the best course of action here is to provide an opportunity for
> NCUC
> >      > members to apply.
> >
> >     Reading the NCSG Operating Procedures rules for NCSG
> >     Travel Slot Transfer,
> >
> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310
> <
> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310
> >
> >
> >     1. The NCSG receives the following travel slots per meeting:
> >
> >          a. At the annual Policy Forum and the annual Community Forum,
> >             the NCSG receives 6 slots for Council members, and 3 slots
> >             for NCSG Executive Committee members, being a total of 9
> >             travel slots.
> >
> >          b. At the Annual General Meeting, the NCSG receives travel slots
> >             for all incoming and outgoing Councilors (a minimum of 6
> slots
> >             and a maximum of 9 slots, depending on whether or not new
> >             persons are rotating into the Council) as well as 3 travel
> >             slots to be allocated to the to NCSG Executive Committee.
> >
> >     So the 3 travel slots belong to the EC. Usually one slot is for
> >     the (incoming) chair, and one each to a NCUC and a NPOC rep. Only
> >     if EC members are unable to use the slots are they offered to
> >     the wider membership. In this case two of the four EC reps
> >     can use the slots - but they both happen to be from NPOC.
> >
> >              Julf
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/c81416f4/attachment.htm>

From julf at Julf.com  Tue Jun 25 12:26:05 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 25 Jun 2024 11:26:05 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
Message-ID: <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>

Hi Andrea,

Can you help clarify - are the 3 NCSG EC travel slots allocated to
NCSG, or to NCUC/NPOC?

	Julf


On 25/06/2024 10:24, farzaneh badii wrote:
> If that was the case then the governance of it should have been at the 
> NCSG level like the council is. But it is not. Each constituency 
> appoints their own reps and nobody can tell them how they allocated 
> their slots.
> 
> Farzaneh
> 
> 
> On Tue, Jun 25, 2024 at 10:14?AM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     The way I see it is that the slots are intended for EC members, and once
>     on the EC, the members really represent NCSG, not NCUC/NPOC.
> 
>      ? ? ? ? Julf
> 
> 
>     On 25/06/2024 09:14, farzaneh badii wrote:
>      > I disagree with your interpretation Julf of the operating
>     procedures. I
>      > find it dangerous to allocate one constituency EC travel slot to
>      > another, I also think as a matter of transparency we should
>     announce the
>      > travel slot available on the NCSG mailing list and ask NCUC
>     members who
>      > also could be the members of NPOC to apply. I don?t understand
>     what the
>      > problem is with opening this up. And no I don?t think NPOC NCSG
>     EC reps
>      > should decide for NCUC NCSG EC reps travel slots. We open it up,
>     Tapani
>      > can apply.
>      >
>      > Farzaneh
>      >
>      >
>      > On Tue, Jun 25, 2024 at 8:54?AM Johan Helsingius <julf at julf.com
>     <mailto:julf at julf.com>
>      > <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
>      >
>      >? ? ?On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:
>      >
>      >? ? ? > I believe these two travel slots belong to NCUC NCSG EC
>     reps. I
>      >? ? ?believe
>      >? ? ? > the best course of action here is to provide an
>     opportunity for NCUC
>      >? ? ? > members to apply.
>      >
>      >? ? ?Reading the NCSG Operating Procedures rules for NCSG
>      >? ? ?Travel Slot Transfer,
>      >
>     https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310 <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310 <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310>>
>      >
>      >? ? ?1. The NCSG receives the following travel slots per meeting:
>      >
>      >? ? ? ? ? a. At the annual Policy Forum and the annual Community
>     Forum,
>      >? ? ? ? ? ? ?the NCSG receives 6 slots for Council members, and 3
>     slots
>      >? ? ? ? ? ? ?for NCSG Executive Committee members, being a total of 9
>      >? ? ? ? ? ? ?travel slots.
>      >
>      >? ? ? ? ? b. At the Annual General Meeting, the NCSG receives
>     travel slots
>      >? ? ? ? ? ? ?for all incoming and outgoing Councilors (a minimum
>     of 6 slots
>      >? ? ? ? ? ? ?and a maximum of 9 slots, depending on whether or not new
>      >? ? ? ? ? ? ?persons are rotating into the Council) as well as 3
>     travel
>      >? ? ? ? ? ? ?slots to be allocated to the to NCSG Executive Committee.
>      >
>      >? ? ?So the 3 travel slots belong to the EC. Usually one slot is for
>      >? ? ?the (incoming) chair, and one each to a NCUC and a NPOC rep. Only
>      >? ? ?if EC members are unable to use the slots are they offered to
>      >? ? ?the wider membership. In this case two of the four EC reps
>      >? ? ?can use the slots - but they both happen to be from NPOC.
>      >
>      >? ? ? ? ? ? ? Julf
>      >
> 


From farzaneh.badii at gmail.com  Tue Jun 25 12:43:42 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Tue, 25 Jun 2024 11:43:42 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
Message-ID: <CAN1qJvDq8sdUA+grGQNpzH20Kt=Fddb+UXsqy_6btk2xJrRPeQ@mail.gmail.com>

Why are we asking this? ICANN gives three travel slots to NCSG EC. I am not
disputing that. How we allocate it is in collaboration with the
constituencies.thats our internal governance.  Which ICANN has no part in
and shouldn?t decide for us and never has.
If you want to insist on this, please go ahead and allocate the slot to
Tapani but let NCSG know. I have raised the issues and made the points. I
don?t think it?s advisable to spend much more time on this.


Farzaneh


On Tue, Jun 25, 2024 at 11:26?AM Johan Helsingius <julf at julf.com> wrote:

> Hi Andrea,
>
> Can you help clarify - are the 3 NCSG EC travel slots allocated to
> NCSG, or to NCUC/NPOC?
>
>         Julf
>
>
> On 25/06/2024 10:24, farzaneh badii wrote:
> > If that was the case then the governance of it should have been at the
> > NCSG level like the council is. But it is not. Each constituency
> > appoints their own reps and nobody can tell them how they allocated
> > their slots.
> >
> > Farzaneh
> >
> >
> > On Tue, Jun 25, 2024 at 10:14?AM Johan Helsingius <julf at julf.com
> > <mailto:julf at julf.com>> wrote:
> >
> >     The way I see it is that the slots are intended for EC members, and
> once
> >     on the EC, the members really represent NCSG, not NCUC/NPOC.
> >
> >              Julf
> >
> >
> >     On 25/06/2024 09:14, farzaneh badii wrote:
> >      > I disagree with your interpretation Julf of the operating
> >     procedures. I
> >      > find it dangerous to allocate one constituency EC travel slot to
> >      > another, I also think as a matter of transparency we should
> >     announce the
> >      > travel slot available on the NCSG mailing list and ask NCUC
> >     members who
> >      > also could be the members of NPOC to apply. I don?t understand
> >     what the
> >      > problem is with opening this up. And no I don?t think NPOC NCSG
> >     EC reps
> >      > should decide for NCUC NCSG EC reps travel slots. We open it up,
> >     Tapani
> >      > can apply.
> >      >
> >      > Farzaneh
> >      >
> >      >
> >      > On Tue, Jun 25, 2024 at 8:54?AM Johan Helsingius <julf at julf.com
> >     <mailto:julf at julf.com>
> >      > <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
> >      >
> >      >     On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:
> >      >
> >      >      > I believe these two travel slots belong to NCUC NCSG EC
> >     reps. I
> >      >     believe
> >      >      > the best course of action here is to provide an
> >     opportunity for NCUC
> >      >      > members to apply.
> >      >
> >      >     Reading the NCSG Operating Procedures rules for NCSG
> >      >     Travel Slot Transfer,
> >      >
> >
> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310
> <
> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310>
> <
> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310
> <
> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310
> >>
> >      >
> >      >     1. The NCSG receives the following travel slots per meeting:
> >      >
> >      >          a. At the annual Policy Forum and the annual Community
> >     Forum,
> >      >             the NCSG receives 6 slots for Council members, and 3
> >     slots
> >      >             for NCSG Executive Committee members, being a total
> of 9
> >      >             travel slots.
> >      >
> >      >          b. At the Annual General Meeting, the NCSG receives
> >     travel slots
> >      >             for all incoming and outgoing Councilors (a minimum
> >     of 6 slots
> >      >             and a maximum of 9 slots, depending on whether or not
> new
> >      >             persons are rotating into the Council) as well as 3
> >     travel
> >      >             slots to be allocated to the to NCSG Executive
> Committee.
> >      >
> >      >     So the 3 travel slots belong to the EC. Usually one slot is
> for
> >      >     the (incoming) chair, and one each to a NCUC and a NPOC rep.
> Only
> >      >     if EC members are unable to use the slots are they offered to
> >      >     the wider membership. In this case two of the four EC reps
> >      >     can use the slots - but they both happen to be from NPOC.
> >      >
> >      >              Julf
> >      >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/b4e5950b/attachment.htm>

From julf at Julf.com  Tue Jun 25 13:19:16 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 25 Jun 2024 12:19:16 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvDq8sdUA+grGQNpzH20Kt=Fddb+UXsqy_6btk2xJrRPeQ@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
 <CAN1qJvDq8sdUA+grGQNpzH20Kt=Fddb+UXsqy_6btk2xJrRPeQ@mail.gmail.com>
Message-ID: <7adc7f8e-282d-410f-aaea-99aa3e1d651f@Julf.com>

On 25/06/2024 11:43, farzaneh badii wrote:
> Why are we asking this?

Because I appreciate clarity in the rather poorly documented
ways travel slots are allocated. There doesn't seem to be
any public document outlining how Org allocates travel
slots to constituencies and groups.

	Julf



From farzaneh.badii at gmail.com  Tue Jun 25 13:20:52 2024
From: farzaneh.badii at gmail.com (farzaneh badii)
Date: Tue, 25 Jun 2024 12:20:52 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <7adc7f8e-282d-410f-aaea-99aa3e1d651f@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
 <CAN1qJvDq8sdUA+grGQNpzH20Kt=Fddb+UXsqy_6btk2xJrRPeQ@mail.gmail.com>
 <7adc7f8e-282d-410f-aaea-99aa3e1d651f@Julf.com>
Message-ID: <CAN1qJvAEt9pX72t5r4Pcn+VqxJeskZ3aAxZpyTmi3XBaeWiDFg@mail.gmail.com>

ICANN org is not setting our travel policy so they cannot provide clarity!

Farzaneh


On Tue, Jun 25, 2024 at 12:19?PM Johan Helsingius <julf at julf.com> wrote:

> On 25/06/2024 11:43, farzaneh badii wrote:
> > Why are we asking this?
>
> Because I appreciate clarity in the rather poorly documented
> ways travel slots are allocated. There doesn't seem to be
> any public document outlining how Org allocates travel
> slots to constituencies and groups.
>
>         Julf
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/c605d84c/attachment.htm>

From bruna.mrtns at gmail.com  Tue Jun 25 13:30:46 2024
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Tue, 25 Jun 2024 12:30:46 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvAEt9pX72t5r4Pcn+VqxJeskZ3aAxZpyTmi3XBaeWiDFg@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
 <CAN1qJvDq8sdUA+grGQNpzH20Kt=Fddb+UXsqy_6btk2xJrRPeQ@mail.gmail.com>
 <7adc7f8e-282d-410f-aaea-99aa3e1d651f@Julf.com>
 <CAN1qJvAEt9pX72t5r4Pcn+VqxJeskZ3aAxZpyTmi3XBaeWiDFg@mail.gmail.com>
Message-ID: <CADAEEV3dbvyZ_ERzt2Bw=B1N3frp36eLtM0-fjzJsMo5jns4Sg@mail.gmail.com>

It?s not Orgs place to define how NCSG and its constituencies distribute
their travel resources, really.

The most appropriate way to deal with this situation would be - again - to
open a call for applications to fill this slot or lose it. I would also be
extra wary of raising this issues to staff since we don?t want them to
think we don?t need these slots as we don?t have people putting their hands
up.

Open a call, say NCUC members will be prioritised since this was a slot for
NCUC EC reps and let?s be more transparent w/ membership.

Best,




*Bruna Martins dos Santos *

Global Campaigns Manager | Digital Action <http://digitalaction.co>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
Humboldt Foundation <https://www.humboldt-foundation.de/>

Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>

Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
bruna.martinsantos
Email: bruna.mrtns at gmail.com


farzaneh badii via NCSG-EC <ncsg-ec at lists.ncsg.is> schrieb am Di. 25. Juni
2024 um 12:21:

> ICANN org is not setting our travel policy so they cannot provide clarity!
>
>
> Farzaneh
>
>
> On Tue, Jun 25, 2024 at 12:19?PM Johan Helsingius <julf at julf.com> wrote:
>
>> On 25/06/2024 11:43, farzaneh badii wrote:
>> > Why are we asking this?
>>
>> Because I appreciate clarity in the rather poorly documented
>> ways travel slots are allocated. There doesn't seem to be
>> any public document outlining how Org allocates travel
>> slots to constituencies and groups.
>>
>>         Julf
>>
>> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/2ba2a44c/attachment.htm>

From julf at Julf.com  Tue Jun 25 14:25:05 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 25 Jun 2024 13:25:05 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvAEt9pX72t5r4Pcn+VqxJeskZ3aAxZpyTmi3XBaeWiDFg@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
 <CAN1qJvDq8sdUA+grGQNpzH20Kt=Fddb+UXsqy_6btk2xJrRPeQ@mail.gmail.com>
 <7adc7f8e-282d-410f-aaea-99aa3e1d651f@Julf.com>
 <CAN1qJvAEt9pX72t5r4Pcn+VqxJeskZ3aAxZpyTmi3XBaeWiDFg@mail.gmail.com>
Message-ID: <2a427133-59cc-4a8b-9260-d1fa0fc277de@Julf.com>

On 25/06/2024 12:20, farzaneh badii wrote:
> ICANN org is not setting our travel policy so they cannot provide clarity!

No, but they can (hopefully) explain what rules they follow.

	Julf



From julf at Julf.com  Tue Jun 25 14:27:23 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 25 Jun 2024 13:27:23 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CADAEEV3dbvyZ_ERzt2Bw=B1N3frp36eLtM0-fjzJsMo5jns4Sg@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
 <CAN1qJvDq8sdUA+grGQNpzH20Kt=Fddb+UXsqy_6btk2xJrRPeQ@mail.gmail.com>
 <7adc7f8e-282d-410f-aaea-99aa3e1d651f@Julf.com>
 <CAN1qJvAEt9pX72t5r4Pcn+VqxJeskZ3aAxZpyTmi3XBaeWiDFg@mail.gmail.com>
 <CADAEEV3dbvyZ_ERzt2Bw=B1N3frp36eLtM0-fjzJsMo5jns4Sg@mail.gmail.com>
Message-ID: <f411318e-d6b8-4e4e-b9b4-85e5199235ed@Julf.com>

On 25/06/2024 12:30, Bruna Martins dos Santos wrote:
> It?s not Orgs place to define how NCSG and its constituencies distribute 
> their travel resources, really.

No, but I would love to see by what rules Org allocate the travel slots.

> I would 
> also be extra wary of raising this issues to staff since we don?t want 
> them to think we don?t need these slots as we don?t have people putting 
> their hands up.

You are of course aware that multiple staff members are on the ncsg-ec
list... :)

	Julf


From bruna.mrtns at gmail.com  Tue Jun 25 14:32:10 2024
From: bruna.mrtns at gmail.com (Bruna Martins dos Santos)
Date: Tue, 25 Jun 2024 13:32:10 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <f411318e-d6b8-4e4e-b9b4-85e5199235ed@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
 <CAN1qJvDq8sdUA+grGQNpzH20Kt=Fddb+UXsqy_6btk2xJrRPeQ@mail.gmail.com>
 <7adc7f8e-282d-410f-aaea-99aa3e1d651f@Julf.com>
 <CAN1qJvAEt9pX72t5r4Pcn+VqxJeskZ3aAxZpyTmi3XBaeWiDFg@mail.gmail.com>
 <CADAEEV3dbvyZ_ERzt2Bw=B1N3frp36eLtM0-fjzJsMo5jns4Sg@mail.gmail.com>
 <f411318e-d6b8-4e4e-b9b4-85e5199235ed@Julf.com>
Message-ID: <CADAEEV2AC=MNUbLpPBkBSMGygehxCnoMyYSXZbVMWBW0Mor73w@mail.gmail.com>

I have also been the admin of such lists in my tenure so no need to explain
the obvious. I?m just flagging one possible conclusion they might have, and
nothing offensive.




*Bruna Martins dos Santos *

Global Campaigns Manager | Digital Action <http://digitalaction.co>

German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von
Humboldt Foundation <https://www.humboldt-foundation.de/>

Member | Coaliz?o Direitos na Rede <https://direitosnarede.org.br/>
Co-Coordinator | Internet Governance Caucus  <https://igcaucus.org/>

Twitter: @boomartins <https://twitter.com/boomartins> // Skype:
bruna.martinsantos
Email: bruna.mrtns at gmail.com


Johan Helsingius <julf at julf.com> schrieb am Di. 25. Juni 2024 um 13:27:

> On 25/06/2024 12:30, Bruna Martins dos Santos wrote:
> > It?s not Orgs place to define how NCSG and its constituencies distribute
> > their travel resources, really.
>
> No, but I would love to see by what rules Org allocate the travel slots.
>
> > I would
> > also be extra wary of raising this issues to staff since we don?t want
> > them to think we don?t need these slots as we don?t have people putting
> > their hands up.
>
> You are of course aware that multiple staff members are on the ncsg-ec
> list... :)
>
>         Julf
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/e401c15e/attachment.htm>

From julf at Julf.com  Tue Jun 25 15:56:00 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 25 Jun 2024 14:56:00 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
Message-ID: <aa7ebc8d-2bc6-4a85-95e5-4059018e68b7@Julf.com>

On 25/06/2024 09:14, farzaneh badii wrote:
> I also think as a matter of transparency we should announce the 
> travel slot available on the NCSG mailing list and ask NCUC members who 
> also could be the members of NPOC to apply.

I am Ok with opening it up, but if we do, it should be for all
NCSG members, but with EC reps getting preference.

	Julf



From jumaropi at yahoo.com  Tue Jun 25 15:59:47 2024
From: jumaropi at yahoo.com (Juan Manuel Rojas)
Date: Tue, 25 Jun 2024 12:59:47 +0000 (UTC)
Subject: [NCSG-EC] Changes for NPOC EC representative
References: <1766363292.5451303.1719320387207.ref@mail.yahoo.com>
Message-ID: <1766363292.5451303.1719320387207@mail.yahoo.com>

Dear all,
I am writing to inform you of a change in one of our NPOC representatives in the EC.
I would like to appoint Jean F. Queralt in place of Tapani Tarvainen.
We extend our heartfelt gratitude to Tapani for all his support, and we are confident that he will continue to share his valuable knowledge when needed.
Best regards,?Juan Manuel Rojas?NPOC Chair?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/c6590d64/attachment.htm>

From benakin at gmail.com  Tue Jun 25 16:22:08 2024
From: benakin at gmail.com (Benjamin Akinmoyeje)
Date: Tue, 25 Jun 2024 15:22:08 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
Message-ID: <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>

Dear Julf and co,
Apologies for my late response.
I do like to inform the team that NCUC would like to utilize this slot to
support  our Issue Forum for ICANN81 . The NCUC ECs were suppose to meet
today but it was postponed.\

We will reach out as soon as possible.

Kind regards,
Benjamin

On Mon, Jun 24, 2024 at 3:32?PM Johan Helsingius <julf at julf.com> wrote:

> i am a bit reluctant to open it up to all of NCUC at this point, as our
> operating procedures state that the slots are specifically for NCSG EC
> members.
>
>         Julf
>
> On 24/06/2024 14:30, farzaneh badii wrote:
> > Hi Julf,
> >
> > I suggest we open the call for travel support to NCUC. Caleb and Tapani
> > are both NCUC members and can apply.
> >
> > Farzaneh
> >
> >
> > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
> > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>> wrote:
> >
> >     NCSG has 3 travel slots for the EC - one for the (incoming) chair,
> and
> >     two that are usually used for the EC reps (one for NCUC, one for
> NPOC).
> >
> >     Form what I can gather, NCUC isn't using their EC travel slot (David
> >     is not able to travel, Farzaneh already has a slot as Councilor).
> >
> >     Would you be OK with using both slots for NPOC (Caleb and Tapani)
> >     this time?
> >
> >              Julf
> >
> >
> >
> >     _______________________________________________
> >     NCSG-EC mailing list
> >     NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/3b9d3a28/attachment.htm>

From julf at Julf.com  Tue Jun 25 16:34:35 2024
From: julf at Julf.com (Johan Helsingius)
Date: Tue, 25 Jun 2024 15:34:35 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
Message-ID: <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>

Thanks Benjamin,

Just to clarify - the slot is specifically for EC reps. Will NCUC be
changing their NCSG EC representative(s) before ICANN81 too (like
NPOC is doing)?

	Julf

On 25/06/2024 15:22, Benjamin Akinmoyeje wrote:
> Dear Julf and co,
> Apologies for my late response.
> I do like to inform the team that NCUC would like to utilize this slot 
> to support? our Issue Forum for ICANN81 . The NCUC ECs were suppose to 
> meet today but it was postponed.\
> 
> We will reach out as soon as?possible.
> 
> Kind?regards,
> Benjamin
> 
> On Mon, Jun 24, 2024 at 3:32?PM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     i am a bit reluctant to open it up to all of NCUC at this point, as our
>     operating procedures state that the slots are specifically for NCSG EC
>     members.
> 
>      ? ? ? ? Julf
> 
>     On 24/06/2024 14:30, farzaneh badii wrote:
>      > Hi Julf,
>      >
>      > I suggest we open the call for travel support to NCUC. Caleb and
>     Tapani
>      > are both NCUC members and can apply.
>      >
>      > Farzaneh
>      >
>      >
>      > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
>      > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>> wrote:
>      >
>      >? ? ?NCSG has 3 travel slots for the EC - one for the (incoming)
>     chair, and
>      >? ? ?two that are usually used for the EC reps (one for NCUC, one
>     for NPOC).
>      >
>      >? ? ?Form what I can gather, NCUC isn't using their EC travel slot
>     (David
>      >? ? ?is not able to travel, Farzaneh already has a slot as Councilor).
>      >
>      >? ? ?Would you be OK with using both slots for NPOC (Caleb and Tapani)
>      >? ? ?this time?
>      >
>      >? ? ? ? ? ? ? Julf
>      >
>      >
>      >
>      >? ? ?_______________________________________________
>      >? ? ?NCSG-EC mailing list
>      > NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>
>      > https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>
>      >
> 


From benakin at gmail.com  Tue Jun 25 16:49:31 2024
From: benakin at gmail.com (Benjamin Akinmoyeje)
Date: Tue, 25 Jun 2024 15:49:31 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
 <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>
Message-ID: <CAJR4JuEgd6bOw5JZBr2NxeJEjr=8JCx--FG6T435uELPP34Qog@mail.gmail.com>

Dear Johan,
This is a conversation that NCUC EC must have.
I do not think it is a unilateral decision.

The NCUC EC will discuss and we will inform the community. Please let me
consult and I will get back to you.

Kind regards,
Benjamin

On Tue, Jun 25, 2024 at 3:34?PM Johan Helsingius <julf at julf.com> wrote:

> Thanks Benjamin,
>
> Just to clarify - the slot is specifically for EC reps. Will NCUC be
> changing their NCSG EC representative(s) before ICANN81 too (like
> NPOC is doing)?
>
>         Julf
>
> On 25/06/2024 15:22, Benjamin Akinmoyeje wrote:
> > Dear Julf and co,
> > Apologies for my late response.
> > I do like to inform the team that NCUC would like to utilize this slot
> > to support  our Issue Forum for ICANN81 . The NCUC ECs were suppose to
> > meet today but it was postponed.\
> >
> > We will reach out as soon as possible.
> >
> > Kind regards,
> > Benjamin
> >
> > On Mon, Jun 24, 2024 at 3:32?PM Johan Helsingius <julf at julf.com
> > <mailto:julf at julf.com>> wrote:
> >
> >     i am a bit reluctant to open it up to all of NCUC at this point, as
> our
> >     operating procedures state that the slots are specifically for NCSG
> EC
> >     members.
> >
> >              Julf
> >
> >     On 24/06/2024 14:30, farzaneh badii wrote:
> >      > Hi Julf,
> >      >
> >      > I suggest we open the call for travel support to NCUC. Caleb and
> >     Tapani
> >      > are both NCUC members and can apply.
> >      >
> >      > Farzaneh
> >      >
> >      >
> >      > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
> >      > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
> >     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>>
> wrote:
> >      >
> >      >     NCSG has 3 travel slots for the EC - one for the (incoming)
> >     chair, and
> >      >     two that are usually used for the EC reps (one for NCUC, one
> >     for NPOC).
> >      >
> >      >     Form what I can gather, NCUC isn't using their EC travel slot
> >     (David
> >      >     is not able to travel, Farzaneh already has a slot as
> Councilor).
> >      >
> >      >     Would you be OK with using both slots for NPOC (Caleb and
> Tapani)
> >      >     this time?
> >      >
> >      >              Julf
> >      >
> >      >
> >      >
> >      >     _______________________________________________
> >      >     NCSG-EC mailing list
> >      > NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>
> >      > https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>
> >      >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240625/d8fd0577/attachment.htm>

From ncsg at tapani.tarvainen.info  Tue Jun 25 17:43:17 2024
From: ncsg at tapani.tarvainen.info (Tapani Tarvainen)
Date: Tue, 25 Jun 2024 17:43:17 +0300
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
Message-ID: <ZnrXhZ9GCC28MwtV@saukko.tarvainen.info>

On Tue, Jun 25, 2024 at 09:14:46AM +0200, farzaneh badii (farzaneh.badii at gmail.com) wrote:

> I don?t think NPOC NCSG EC reps should decide for NCUC NCSG EC reps
> travel slots.

Julf's interpretation of the procedure doesn't actually mean that,
because constituencies can change their NCSG EC representatives at any
time, even at a short notice, as you have seen.

What it does mean is that whoever gets to travel on NCSG EC travel
slot should also take over NCSG EC representative's tasks, participate
in NCSG EC meetings &c. Which sounds perfectly reasonable to me.

Cheers,

-- 
Tapani Tarvainen


From julf at Julf.com  Wed Jun 26 10:18:05 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 26 Jun 2024 09:18:05 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAJR4JuEgd6bOw5JZBr2NxeJEjr=8JCx--FG6T435uELPP34Qog@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
 <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>
 <CAJR4JuEgd6bOw5JZBr2NxeJEjr=8JCx--FG6T435uELPP34Qog@mail.gmail.com>
Message-ID: <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com>

Dear Benjamin,

Please let us know what the NCUC EC decides, as we would like to nail
down the travel slots as soon as possible (we already had to submit
the list of names for the request for a NCPH 0-day, for example).

	Julf


On 25/06/2024 15:49, Benjamin Akinmoyeje wrote:
> Dear?Johan,
> This is a conversation that NCUC EC must have.
> I do not think it is a unilateral decision.
> 
> The NCUC EC will discuss and we will inform the community. Please let me 
> consult and I will get back to you.
> 
> Kind regards,
> Benjamin
> 
> On Tue, Jun 25, 2024 at 3:34?PM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     Thanks Benjamin,
> 
>     Just to clarify - the slot is specifically for EC reps. Will NCUC be
>     changing their NCSG EC representative(s) before ICANN81 too (like
>     NPOC is doing)?
> 
>      ? ? ? ? Julf
> 
>     On 25/06/2024 15:22, Benjamin Akinmoyeje wrote:
>      > Dear Julf and co,
>      > Apologies for my late response.
>      > I do like to inform the team that NCUC would like to utilize this
>     slot
>      > to support? our Issue Forum for ICANN81 . The NCUC ECs were
>     suppose to
>      > meet today but it was postponed.\
>      >
>      > We will reach out as soon as?possible.
>      >
>      > Kind?regards,
>      > Benjamin
>      >
>      > On Mon, Jun 24, 2024 at 3:32?PM Johan Helsingius <julf at julf.com
>     <mailto:julf at julf.com>
>      > <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
>      >
>      >? ? ?i am a bit reluctant to open it up to all of NCUC at this
>     point, as our
>      >? ? ?operating procedures state that the slots are specifically
>     for NCSG EC
>      >? ? ?members.
>      >
>      >? ? ? ? ? ? ? Julf
>      >
>      >? ? ?On 24/06/2024 14:30, farzaneh badii wrote:
>      >? ? ? > Hi Julf,
>      >? ? ? >
>      >? ? ? > I suggest we open the call for travel support to NCUC.
>     Caleb and
>      >? ? ?Tapani
>      >? ? ? > are both NCUC members and can apply.
>      >? ? ? >
>      >? ? ? > Farzaneh
>      >? ? ? >
>      >? ? ? >
>      >? ? ? > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via NCSG-EC
>      >? ? ? > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>
>      >? ? ?<mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>>> wrote:
>      >? ? ? >
>      >? ? ? >? ? ?NCSG has 3 travel slots for the EC - one for the
>     (incoming)
>      >? ? ?chair, and
>      >? ? ? >? ? ?two that are usually used for the EC reps (one for
>     NCUC, one
>      >? ? ?for NPOC).
>      >? ? ? >
>      >? ? ? >? ? ?Form what I can gather, NCUC isn't using their EC
>     travel slot
>      >? ? ?(David
>      >? ? ? >? ? ?is not able to travel, Farzaneh already has a slot as
>     Councilor).
>      >? ? ? >
>      >? ? ? >? ? ?Would you be OK with using both slots for NPOC (Caleb
>     and Tapani)
>      >? ? ? >? ? ?this time?
>      >? ? ? >
>      >? ? ? >? ? ? ? ? ? ? Julf
>      >? ? ? >
>      >? ? ? >
>      >? ? ? >
>      >? ? ? >? ? ?_______________________________________________
>      >? ? ? >? ? ?NCSG-EC mailing list
>      >? ? ? > NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>
>      >? ? ?<mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>>
>      >? ? ? > https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>
>      >? ? ? >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>>
>      >? ? ? >
>      >
> 


From julf at Julf.com  Wed Jun 26 10:19:10 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 26 Jun 2024 09:19:10 +0200
Subject: [NCSG-EC] Changes for NPOC EC representative
In-Reply-To: <1766363292.5451303.1719320387207@mail.yahoo.com>
References: <1766363292.5451303.1719320387207.ref@mail.yahoo.com>
 <1766363292.5451303.1719320387207@mail.yahoo.com>
Message-ID: <8f2595b6-b18b-43b1-91a1-434b9779231a@Julf.com>

Dear Juan,

Is this with immediate effect (just so that I know to update the
mailing lists and other information)?

	Julf


On 25/06/2024 14:59, Juan Manuel Rojas via NCSG-EC wrote:
> Dear all,
> 
> I am writing to inform you of a change in one of our NPOC 
> representatives in the EC.
> 
> I would like to appoint Jean F. Queralt in place of Tapani Tarvainen.
> 
> We extend our heartfelt gratitude to Tapani for all his support, and we 
> are confident that he will continue to share his valuable knowledge when 
> needed.
> 
> Best regards,
> Juan Manuel Rojas
> NPOC Chair
> 
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec


From julf at Julf.com  Wed Jun 26 11:51:24 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 26 Jun 2024 10:51:24 +0200
Subject: [NCSG-EC] Fwd: [SOAC-Leaders-ICANNMeeting-Planning] Re: ICANN81
 Block Schedule, Production Timeline
In-Reply-To: <BB136AC0-2366-4677-8B66-A9522C57341E@icann.org>
References: <BB136AC0-2366-4677-8B66-A9522C57341E@icann.org>
Message-ID: <017d28e8-25f1-438e-8ee0-e7ae9f5f5da8@Julf.com>

FYI...

	Julf

-------- Forwarded Message --------
Subject: 	[SOAC-Leaders-ICANNMeeting-Planning] Re: ICANN81 Block 
Schedule, Production Timeline
Date: 	Wed, 26 Jun 2024 08:13:12 +0000
From: 	Nathalie Peregrine via SOAC-Leaders-ICANNMeeting-Planning 
<soac-leaders-icannmeeting-planning at icann.org>
Reply-To: 	Nathalie Peregrine <nathalie.peregrine at icann.org>
To: 	soac-leaders-icannmeeting-planning at icann.org 
<soac-leaders-icannmeeting-planning at icann.org>



Dear all,

Ahead of our first ICANN81 Production call scheduled later today at 
17:30 UTC, the Schedule team would like to share an updated version of 
the previously circulated ICANN81 Block Schedule.

Notable changes are:

*Monday*

The Welcome Ceremony has now been extended to 75 mins rather than the 
initially scheduled 60 mins. This is to allow for sufficient time for 
the Tarek Kamal Award. The 30 min break is preserved to allow for room 
re-set for the following session, the Q&A with ICANN org Executives, 
which will now run for 75 mins instead of the previously scheduled 90 mins.

*Thursday*

The schedule will end at 17:30 local time, instead of the previously 
scheduled 16:00 end time in keeping with habitual planning. This will 
also allow for the Board Placeholder session should it be required.

The updated document as well as the previously circulated Production 
Timeline are attached to this email.

Looking forward to discussing this further with you all later today!

Thank you!

Nathalie, on behalf of the Schedule Team.

*From: *Nathalie Peregrine <nathalie.peregrine at icann.org>
*Date: *Wednesday, 22 May 2024 at 22:13
*To: *"soac-leaders-icannmeeting-planning at icann.org" 
<soac-leaders-icannmeeting-planning at icann.org>
*Subject: *ICANN81 Block Schedule, Production Timeline

Dear all,

Whilst you are all busy planning for ICANN80, staff support thought it 
might be helpful for you to have access to the ICANN81 draft block 
schedule and production timeline ahead of time. ICANN81 will take place 
in Istanbul from the 9 ? 14 November 2024.

As most of you know, planning for an ICANN meeting would traditionally 
start at the end of the previous ICANN meeting for the next one. There 
are many benefits to starting planning earlier, this allows for more 
discussions about topics, new session formats and ought to make outreach 
and engagement efforts easier.

Holding ICANN81 Production Calls prior to ICANN80 may be confusing, but 
having access to a proposed block schedule and production timeline could 
trigger discussions within your own groups but also on this ICANN 
meeting planning mailing list. It may also assist with session agenda 
planning for ICANN80.

Please bear in mind the following:

   * The draft block schedule follows a thought process stemming from
     what worked at previous AGMs and equally other ICANN meetings. It
     can however be modified and tweaked according to your collective input
   * The production timeline shows an estimate of the deadlines by which
     scheduling steps should have taken place. If we can be ahead of the
     production timeline (for instance, the sharing of the block schedule
     and timeline before ICANN80), this will free up more Production Call
     time for discussion.

Please do not hesitate to provide your input here, your questions, your 
ideas for ICANN81.

We look forward to working with you on the AGM!

Kind regards,

The Schedule Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN81- AGM Istanbul DRAFT v.2 26 June 2024 - Sheet1.pdf
Type: application/pdf
Size: 58470 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240626/25f5eb22/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ICANN81 Production Timeline.pdf
Type: application/pdf
Size: 75225 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240626/25f5eb22/attachment-0001.pdf>
-------------- next part --------------
_______________________________________________
SOAC-Leaders-ICANNMeeting-Planning mailing list -- soac-leaders-icannmeeting-planning at icann.org
To unsubscribe send an email to soac-leaders-icannmeeting-planning-leave at icann.org

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

From benakin at gmail.com  Wed Jun 26 15:15:04 2024
From: benakin at gmail.com (Benjamin Akinmoyeje)
Date: Wed, 26 Jun 2024 14:15:04 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
 <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>
 <CAJR4JuEgd6bOw5JZBr2NxeJEjr=8JCx--FG6T435uELPP34Qog@mail.gmail.com>
 <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com>
Message-ID: <CAJR4JuF6iDE0QRRyLsgBiwMKLEM8H-Wt+Rap0=3bc3RogUqmOQ@mail.gmail.com>

Dear Julf,
Thank you for being so patient.

We recommend Pedro as one who can take up the slot.

Kind regards,
Benjamin

On Wed, Jun 26, 2024 at 9:18?AM Johan Helsingius <julf at julf.com> wrote:

> Dear Benjamin,
>
> Please let us know what the NCUC EC decides, as we would like to nail
> down the travel slots as soon as possible (we already had to submit
> the list of names for the request for a NCPH 0-day, for example).
>
>         Julf
>
>
> On 25/06/2024 15:49, Benjamin Akinmoyeje wrote:
> > Dear Johan,
> > This is a conversation that NCUC EC must have.
> > I do not think it is a unilateral decision.
> >
> > The NCUC EC will discuss and we will inform the community. Please let me
> > consult and I will get back to you.
> >
> > Kind regards,
> > Benjamin
> >
> > On Tue, Jun 25, 2024 at 3:34?PM Johan Helsingius <julf at julf.com
> > <mailto:julf at julf.com>> wrote:
> >
> >     Thanks Benjamin,
> >
> >     Just to clarify - the slot is specifically for EC reps. Will NCUC be
> >     changing their NCSG EC representative(s) before ICANN81 too (like
> >     NPOC is doing)?
> >
> >              Julf
> >
> >     On 25/06/2024 15:22, Benjamin Akinmoyeje wrote:
> >      > Dear Julf and co,
> >      > Apologies for my late response.
> >      > I do like to inform the team that NCUC would like to utilize this
> >     slot
> >      > to support  our Issue Forum for ICANN81 . The NCUC ECs were
> >     suppose to
> >      > meet today but it was postponed.\
> >      >
> >      > We will reach out as soon as possible.
> >      >
> >      > Kind regards,
> >      > Benjamin
> >      >
> >      > On Mon, Jun 24, 2024 at 3:32?PM Johan Helsingius <julf at julf.com
> >     <mailto:julf at julf.com>
> >      > <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
> >      >
> >      >     i am a bit reluctant to open it up to all of NCUC at this
> >     point, as our
> >      >     operating procedures state that the slots are specifically
> >     for NCSG EC
> >      >     members.
> >      >
> >      >              Julf
> >      >
> >      >     On 24/06/2024 14:30, farzaneh badii wrote:
> >      >      > Hi Julf,
> >      >      >
> >      >      > I suggest we open the call for travel support to NCUC.
> >     Caleb and
> >      >     Tapani
> >      >      > are both NCUC members and can apply.
> >      >      >
> >      >      > Farzaneh
> >      >      >
> >      >      >
> >      >      > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius via
> NCSG-EC
> >      >      > <ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
> >     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>
> >      >     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
> >     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>>>
> wrote:
> >      >      >
> >      >      >     NCSG has 3 travel slots for the EC - one for the
> >     (incoming)
> >      >     chair, and
> >      >      >     two that are usually used for the EC reps (one for
> >     NCUC, one
> >      >     for NPOC).
> >      >      >
> >      >      >     Form what I can gather, NCUC isn't using their EC
> >     travel slot
> >      >     (David
> >      >      >     is not able to travel, Farzaneh already has a slot as
> >     Councilor).
> >      >      >
> >      >      >     Would you be OK with using both slots for NPOC (Caleb
> >     and Tapani)
> >      >      >     this time?
> >      >      >
> >      >      >              Julf
> >      >      >
> >      >      >
> >      >      >
> >      >      >     _______________________________________________
> >      >      >     NCSG-EC mailing list
> >      >      > NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>
> >      >     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>>
> >      >      > https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>
> >      >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>>
> >      >      >
> >      >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240626/5f6b4b10/attachment.htm>

From julf at Julf.com  Wed Jun 26 15:41:31 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 26 Jun 2024 14:41:31 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAJR4JuF6iDE0QRRyLsgBiwMKLEM8H-Wt+Rap0=3bc3RogUqmOQ@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
 <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>
 <CAJR4JuEgd6bOw5JZBr2NxeJEjr=8JCx--FG6T435uELPP34Qog@mail.gmail.com>
 <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com>
 <CAJR4JuF6iDE0QRRyLsgBiwMKLEM8H-Wt+Rap0=3bc3RogUqmOQ@mail.gmail.com>
Message-ID: <221dd75a-7fc9-44ec-a554-5f2e6ce674cd@Julf.com>

Thanks, Benjamin. As he isn't an NCSG EC representative, we will
have to issue an open call and he can apply - and we will note
your recommendation.

	Julf


On 26/06/2024 14:15, Benjamin Akinmoyeje wrote:
> Dear Julf,
> Thank you for being so patient.
> 
> We recommend Pedro as one who can take up the slot.
> 
> Kind regards,
> Benjamin
> 
> On Wed, Jun 26, 2024 at 9:18?AM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     Dear Benjamin,
> 
>     Please let us know what the NCUC EC decides, as we would like to nail
>     down the travel slots as soon as possible (we already had to submit
>     the list of names for the request for a NCPH 0-day, for example).
> 
>      ? ? ? ? Julf
> 
> 
>     On 25/06/2024 15:49, Benjamin Akinmoyeje wrote:
>      > Dear?Johan,
>      > This is a conversation that NCUC EC must have.
>      > I do not think it is a unilateral decision.
>      >
>      > The NCUC EC will discuss and we will inform the community. Please
>     let me
>      > consult and I will get back to you.
>      >
>      > Kind regards,
>      > Benjamin
>      >
>      > On Tue, Jun 25, 2024 at 3:34?PM Johan Helsingius <julf at julf.com
>     <mailto:julf at julf.com>
>      > <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
>      >
>      >? ? ?Thanks Benjamin,
>      >
>      >? ? ?Just to clarify - the slot is specifically for EC reps. Will
>     NCUC be
>      >? ? ?changing their NCSG EC representative(s) before ICANN81 too (like
>      >? ? ?NPOC is doing)?
>      >
>      >? ? ? ? ? ? ? Julf
>      >
>      >? ? ?On 25/06/2024 15:22, Benjamin Akinmoyeje wrote:
>      >? ? ? > Dear Julf and co,
>      >? ? ? > Apologies for my late response.
>      >? ? ? > I do like to inform the team that NCUC would like to
>     utilize this
>      >? ? ?slot
>      >? ? ? > to support? our Issue Forum for ICANN81 . The NCUC ECs were
>      >? ? ?suppose to
>      >? ? ? > meet today but it was postponed.\
>      >? ? ? >
>      >? ? ? > We will reach out as soon as?possible.
>      >? ? ? >
>      >? ? ? > Kind?regards,
>      >? ? ? > Benjamin
>      >? ? ? >
>      >? ? ? > On Mon, Jun 24, 2024 at 3:32?PM Johan Helsingius
>     <julf at julf.com <mailto:julf at julf.com>
>      >? ? ?<mailto:julf at julf.com <mailto:julf at julf.com>>
>      >? ? ? > <mailto:julf at julf.com <mailto:julf at julf.com>
>     <mailto:julf at julf.com <mailto:julf at julf.com>>>> wrote:
>      >? ? ? >
>      >? ? ? >? ? ?i am a bit reluctant to open it up to all of NCUC at this
>      >? ? ?point, as our
>      >? ? ? >? ? ?operating procedures state that the slots are specifically
>      >? ? ?for NCSG EC
>      >? ? ? >? ? ?members.
>      >? ? ? >
>      >? ? ? >? ? ? ? ? ? ? Julf
>      >? ? ? >
>      >? ? ? >? ? ?On 24/06/2024 14:30, farzaneh badii wrote:
>      >? ? ? >? ? ? > Hi Julf,
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? > I suggest we open the call for travel support to NCUC.
>      >? ? ?Caleb and
>      >? ? ? >? ? ?Tapani
>      >? ? ? >? ? ? > are both NCUC members and can apply.
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? > Farzaneh
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius
>     via NCSG-EC
>      >? ? ? >? ? ? > <ncsg-ec at lists.ncsg.is
>     <mailto:ncsg-ec at lists.ncsg.is> <mailto:ncsg-ec at lists.ncsg.is
>     <mailto:ncsg-ec at lists.ncsg.is>>
>      >? ? ?<mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>>
>      >? ? ? >? ? ?<mailto:ncsg-ec at lists.ncsg.is
>     <mailto:ncsg-ec at lists.ncsg.is> <mailto:ncsg-ec at lists.ncsg.is
>     <mailto:ncsg-ec at lists.ncsg.is>>
>      >? ? ?<mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
>     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>>>> wrote:
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? >? ? ?NCSG has 3 travel slots for the EC - one for the
>      >? ? ?(incoming)
>      >? ? ? >? ? ?chair, and
>      >? ? ? >? ? ? >? ? ?two that are usually used for the EC reps (one for
>      >? ? ?NCUC, one
>      >? ? ? >? ? ?for NPOC).
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? >? ? ?Form what I can gather, NCUC isn't using their EC
>      >? ? ?travel slot
>      >? ? ? >? ? ?(David
>      >? ? ? >? ? ? >? ? ?is not able to travel, Farzaneh already has a
>     slot as
>      >? ? ?Councilor).
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? >? ? ?Would you be OK with using both slots for NPOC
>     (Caleb
>      >? ? ?and Tapani)
>      >? ? ? >? ? ? >? ? ?this time?
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? >? ? ? ? ? ? ? Julf
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? >
>      >? ? ? >? ? ? >? ? ?_______________________________________________
>      >? ? ? >? ? ? >? ? ?NCSG-EC mailing list
>      >? ? ? >? ? ? > NCSG-EC at lists.ncsg.is
>     <mailto:NCSG-EC at lists.ncsg.is> <mailto:NCSG-EC at lists.ncsg.is
>     <mailto:NCSG-EC at lists.ncsg.is>>
>      >? ? ?<mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>>
>      >? ? ? >? ? ?<mailto:NCSG-EC at lists.ncsg.is
>     <mailto:NCSG-EC at lists.ncsg.is> <mailto:NCSG-EC at lists.ncsg.is
>     <mailto:NCSG-EC at lists.ncsg.is>>
>      >? ? ?<mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
>     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>>>
>      >? ? ? >? ? ? > https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>
>      >? ? ? >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>>
>      >? ? ? >? ? ? >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>
>      >? ? ? >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
>      >? ? ?<https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>>>
>      >? ? ? >? ? ? >
>      >? ? ? >
>      >
> 


From andrea.glandon at icann.org  Wed Jun 26 15:46:25 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Wed, 26 Jun 2024 12:46:25 +0000
Subject: [NCSG-EC] [Ext] Re:  NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
Message-ID: <312065D8-CFDB-482B-B041-36D60815F43B@icann.org>

Hello all, 

Apologies for the late response as I was out of the office yesterday.

The NCSG receives 3 travel slots (plus 6 for GNSO Councilors). Org does not specify how they are to be used, that would go to the NCSG travel procedures. NPOC & NCUC also receive 3 travel slots for their own ECs. 

Thank you!
Kind Regards, 
Andrea 








?On 6/25/24, 04:26, "Johan Helsingius" <julf at Julf.com <mailto:julf at Julf.com> <mailto:julf at Julf.com <mailto:julf at Julf.com>>> wrote:




Hi Andrea,




Can you help clarify - are the 3 NCSG EC travel slots allocated to
NCSG, or to NCUC/NPOC?




Julf








On 25/06/2024 10:24, farzaneh badii wrote:
> If that was the case then the governance of it should have been at the 
> NCSG level like the council is. But it is not. Each constituency 
> appoints their own reps and nobody can tell them how they allocated 
> their slots.
> 
> Farzaneh
> 
> 
> On Tue, Jun 25, 2024 at 10:14 AM Johan Helsingius <julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>> 
> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>> wrote:
> 
> The way I see it is that the slots are intended for EC members, and once
> on the EC, the members really represent NCSG, not NCUC/NPOC.
> 
> Julf
> 
> 
> On 25/06/2024 09:14, farzaneh badii wrote:
> > I disagree with your interpretation Julf of the operating
> procedures. I
> > find it dangerous to allocate one constituency EC travel slot to
> > another, I also think as a matter of transparency we should
> announce the
> > travel slot available on the NCSG mailing list and ask NCUC
> members who
> > also could be the members of NPOC to apply. I don?t understand
> what the
> > problem is with opening this up. And no I don?t think NPOC NCSG
> EC reps
> > should decide for NCUC NCSG EC reps travel slots. We open it up,
> Tapani
> > can apply.
> >
> > Farzaneh
> >
> >
> > On Tue, Jun 25, 2024 at 8:54 AM Johan Helsingius <julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>
> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>
> > <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>>> wrote:
> >
> > On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:
> >
> > > I believe these two travel slots belong to NCUC NCSG EC
> reps. I
> > believe
> > > the best course of action here is to provide an
> opportunity for NCUC
> > > members to apply.
> >
> > Reading the NCSG Operating Procedures rules for NCSG
> > Travel Slot Transfer,
> >
> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310 <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310 <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310>> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&amp;gt;&gt;>
> >
> > 1. The NCSG receives the following travel slots per meeting:
> >
> > a. At the annual Policy Forum and the annual Community
> Forum,
> > the NCSG receives 6 slots for Council members, and 3
> slots
> > for NCSG Executive Committee members, being a total of 9
> > travel slots.
> >
> > b. At the Annual General Meeting, the NCSG receives
> travel slots
> > for all incoming and outgoing Councilors (a minimum
> of 6 slots
> > and a maximum of 9 slots, depending on whether or not new
> > persons are rotating into the Council) as well as 3
> travel
> > slots to be allocated to the to NCSG Executive Committee.
> >
> > So the 3 travel slots belong to the EC. Usually one slot is for
> > the (incoming) chair, and one each to a NCUC and a NPOC rep. Only
> > if EC members are unable to use the slots are they offered to
> > the wider membership. In this case two of the four EC reps
> > can use the slots - but they both happen to be from NPOC.
> >
> > Julf
> >
> 








From julf at Julf.com  Wed Jun 26 16:16:12 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 26 Jun 2024 15:16:12 +0200
Subject: [NCSG-EC] [Ext] Re:  NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <312065D8-CFDB-482B-B041-36D60815F43B@icann.org>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
 <312065D8-CFDB-482B-B041-36D60815F43B@icann.org>
Message-ID: <240d77af-bda5-4107-9a38-fadab949b09e@Julf.com>

Thank you for the clarification, Andrea!

	Julf


On 26/06/2024 14:46, Andrea Glandon wrote:
> Hello all,
> 
> Apologies for the late response as I was out of the office yesterday.
> 
> The NCSG receives 3 travel slots (plus 6 for GNSO Councilors). Org does not specify how they are to be used, that would go to the NCSG travel procedures. NPOC & NCUC also receive 3 travel slots for their own ECs.
> 
> Thank you!
> Kind Regards,
> Andrea
> 
> 
> 
> 
> 
> 
> 
> 
> ?On 6/25/24, 04:26, "Johan Helsingius" <julf at Julf.com <mailto:julf at Julf.com> <mailto:julf at Julf.com <mailto:julf at Julf.com>>> wrote:
> 
> 
> 
> 
> Hi Andrea,
> 
> 
> 
> 
> Can you help clarify - are the 3 NCSG EC travel slots allocated to
> NCSG, or to NCUC/NPOC?
> 
> 
> 
> 
> Julf
> 
> 
> 
> 
> 
> 
> 
> 
> On 25/06/2024 10:24, farzaneh badii wrote:
>> If that was the case then the governance of it should have been at the
>> NCSG level like the council is. But it is not. Each constituency
>> appoints their own reps and nobody can tell them how they allocated
>> their slots.
>>
>> Farzaneh
>>
>>
>> On Tue, Jun 25, 2024 at 10:14 AM Johan Helsingius <julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>
>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>> wrote:
>>
>> The way I see it is that the slots are intended for EC members, and once
>> on the EC, the members really represent NCSG, not NCUC/NPOC.
>>
>> Julf
>>
>>
>> On 25/06/2024 09:14, farzaneh badii wrote:
>>> I disagree with your interpretation Julf of the operating
>> procedures. I
>>> find it dangerous to allocate one constituency EC travel slot to
>>> another, I also think as a matter of transparency we should
>> announce the
>>> travel slot available on the NCSG mailing list and ask NCUC
>> members who
>>> also could be the members of NPOC to apply. I don?t understand
>> what the
>>> problem is with opening this up. And no I don?t think NPOC NCSG
>> EC reps
>>> should decide for NCUC NCSG EC reps travel slots. We open it up,
>> Tapani
>>> can apply.
>>>
>>> Farzaneh
>>>
>>>
>>> On Tue, Jun 25, 2024 at 8:54 AM Johan Helsingius <julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>
>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>
>>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>>> wrote:
>>>
>>> On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:
>>>
>>>> I believe these two travel slots belong to NCUC NCSG EC
>> reps. I
>>> believe
>>>> the best course of action here is to provide an
>> opportunity for NCUC
>>>> members to apply.
>>>
>>> Reading the NCSG Operating Procedures rules for NCSG
>>> Travel Slot Transfer,
>>>
>> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310 <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310 <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310>> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&amp;gt;&gt;>
>>>
>>> 1. The NCSG receives the following travel slots per meeting:
>>>
>>> a. At the annual Policy Forum and the annual Community
>> Forum,
>>> the NCSG receives 6 slots for Council members, and 3
>> slots
>>> for NCSG Executive Committee members, being a total of 9
>>> travel slots.
>>>
>>> b. At the Annual General Meeting, the NCSG receives
>> travel slots
>>> for all incoming and outgoing Councilors (a minimum
>> of 6 slots
>>> and a maximum of 9 slots, depending on whether or not new
>>> persons are rotating into the Council) as well as 3
>> travel
>>> slots to be allocated to the to NCSG Executive Committee.
>>>
>>> So the 3 travel slots belong to the EC. Usually one slot is for
>>> the (incoming) chair, and one each to a NCUC and a NPOC rep. Only
>>> if EC members are unable to use the slots are they offered to
>>> the wider membership. In this case two of the four EC reps
>>> can use the slots - but they both happen to be from NPOC.
>>>
>>> Julf
>>>
>>
> 
> 
> 
> 
> 
> 
> 

From andrea.glandon at icann.org  Wed Jun 26 16:17:01 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Wed, 26 Jun 2024 13:17:01 +0000
Subject: [NCSG-EC] [Ext] Re:  NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <240d77af-bda5-4107-9a38-fadab949b09e@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAL_ZvK4pWUBKpSLYyHA5jdUxAtYdZQsv92sFCyqAcVJY3OFgvw@mail.gmail.com>
 <CAN1qJvA1zPrm5GsW04EvGBW13rT-G3jjjumHNrrOiZtKukHN2Q@mail.gmail.com>
 <ZnpPltfTuA84Fi1w@saukko.tarvainen.info>
 <CAN1qJvBetN4JRdNoYWdC4uL7xCZ1jM7ejyKEy6ToUZ1y_3X4bQ@mail.gmail.com>
 <d3e0efae-ad06-405d-8fff-ac434c8bfcf0@Julf.com>
 <CAN1qJvAWeuQJmSt-KZPpRFzNMH+TqSFLj7O8C5-JBgYNh4vXWg@mail.gmail.com>
 <4bd71cff-7951-49c2-97c8-3f0d3dce568c@Julf.com>
 <CAN1qJvD8ZZfuc90veFkRafNhdtH69LzUhDKo9srQqG_RRu9AmQ@mail.gmail.com>
 <c8a8f67f-f267-493b-983c-937672b98e37@Julf.com>
 <312065D8-CFDB-482B-B041-36D60815F43B@icann.org>
 <240d77af-bda5-4107-9a38-fadab949b09e@Julf.com>
Message-ID: <8B3EBF3B-B816-4EAD-A077-FC154A50822C@icann.org>

You're welcome!

Kind Regards, 
Andrea 




?On 6/26/24, 08:16, "Johan Helsingius" <julf at Julf.com <mailto:julf at Julf.com>> wrote:


Thank you for the clarification, Andrea!


Julf




On 26/06/2024 14:46, Andrea Glandon wrote:
> Hello all,
> 
> Apologies for the late response as I was out of the office yesterday.
> 
> The NCSG receives 3 travel slots (plus 6 for GNSO Councilors). Org does not specify how they are to be used, that would go to the NCSG travel procedures. NPOC & NCUC also receive 3 travel slots for their own ECs.
> 
> Thank you!
> Kind Regards,
> Andrea
> 
> 
> 
> 
> 
> 
> 
> 
> On 6/25/24, 04:26, "Johan Helsingius" <julf at Julf.com <mailto:julf at Julf.com> <mailto:julf at Julf.com <mailto:julf at Julf.com>> <mailto:julf at Julf.com <mailto:julf at Julf.com> <mailto:julf at Julf.com <mailto:julf at Julf.com>>>> wrote:
> 
> 
> 
> 
> Hi Andrea,
> 
> 
> 
> 
> Can you help clarify - are the 3 NCSG EC travel slots allocated to
> NCSG, or to NCUC/NPOC?
> 
> 
> 
> 
> Julf
> 
> 
> 
> 
> 
> 
> 
> 
> On 25/06/2024 10:24, farzaneh badii wrote:
>> If that was the case then the governance of it should have been at the
>> NCSG level like the council is. But it is not. Each constituency
>> appoints their own reps and nobody can tell them how they allocated
>> their slots.
>>
>> Farzaneh
>>
>>
>> On Tue, Jun 25, 2024 at 10:14 AM Johan Helsingius <julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>
>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>>> wrote:
>>
>> The way I see it is that the slots are intended for EC members, and once
>> on the EC, the members really represent NCSG, not NCUC/NPOC.
>>
>> Julf
>>
>>
>> On 25/06/2024 09:14, farzaneh badii wrote:
>>> I disagree with your interpretation Julf of the operating
>> procedures. I
>>> find it dangerous to allocate one constituency EC travel slot to
>>> another, I also think as a matter of transparency we should
>> announce the
>>> travel slot available on the NCSG mailing list and ask NCUC
>> members who
>>> also could be the members of NPOC to apply. I don?t understand
>> what the
>>> problem is with opening this up. And no I don?t think NPOC NCSG
>> EC reps
>>> should decide for NCUC NCSG EC reps travel slots. We open it up,
>> Tapani
>>> can apply.
>>>
>>> Farzaneh
>>>
>>>
>>> On Tue, Jun 25, 2024 at 8:54 AM Johan Helsingius <julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>
>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>>
>>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>> <mailto:julf at julf.com <mailto:julf at julf.com> <mailto:julf at julf.com <mailto:julf at julf.com>>>>>> wrote:
>>>
>>> On 25/06/2024 07:48, farzaneh badii via NCSG-EC wrote:
>>>
>>>> I believe these two travel slots belong to NCUC NCSG EC
>> reps. I
>>> believe
>>>> the best course of action here is to provide an
>> opportunity for NCUC
>>>> members to apply.
>>>
>>> Reading the NCSG Operating Procedures rules for NCSG
>>> Travel Slot Transfer,
>>>
>> https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310 <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;amp;gt;&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310 <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310>> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;gt;&amp;gt;&gt;> <https://community.icann.org/display/gnsononcomstake/Operating+Procedures#OperatingProcedures-996937310&amp;amp;gt;&amp;amp;gt;&amp;gt;&gt;>
>>>
>>> 1. The NCSG receives the following travel slots per meeting:
>>>
>>> a. At the annual Policy Forum and the annual Community
>> Forum,
>>> the NCSG receives 6 slots for Council members, and 3
>> slots
>>> for NCSG Executive Committee members, being a total of 9
>>> travel slots.
>>>
>>> b. At the Annual General Meeting, the NCSG receives
>> travel slots
>>> for all incoming and outgoing Councilors (a minimum
>> of 6 slots
>>> and a maximum of 9 slots, depending on whether or not new
>>> persons are rotating into the Council) as well as 3
>> travel
>>> slots to be allocated to the to NCSG Executive Committee.
>>>
>>> So the 3 travel slots belong to the EC. Usually one slot is for
>>> the (incoming) chair, and one each to a NCUC and a NPOC rep. Only
>>> if EC members are unable to use the slots are they offered to
>>> the wider membership. In this case two of the four EC reps
>>> can use the slots - but they both happen to be from NPOC.
>>>
>>> Julf
>>>
>>
> 
> 
> 
> 
> 
> 
> 




From benakin at gmail.com  Wed Jun 26 16:49:16 2024
From: benakin at gmail.com (Benjamin Akinmoyeje)
Date: Wed, 26 Jun 2024 15:49:16 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <221dd75a-7fc9-44ec-a554-5f2e6ce674cd@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
 <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>
 <CAJR4JuEgd6bOw5JZBr2NxeJEjr=8JCx--FG6T435uELPP34Qog@mail.gmail.com>
 <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com>
 <CAJR4JuF6iDE0QRRyLsgBiwMKLEM8H-Wt+Rap0=3bc3RogUqmOQ@mail.gmail.com>
 <221dd75a-7fc9-44ec-a554-5f2e6ce674cd@Julf.com>
Message-ID: <CAJR4JuFN=JTJ8Q7rRaJCat+wY+PTaeTTSr-MLWQOAs0us=-cdA@mail.gmail.com>

Hello Julf,
Please why can't Pedro be an NCSG EC?

You mentioned you want an NCUC  EC, and he can be our NCSG interim EC, that
is the path we would like to take.


Pedro is our NCSG EC since others are indisposed.

Kind regards,
Benjamin

On Wed, Jun 26, 2024, 2:41?PM Johan Helsingius <julf at julf.com> wrote:

> Thanks, Benjamin. As he isn't an NCSG EC representative, we will
> have to issue an open call and he can apply - and we will note
> your recommendation.
>
>         Julf
>
>
> On 26/06/2024 14:15, Benjamin Akinmoyeje wrote:
> > Dear Julf,
> > Thank you for being so patient.
> >
> > We recommend Pedro as one who can take up the slot.
> >
> > Kind regards,
> > Benjamin
> >
> > On Wed, Jun 26, 2024 at 9:18?AM Johan Helsingius <julf at julf.com
> > <mailto:julf at julf.com>> wrote:
> >
> >     Dear Benjamin,
> >
> >     Please let us know what the NCUC EC decides, as we would like to nail
> >     down the travel slots as soon as possible (we already had to submit
> >     the list of names for the request for a NCPH 0-day, for example).
> >
> >              Julf
> >
> >
> >     On 25/06/2024 15:49, Benjamin Akinmoyeje wrote:
> >      > Dear Johan,
> >      > This is a conversation that NCUC EC must have.
> >      > I do not think it is a unilateral decision.
> >      >
> >      > The NCUC EC will discuss and we will inform the community. Please
> >     let me
> >      > consult and I will get back to you.
> >      >
> >      > Kind regards,
> >      > Benjamin
> >      >
> >      > On Tue, Jun 25, 2024 at 3:34?PM Johan Helsingius <julf at julf.com
> >     <mailto:julf at julf.com>
> >      > <mailto:julf at julf.com <mailto:julf at julf.com>>> wrote:
> >      >
> >      >     Thanks Benjamin,
> >      >
> >      >     Just to clarify - the slot is specifically for EC reps. Will
> >     NCUC be
> >      >     changing their NCSG EC representative(s) before ICANN81 too
> (like
> >      >     NPOC is doing)?
> >      >
> >      >              Julf
> >      >
> >      >     On 25/06/2024 15:22, Benjamin Akinmoyeje wrote:
> >      >      > Dear Julf and co,
> >      >      > Apologies for my late response.
> >      >      > I do like to inform the team that NCUC would like to
> >     utilize this
> >      >     slot
> >      >      > to support  our Issue Forum for ICANN81 . The NCUC ECs were
> >      >     suppose to
> >      >      > meet today but it was postponed.\
> >      >      >
> >      >      > We will reach out as soon as possible.
> >      >      >
> >      >      > Kind regards,
> >      >      > Benjamin
> >      >      >
> >      >      > On Mon, Jun 24, 2024 at 3:32?PM Johan Helsingius
> >     <julf at julf.com <mailto:julf at julf.com>
> >      >     <mailto:julf at julf.com <mailto:julf at julf.com>>
> >      >      > <mailto:julf at julf.com <mailto:julf at julf.com>
> >     <mailto:julf at julf.com <mailto:julf at julf.com>>>> wrote:
> >      >      >
> >      >      >     i am a bit reluctant to open it up to all of NCUC at
> this
> >      >     point, as our
> >      >      >     operating procedures state that the slots are
> specifically
> >      >     for NCSG EC
> >      >      >     members.
> >      >      >
> >      >      >              Julf
> >      >      >
> >      >      >     On 24/06/2024 14:30, farzaneh badii wrote:
> >      >      >      > Hi Julf,
> >      >      >      >
> >      >      >      > I suggest we open the call for travel support to
> NCUC.
> >      >     Caleb and
> >      >      >     Tapani
> >      >      >      > are both NCUC members and can apply.
> >      >      >      >
> >      >      >      > Farzaneh
> >      >      >      >
> >      >      >      >
> >      >      >      > On Mon, Jun 24, 2024 at 1:15?PM Johan Helsingius
> >     via NCSG-EC
> >      >      >      > <ncsg-ec at lists.ncsg.is
> >     <mailto:ncsg-ec at lists.ncsg.is> <mailto:ncsg-ec at lists.ncsg.is
> >     <mailto:ncsg-ec at lists.ncsg.is>>
> >      >     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
> >     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>>
> >      >      >     <mailto:ncsg-ec at lists.ncsg.is
> >     <mailto:ncsg-ec at lists.ncsg.is> <mailto:ncsg-ec at lists.ncsg.is
> >     <mailto:ncsg-ec at lists.ncsg.is>>
> >      >     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>
> >     <mailto:ncsg-ec at lists.ncsg.is <mailto:ncsg-ec at lists.ncsg.is>>>>>
> wrote:
> >      >      >      >
> >      >      >      >     NCSG has 3 travel slots for the EC - one for the
> >      >     (incoming)
> >      >      >     chair, and
> >      >      >      >     two that are usually used for the EC reps (one
> for
> >      >     NCUC, one
> >      >      >     for NPOC).
> >      >      >      >
> >      >      >      >     Form what I can gather, NCUC isn't using their
> EC
> >      >     travel slot
> >      >      >     (David
> >      >      >      >     is not able to travel, Farzaneh already has a
> >     slot as
> >      >     Councilor).
> >      >      >      >
> >      >      >      >     Would you be OK with using both slots for NPOC
> >     (Caleb
> >      >     and Tapani)
> >      >      >      >     this time?
> >      >      >      >
> >      >      >      >              Julf
> >      >      >      >
> >      >      >      >
> >      >      >      >
> >      >      >      >     _______________________________________________
> >      >      >      >     NCSG-EC mailing list
> >      >      >      > NCSG-EC at lists.ncsg.is
> >     <mailto:NCSG-EC at lists.ncsg.is> <mailto:NCSG-EC at lists.ncsg.is
> >     <mailto:NCSG-EC at lists.ncsg.is>>
> >      >     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>>
> >      >      >     <mailto:NCSG-EC at lists.ncsg.is
> >     <mailto:NCSG-EC at lists.ncsg.is> <mailto:NCSG-EC at lists.ncsg.is
> >     <mailto:NCSG-EC at lists.ncsg.is>>
> >      >     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>
> >     <mailto:NCSG-EC at lists.ncsg.is <mailto:NCSG-EC at lists.ncsg.is>>>>
> >      >      >      > https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>
> >      >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>>
> >      >      >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>
> >      >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>
> >      >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec
> >     <https://lists.ncsg.is/mailman/listinfo/ncsg-ec>>>>
> >      >      >      >
> >      >      >
> >      >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240626/43733f40/attachment.htm>

From andrea.glandon at icann.org  Wed Jun 26 17:13:32 2024
From: andrea.glandon at icann.org (Andrea Glandon)
Date: Wed, 26 Jun 2024 14:13:32 +0000
Subject: [NCSG-EC] [Ext] Changes for NPOC EC representative
In-Reply-To: <1766363292.5451303.1719320387207@mail.yahoo.com>
References: <1766363292.5451303.1719320387207.ref@mail.yahoo.com>
 <1766363292.5451303.1719320387207@mail.yahoo.com>
Message-ID: <C27DF9C4-8051-472B-B7CD-A7BC726786A4@icann.org>

Thank you, Juan Manuel. I have updated the NCSG EC email list. I will also try to make the updates in Civi (fingers crossed they work) and I will send him the Google document that the EC has been working off of

Kind Regards,
Andrea


From: Juan Manuel Rojas <jumaropi at yahoo.com>
Reply-To: Juan Manuel Rojas <jumaropi at yahoo.com>
Date: Tuesday, June 25, 2024 at 08:00
To: NCSG EC <ncsg-ec at lists.ncsg.is>
Cc: Andrea Glandon <andrea.glandon at icann.org>, Tapani Tarvainen <ncsg at tapani.tarvainen.info>
Subject: [Ext] Changes for NPOC EC representative

Dear all,

I am writing to inform you of a change in one of our NPOC representatives in the EC.

I would like to appoint Jean F. Queralt in place of Tapani Tarvainen.

We extend our heartfelt gratitude to Tapani for all his support, and we are confident that he will continue to share his valuable knowledge when needed.

Best regards,
Juan Manuel Rojas
NPOC Chair
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240626/d827a72f/attachment.htm>

From JFQueralt at theiofoundation.org  Wed Jun 26 17:34:42 2024
From: JFQueralt at theiofoundation.org (=?UTF-8?Q?Jean_F=2E_Qu=C3=A9ralt?=)
Date: Wed, 26 Jun 2024 22:34:42 +0800
Subject: [NCSG-EC] [Ext] Changes for NPOC EC representative
In-Reply-To: <C27DF9C4-8051-472B-B7CD-A7BC726786A4@icann.org>
References: <1766363292.5451303.1719320387207.ref@mail.yahoo.com>
 <1766363292.5451303.1719320387207@mail.yahoo.com>
 <C27DF9C4-8051-472B-B7CD-A7BC726786A4@icann.org>
Message-ID: <CACuyrh_YZJDJvRgLBw5enuEXkLJGOnbTGmzBRXxvmQw7rzOLdQ@mail.gmail.com>

Hi everyone.

Thanks for the trust, @Juan Manuel Rojas <jumaropi at yahoo.com>. Looking
forward to help in the NCSG EC.

@Andrea Glandon <andrea.glandon at icann.org>, I'll be checking the document
once I am back in KL next week.
Got the NCSG Charter and the Operating Procedures to also looking into.

Best
Jean F. Queralt
Founder & CEO - The IO Foundation <http://www.TheIOFoundation.org>
Book a meeting <http://TIOF.Click/BookJFQ> (30 minutes)


On Wed, 26 Jun 2024 at 22:13, Andrea Glandon via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Thank you, Juan Manuel. I have updated the NCSG EC email list. I will also
> try to make the updates in Civi (fingers crossed they work) and I will send
> him the Google document that the EC has been working off of
>
>
>
> Kind Regards,
>
> Andrea
>
>
>
>
>
> *From: *Juan Manuel Rojas <jumaropi at yahoo.com>
> *Reply-To: *Juan Manuel Rojas <jumaropi at yahoo.com>
> *Date: *Tuesday, June 25, 2024 at 08:00
> *To: *NCSG EC <ncsg-ec at lists.ncsg.is>
> *Cc: *Andrea Glandon <andrea.glandon at icann.org>, Tapani Tarvainen <
> ncsg at tapani.tarvainen.info>
> *Subject: *[Ext] Changes for NPOC EC representative
>
>
>
> Dear all,
>
>
>
> I am writing to inform you of a change in one of our NPOC representatives
> in the EC.
>
>
>
> I would like to appoint Jean F. Queralt in place of Tapani Tarvainen.
>
>
>
> We extend our heartfelt gratitude to Tapani for all his support, and we
> are confident that he will continue to share his valuable knowledge when
> needed.
>
>
>
> Best regards,
>
> Juan Manuel Rojas
>
> NPOC Chair
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>

-- 
**DISCLAIMER**
*The content of this message, which may contain personal or 
sensitive data, is confidential. If you have received it by mistake, please 
inform the sender by replying to the email and then permanently delete the 
message, including any attachments. It is forbidden to copy, forward or in 
any way reveal the content of this message to anyone. The integrity and 
security of this email cannot be guaranteed over the Internet and, 
therefore, the sender will not be held liable for any damage caused by the 
message.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240626/8178c745/attachment.htm>

From julf at Julf.com  Wed Jun 26 18:44:15 2024
From: julf at Julf.com (Johan Helsingius)
Date: Wed, 26 Jun 2024 17:44:15 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAJR4JuFN=JTJ8Q7rRaJCat+wY+PTaeTTSr-MLWQOAs0us=-cdA@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
 <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>
 <CAJR4JuEgd6bOw5JZBr2NxeJEjr=8JCx--FG6T435uELPP34Qog@mail.gmail.com>
 <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com>
 <CAJR4JuF6iDE0QRRyLsgBiwMKLEM8H-Wt+Rap0=3bc3RogUqmOQ@mail.gmail.com>
 <221dd75a-7fc9-44ec-a554-5f2e6ce674cd@Julf.com>
 <CAJR4JuFN=JTJ8Q7rRaJCat+wY+PTaeTTSr-MLWQOAs0us=-cdA@mail.gmail.com>
Message-ID: <d92580de-b870-47db-91cc-5e26d9b5c313@Julf.com>

Hi Benjamin,

> Please why can't Pedro be an NCSG EC?

He can. of course, if the NCUC decides so.
> You mentioned you want an NCUC? EC, and he can be our NCSG interim EC, 
> that is the path we would like to take.

Interim as in "until a permanent new EC member is appointed"? Sure.
Will he replace David or Farzaneh?

	Julf



From benakin at gmail.com  Fri Jun 28 18:08:00 2024
From: benakin at gmail.com (Benjamin Akinmoyeje)
Date: Fri, 28 Jun 2024 17:08:00 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <d92580de-b870-47db-91cc-5e26d9b5c313@Julf.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
 <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>
 <CAJR4JuEgd6bOw5JZBr2NxeJEjr=8JCx--FG6T435uELPP34Qog@mail.gmail.com>
 <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com>
 <CAJR4JuF6iDE0QRRyLsgBiwMKLEM8H-Wt+Rap0=3bc3RogUqmOQ@mail.gmail.com>
 <221dd75a-7fc9-44ec-a554-5f2e6ce674cd@Julf.com>
 <CAJR4JuFN=JTJ8Q7rRaJCat+wY+PTaeTTSr-MLWQOAs0us=-cdA@mail.gmail.com>
 <d92580de-b870-47db-91cc-5e26d9b5c313@Julf.com>
Message-ID: <CAJR4JuGQZJG_GoO=0jLEvA9LN8TRu7JnHvkZSoDTgByxj5X01w@mail.gmail.com>

Dear Julf,

He will replace David.

Kind regards,
Benjamin


On Wed, Jun 26, 2024 at 5:44?PM Johan Helsingius <julf at julf.com> wrote:

> Hi Benjamin,
>
> > Please why can't Pedro be an NCSG EC?
>
> He can. of course, if the NCUC decides so.
> > You mentioned you want an NCUC  EC, and he can be our NCSG interim EC,
> > that is the path we would like to take.
>
> Interim as in "until a permanent new EC member is appointed"? Sure.
> Will he replace David or Farzaneh?
>
>         Julf
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20240628/368a1710/attachment.htm>

From julf at julf.com  Fri Jun 28 21:34:43 2024
From: julf at julf.com (Johan Helsingius)
Date: Fri, 28 Jun 2024 20:34:43 +0200
Subject: [NCSG-EC] NCSG EC travel for ICANN81 (Istanbul)
In-Reply-To: <CAJR4JuGQZJG_GoO=0jLEvA9LN8TRu7JnHvkZSoDTgByxj5X01w@mail.gmail.com>
References: <7fecb8ad-4b9d-479c-b7b6-c7a385108dab@Julf.com>
 <CAN1qJvCmRoDhC2U7t4GrQEyyBD5QMpAPXPZwEN5SW4N-Hm_cCg@mail.gmail.com>
 <518e4776-303e-4f75-b137-e49a243a8e72@Julf.com>
 <CAJR4JuHUXGHYbQK4tt=oFji_wDwzybV6w0+nxbkAE1zexmAWNQ@mail.gmail.com>
 <5b281f29-4915-445f-ba0a-e21550c2b079@Julf.com>
 <CAJR4JuEgd6bOw5JZBr2NxeJEjr=8JCx--FG6T435uELPP34Qog@mail.gmail.com>
 <2a534ff6-965a-4708-9504-b14e06af855d@Julf.com>
 <CAJR4JuF6iDE0QRRyLsgBiwMKLEM8H-Wt+Rap0=3bc3RogUqmOQ@mail.gmail.com>
 <221dd75a-7fc9-44ec-a554-5f2e6ce674cd@Julf.com>
 <CAJR4JuFN=JTJ8Q7rRaJCat+wY+PTaeTTSr-MLWQOAs0us=-cdA@mail.gmail.com>
 <d92580de-b870-47db-91cc-5e26d9b5c313@Julf.com>
 <CAJR4JuGQZJG_GoO=0jLEvA9LN8TRu7JnHvkZSoDTgByxj5X01w@mail.gmail.com>
Message-ID: <bacbac65-5dfb-4320-8709-1a7bc31fbc38@julf.com>

Dear Benjamin,

Understood. Thanks! Do you have any guess about when there would
be a permanent replacement (by Pedro or someone else)?

	Julf


On 28/06/2024 17:08, Benjamin Akinmoyeje wrote:
> Dear Julf,
> 
> He will replace David.
> 
> Kind regards,
> Benjamin
> 
> 
> On Wed, Jun 26, 2024 at 5:44?PM Johan Helsingius <julf at julf.com 
> <mailto:julf at julf.com>> wrote:
> 
>     Hi Benjamin,
> 
>      > Please why can't Pedro be an NCSG EC?
> 
>     He can. of course, if the NCUC decides so.
>      > You mentioned you want an NCUC? EC, and he can be our NCSG
>     interim EC,
>      > that is the path we would like to take.
> 
>     Interim as in "until a permanent new EC member is appointed"? Sure.
>     Will he replace David or Farzaneh?
> 
>      ? ? ? ? Julf
>