[NCUC-EC] ICANN65 | Marrakech - EC Travelers Application Due15 February 2019

David Cake dave at davecake.net
Tue Feb 19 01:57:36 CET 2019


I’ve been crazy busy, so unfortunately did not lodge my application in time, which of course is my problem not anyone elses. Antonella and Michael are fine choices. 

David

> On 19 Feb 2019, at 8:02 am, Louise Marie Hurel <louise.marie.hsd at gmail.com> wrote:
> 
> Sounds good.
> 
> Thanks for the update.
> 
> Louise Marie Hurel
> Cybersecurity and Digital Liberties Programme | Igarapé Institute
> Media and Communications (Data and Society) | London School of Economics and Political Science (LSE)
> Publications <https://www.researchgate.net/profile/Louise_Marie_Hurel/publications>
> Skype: louise.dias
> +44 (0) 7468 906327
> l.h.dias at lse.ac.uk <mailto:l.h.dias at lse.ac.uk> 
> louise.marie.hsd at gmail.com <mailto:louise.marie.hsd at gmail.com> 
> 
> 
> 
> On Mon, 18 Feb 2019 at 22:46, Bruna Martins dos Santos <bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>> wrote:
> Dear EC, 
> 
> Based on the fact that the only two EC members who sent in their complete applications within the deadline were Antonella and Michael, I will send their names to staff as the 2 EC funded travelers for Marrakech. 
> 
> best, 
> bruna 
> 
> Em sex, 15 de fev de 2019 às 17:13, Michael Karanicolas <mkaranicolas at gmail.com <mailto:mkaranicolas at gmail.com>> escreveu:
> Hi,
> 
> Apologies for the delay. Please accept the attached as my application. 
> 
> In terms of my current engagement with ICANN activities, currently I am one of a small handful non-commercial participants who is active in the RPMs WG. I have not missed a meeting of this WG over at least the past year, and I have contributed and continue to contribute written submissions to our work. RPMs typically does a great deal of business at the face to face meetings, and I am often the only non-commercial attendee in the room, apart from Kathy, whose advocacy role can be limited by her position as co-chair. These factors, and the time-zone challenges to remote participation in Marrakech, make my presence in Morocco of strong importance. I am also a member of the ATRT3 review team. While our schedule is still being established, we are planning to hold a face to face in Kobe, and there is a significant likelihood that the team will carry out similar activities in Marrakech. Third, as the rapporteur of the WS2 transparency subgroup, I am a member of the implementation team for the WS2 recommendations. Again, there is no set schedule, but it is highly likely that this will involve some face to face component in Marrakech. Fourth, I have been an active observer of ICANN's work in the open data initiative and the information transparency initiative, and a participant in conversations about progress on both of these fronts. These conversations mostly take place at ICANN meetings, so Marrakech is an important opportunity to maintain engagement here.
> 
> In terms of my plan for engagement, I will be attending two events over the next month to support NCUC outreach, namely a conference at American University on February 25, and the Canadian IGF event on February 27, both of which will be good opportunities to canvass non-commercial stakeholders for their thoughts and concerns. In terms of engagement at the meeting itself, although I am the North American rep, I am actually quite well networked in North Africa, and in Morocco in particular, and would be a good asset in terms of outreach. I have a good working relationship with both Transparency Maroc and with contacts at the Universities of Fez and Rabat-Sale, who could help to spread the word and bring in new attendees. As with previous meetings, I plan on being active on social media throughout the event, and networking constituencies to help support collaboration to achieve NCUC priorities. I am also happy to do whatever is needed to support outreach activities on site, including taking speaking, presenting or coordinating roles as necessary.
> 
> I currently have no other possible sources of funding for attending ICANN 65 and, as a graduate student, I will not be able to attend unless fully funded. Also, it's worth noting that, in addition to not requesting funding for Kobe, ICANN 66 is taking place in Montreal, fairly close to my home, so I will not need to apply for funding in the fall, and this will be the only ICANN event in 2019 where it makes sense for me to request support.
> 
> Thank you for your consideration,
> 
> Michael Karanicolas
> 
> 
> 
> On Fri, Feb 15, 2019 at 2:23 PM Bruna Martins dos Santos <bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>> wrote:
> Hey all, 
> 
> So far I've only got Antonella's application. Given that the deadline is today, I ask you to submit the applicationa asap. 
> 
> best, 
> bruna 
> 
> Em sex, 15 de fev de 2019 às 03:07, Antonella Perini <antomperini at gmail.com <mailto:antomperini at gmail.com>> escreveu:
> Dear all, 
>  
> I would like to formally express my interest for the Marrakech slot. I did not apply for the one for Kobe meeting nor will I be attending, and for the moment this is my only current option for funding.
>  
> As regards regional outreach/inreach, I’m planning on a two-step action plan, besides ongoing opportunities for outreach at DNS- or IG-related events. The first one will be taking place now after the NCUC call we had yesterday and right before Kobe. I will be personally contacting NCUC LAC members in order to understand better their current participation in ICANN and interests. That is to say, map how we are in terms of engagement in order to better design the following stage, and guide those who will be attending this first meeting of the year as well as to encourage remote participation. I hope these actions propel increasing participation of LAC members in public comments and PDPs as well.
>  
> Secondly, and here is where I believe the slot would be of great help, I would like to attend the Marrakech meeting in order to collaborate on-site this time: planning outreach activities with considerable anticipation (maybe I can help with participatory methodologies or dynamics), and help where needed, such as facilitation, presentations, assisting at the ICANN information booth and/or assisting mentees. Having said that, I believe that close collaboration with EC AF would be of great help in order to connect with local organizations and community in general. As regards regional outreach/inreach, it would be an opportunity to take more solid steps towards consolidating LAC members engagement. Having in mind that this is a Policy Meeting, steps taken during the first stage mentioned above are intended to be reflected during this meeting. 
>  
> As for my activities at ICANN, until now I have been studying quite a lot about our roles as EC, which was new to me, and I’ve been mostly focused on that. With more solid knowledge now, although there is still room for more, I want to engage with the CCWP on Human Rights. I have talked with Collin Cure during ICANN62 meeting and I am looking forward to being actively involved in this process and help where it is needed.
>  
> I hope you take my interests and intentions into consideration. I’m available if you need any further information.
>  
> Best,
>  
> Antonella.
> 
> 
> On Tue, 12 Feb 2019 at 14:09, Bruna Martins dos Santos <bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>> wrote:
> Great, 
> 
> Looking forward to reading your applications, they are due friday! 
> 
> best, 
> bruna 
> 
> Em ter, 5 de fev de 2019 às 03:32, David Cake <dave at davecake.net <mailto:dave at davecake.net>> escreveu:
> I would also like to apply to use the EC slot. 
> 
> I have not used any NCUC resources for the last two meetings, I expect to be needed for some EPDP sessions in Kobe, and I am involved in a number of other policy processes. 
> 
> David
> 
>> On 5 Feb 2019, at 5:24 am, hfaiedh ines <hfaiedh.ines2 at gmail.com <mailto:hfaiedh.ines2 at gmail.com>> wrote:
>> 
>> Hi everyone, I am happy to see Michael and Antonella stepped up to attend the Marrakesh meeting. I will follow remotely or maybe attend on my own ressources if my schedule allows.
>> 
>> Le lundi 4 février 2019, Antonella Perini <antomperini at gmail.com <mailto:antomperini at gmail.com>> a écrit :
>> Hi all,
>> 
>> I'd like to express my interest in the slot. I will be working on the application and plan in order to deliver it in time before the 15th. 
>> 
>> Best,
>> 
>> Antonella
>> 
>> On Mon, 4 Feb 2019 at 17:04, Michael Karanicolas <mkaranicolas at gmail.com <mailto:mkaranicolas at gmail.com>> wrote:
>> Hi all,
>> 
>> I would like to apply for a Marrakech slot. I haven't asked for EC
>> support for Kobe, and since ICANN66 will be in Canada, this will be
>> the only meeting in 2019 where I request support.
>> 
>> I'm heavily involved in a number of aspects of ICANN policy work
>> representing the NCUC, including in the RPMs group, as most recently
>> as a member of the ATRT3 review team. Happy to develop an engagement
>> plan, as needed, and to complete the reporting requirements, as I've
>> done for previous meetings.
>> 
>> Best,
>> 
>> Michael
>> 
>> On Mon, Feb 4, 2019 at 3:48 PM Bruna Martins dos Santos
>> <bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>> wrote:
>> >
>> > Dear EC,
>> >
>> > FYI - we need to indicate who will be the Marrakech travelers until Friday, 22 February 2019. Therefore, I will be accepting applications for the two EC funded slots available for EC members who wish to attend ICANN 65 and are not otherwise funded.
>> >
>> > Please see below the procedures for EC funding allocation from our travel policy and send your application to the EC list until February 15th.
>> >
>> > Best,
>> > --
>> > Bruna Martins dos Santos
>> >
>> > Skype ID: bruna.martinsantos
>> > @boomartins
>> >
>> >
>> > _______________________________________________________
>> > Procedures for EC funding allocation
>> >
>> >  – ICANN Meetings funding allocation for Executive Committee representatives
>> >
>> > –  Executive Committee representatives travel support allocations
>> >
>> > For each ICANN Meeting, the NCUC leadership team is allocated three travel slots. One of these travel slots must be assigned to the NCUC Chair. The remaining two travel slots, or a reallocation of the Chair’s travel slot if he or she relinquishes it, will be assigned to representatives who fulfill the following criteria:
>> >
>> > The representative develops an activity plan that he or she will carry out in the ICANN meeting. This plan must contain a detailed account of the representative’s current engagement in ICANN activities, their plan of engagement at the face-to-face meeting, and explain why and how their physical presence in that meeting is important for achieving the NCUC’s objectives and mission. The timeline for the submission of this application will follow the procedure described in the NCUC Travel Support Policy unless initiated sooner by the NCUC Chair at his or her discretion. The EC travel funding allocation should precede NCUC travel support programme.
>> >
>> > The representative must observe all criteria for eligibility as described in the NCUC Travel policy session above, highlighting the participation on NCSG and NCUC activities. In case of a tie between applicants, the Chair will ask representatives to make reasonable efforts to find an alternative source of funding. Evidence must be provided to the Chair of these attempts. If a representative seeks alternative funding but is declined or rejected, this will not be held against them. Representatives who make no reasonable efforts to find alternative funding will receive lower priority for NCUC resources than those who make reasonable efforts;
>> >
>> > Where there are more candidates for a slot than there are slots available, the regional designation of the EC representative may be a factor weighing in its allocation. The EC representative must send a detailed action plan outlining their plans for inreach/outreach of membership within their region;
>> >
>> > As described in Eligibility criteria, EC who have received travel support for the previous meeting cannot apply again.
>> >
>> > In receiving funding for a meeting, travellers agree to write daily reports during the meeting to update the membership on the proceedings. At his or her discretion, the NCUC Chair may choose to publish these reports as a blog post, or may request that the representative convert their report into a blog post.If a representative receives support, and does not meet their commitments as outlined above, they will be ineligible to receive further NCUC resources.
>> >
>> > References:
>> > * NCUC Operating Procedures: https://www.ncuc.org/wp-content/uploads/2017/09/NCUC-Operating-Procedures-Sept-2017.pdf <https://www.ncuc.org/wp-content/uploads/2017/09/NCUC-Operating-Procedures-Sept-2017.pdf>
>> > (Noting item III Travel support selection and VI Outreach and VII Funding)
>> >
>> > *NCUC Bylaws (Esp. Item XI.A on Transparency): https://www.ncuc.org/bylaws/ <https://www.ncuc.org/bylaws/>
>> >
>> >
>> > ---------- Forwarded message ---------
>> > From: Terri Agnew <terri.agnew at icann.org <mailto:terri.agnew at icann.org>>
>> > Date: seg, 4 de fev de 2019 às 17:21
>> > Subject: ICANN65 | Marrakech- Supported Travelers/Contractor Travelers Database Due // Friday, 22 February 2019
>> > To: bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com> <bruna.mrtns at gmail.com <mailto:bruna.mrtns at gmail.com>>, Maryam Bakoshi <maryam.bakoshi at icann.org <mailto:maryam.bakoshi at icann.org>>
>> > Cc: gnso-secs at icann.org <mailto:gnso-secs at icann.org> <gnso-secs at icann.org <mailto:gnso-secs at icann.org>>
>> >
>> >
>> > Dear all,
>> >
>> >
>> >
>> > In order to service your travel needs for ICANN65 in Marrakech in a timely fashion, please submit your ICANN65 Meeting database to gnso-secs at icann.org <mailto:gnso-secs at icann.org> by Friday, 22 February 2019.
>> >
>> > 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.
>> >
>> > Moving forward, all tri-annual meeting funded traveler lists are due 120 days prior to the next ICANN meeting. (This was formerly 90 days prior).
>> >
>> >
>> >
>> > Benefits of having the list 120 Days Before the Meeting:
>> >
>> > Allow ICANN to gather the documentation required (hotel and flight confirmations) for funded travelers to apply for their visa.
>> > Allow enough time for funded travelers to complete and submit their visa application, which often vary per ICANN Meeting location.
>> > Allow enough time for funded travelers to apply for a transit visa (if required), which often vary per ICANN Meeting location.
>> > Allow ICANN to purchase less expensive airfares.
>> > Allow the travelers to plan their pre-and-post Meeting Travel in advance.
>> > Allow ICANN to set-up funded travelers in advance as vendors with Finance allowing us to wire their per diem funds in a timelier manner.
>> >
>> >
>> >
>> > Please note:
>> >
>> > 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/>].  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>.
>> >
>> >
>> >
>> > 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.
>> >
>> > 2.               If you require a visa to enter the country, please make sure to acquire your visa immediately. Please contact the ICANN travel team to let them know you will need a visa.
>> >
>> > 3.               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.
>> >
>> > 4.               If possible please book direct travel requests. Detours and multi-stop trips are unfortunately not guaranteed.
>> >
>> > 5.               Strictly limit your travel from your home to the ICANN meeting venue.
>> >
>> > 6.               Approved date of arrival/departure for this meeting is Sunday, 23 June – Friday, 28 June 2019
>> >
>> > 7.               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.
>> >
>> > 8.               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.
>> >
>> >
>> >
>> >  Many thanks for your cooperation!
>> >
>> >
>> >
>> > With kind regards,
>> >
>> > Terri
>> >
>> >             ---
>> >
>> > Terri Agnew
>> >
>> > Operations Support - GNSO Lead Administrator
>> >
>> > Internet Corporation for Assigned Names and Numbers (ICANN)
>> >
>> > Email:  terri.agnew at icann.org <mailto:terri.agnew at icann.org>
>> >
>> > Skype ID:  terri.agnew.icann
>> >
>> >
>> >
>> > Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages [gnso.icann.org <http://gnso.icann.org/>]
>> >
>> > Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://twitter.com/ICANN_GNSO> [twitter.com <http://twitter.com/>]
>> >
>> > Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ <https://www.facebook.com/icanngnso/> [facebook.com <http://facebook.com/>]
>> >
>> > http://gnso.icann.org/en/ <http://gnso.icann.org/en/> [gnso.icann.org <http://gnso.icann.org/>]
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Bruna Martins dos Santos
>> >
>> > Skype ID: bruna.martinsantos
>> > @boomartins
>> > _______________________________________________
>> > 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 <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 <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 <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>
> 
> 
> -- 
> Bruna Martins dos Santos 
> 
> Skype ID: bruna.martinsantos
> @boomartins
> _______________________________________________
> 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>
> 
> 
> -- 
> Bruna Martins dos Santos 
> 
> Skype ID: bruna.martinsantos
> @boomartins
> _______________________________________________
> 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>
> 
> 
> -- 
> Bruna Martins dos Santos 
> 
> Skype ID: bruna.martinsantos
> @boomartins
> _______________________________________________
> 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.ncuc.org/pipermail/ncuc-ec/attachments/20190219/da8a33a3/attachment.html>


More information about the NCUC-EC mailing list