- comments-travel-support-guidelines-30may18@icann.org

[Comments-travel-support-guidelines-30may18] Ratified: ALAC Statement on the Draft Community Travel Support Guidelines
by ICANN At-Large Staff July 20, 2018

July 20, 2018

Dear All, Please find attached the ALAC Statement on the Draft Community Travel Support Guidelines<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Dra…>. Content of the statement is unchanged. Ratification information has been included on the cover page. ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_289792246]

1 0

[Comments-travel-support-guidelines-30may18] NCSG Comment
by Rafik Dammak July 16, 2018

July 16, 2018

Hi, please find attached the comment sent on behalf of NCSG. Best Regards, Rafik Dammak

1 0

[Comments-travel-support-guidelines-30may18] Comments on Draft Community Travel Guidelines – 30 May 2018
by Sarah Kiden July 16, 2018

July 16, 2018

Greetings, Please see attached my comments on the Draft Community Travel Guidelines. Kind regards, Sarah Kiden

1 0

[Comments-travel-support-guidelines-30may18] RrSG response to Draft Community Travel Support Guidelines
by Zoe Bonython July 16, 2018

July 16, 2018

Hello, On behalf of the Registrar Stakeholder Group (RrSG) I would like to submit the attached response to the Draft Community Travel Support Guidelines. Kind regards, Zoe Bonython RrSG Secretariat

1 0

[Comments-travel-support-guidelines-30may18] Ratification Pending: ALAC Statement on the Draft Community Travel Support Guidelines
by ICANN At-Large Staff July 16, 2018

July 16, 2018

Dear All, Please find attached the ALAC Statement on the Draft Community Travel Support Guidelines<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Dra…>. Please disregard the prior comment submission. The revised statement with updated statement number is attached. In the interest of time, the ALAC Chair requested that the Statement be transmitted to the ICANN public comment process with a note that the Statement is pending ALAC ratification. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_1616496524]

1 0

[Comments-travel-support-guidelines-30may18] BC comment on Draft Community Travel Support Guidelines
by Steve DelBianco July 16, 2018

July 16, 2018

Attached is the comment of the ICANN Business Constituency (BC) regarding Draft Community Travel Support Guidelines. This comment was drafted by Jimson Olufuye, with edits by Marilyn Cade and Mark Datysgeld. It was approved in accord with the BC Charter. Steve DelBianco Vice Chair for Policy Coordination ICANN Business Constituency

1 0

[Comments-travel-support-guidelines-30may18] Comments to Travel Guidelines
by Judith Hellerstein July 16, 2018

July 16, 2018

1 0

[Comments-travel-support-guidelines-30may18] Valideus & Com Laude Comments on Travel Support Guidelines
by Susan Payne July 16, 2018

July 16, 2018

Please find attached our comments. Susan Payne Head of Legal Policy | Valideus Ltd 28-30 Little Russell Street London, WC1A 2HN, United Kingdom Liability cannot be accepted for statements made which are clearly the sender's own and not made on behalf of Valideus Ltd. This message is intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to us, and immediately and permanently delete it. Do not use, copy or disclose the information contained in this message or in any attachment. Valideus Ltd is registered in England and Wales with company number 06181291 and VAT number GB 272 9057 85. Our registered office is at 28-30 Little Russell Street, London, WC1A 2HN.

1 0

[Comments-travel-support-guidelines-30may18] RySG comments on Community Travel Support Guidelines
by Paul Diaz July 16, 2018

July 16, 2018

On behalf of the gTLD Registries Stakeholder Group (RySG), please find attached our input on the Draft Community Travel Support Guidelines. In the interest of time, we did not conduct a vote on these comments. We did discuss them on our mailing list and during a biweekly conference call, and no member opposed their submission. Feel free to contact me with questions or concerns. Best, P Paul Diaz Chairman, Registries Stakeholder Group Mobile:+1 703.973.1667 | Skype: pdiaz(a)pir.org

1 0

[Comments-travel-support-guidelines-30may18] Regarding Wire Transfer
by Gustavo Paiva July 13, 2018

July 13, 2018

I am Gustavo Paiva and recently attended my first ICANN Meeting, at Panama, under the NEXTGEN program. I'd like to add a few points, building upon what Mark W. Datysgeld described in his public comment regarding the "Wire Transfer and Foreign Exchange Fees/Losses" issue and basing myself on what I've observed first-hand in the NEXTGEN62 program. As Mark already mentioned, from a stipend of 500USD what was actually received via the wire transfer was an amount close to 380USD. That was a 24% loss right here, which actually became greater than that since the amount was received in local currency — not USD — which meant it was again eaten up by currency exchange rates. This is not a complex argument. Nearly one fourth of the stipend given by ICANN was wasted, lost to needless expenses completely unrelated to the actual ICANN Meeting. Had Fellows or NEXTGENers wasted their stipend on frivolous expenses that impaired their attendance to the event — such as tourism, we could say — they would at least be frowned upon. And yet we see this flagrant wasteful attitude, nearly incomprehensible from a common sense point of view, that also directly impacts the Fellows' and NEXTGENers' capacity to attend the meeting unimpaired from economical constraints. Just this last meeting there were 15 NEXTGENers. If we assume a 120USD loss per attendant that's 1.800USD already. And if we go by the number mentioned in the Public Comment of 300 community members supported that amount could go upwards to 36.000USD (although, admittedly, it wouldn't get to that since this scale of financial loss seemingly is not a problem elsewhere.) Another point that should be accounted is that the wire transfer is a byzantine process here. Despite submitting their forms early and on time, two NEXTGENers were gravely affected by the huge delays in receiving their stipends. I'll not cite names, but one of them only got her stipend on-site despite being told it would arrive via wire transfer up until the last minute. That person, afraid of arriving at Panama without any money and of possibly not receiving the stipend at all, sold her watch to have a viable amount with her to cover possible emergency expenses. And here you can see an important point: the people receiving this assistance often aren't doing well enough at all to be able to just produce some 200USD for unexpected expenses. Their finances are tight, and the byzantine delays from the wire transfer could have outright made it impossible for them to participate. Another NEXTGENer did not receive his stipend on time, neither did they approve giving it to him on-site. As you might expected he was told he would receive a reimbursement. Perhaps it wouldn't be a problem for many, but this NEXTGENer due to the delay took on a loan to cover possible unexpected expenses. He hoped to return home with the stipend to pay it off, yet last I checked he was still waiting for the transfer — and his loan, naturally, collecting interest. Although my experience wasn't as difficult as theirs, my wire transfer did not arrive on time and I was scheduled to receive it on-site. I took some small savings with me, yet when I arrived at the airport I was informed FCM themselves had outright cancelled my ticket to the Meeting. I was instructed to pay it off myself, that I would later get a reimbursement, but my issue here was that I didn't even have that kind of money — those expenses were gravely over the most overzealous expenses for this trip. My situation was, fortunately, resolved on FCM's side, but my point stands — the very delay behind the wire transfer is a problem by itself, that breeds insecurity, distrust and harms one's capacity to attend a Meeting unhindered. With all of that said, I'd like to support Mark's comment regarding alternatives to the wire transfer. He has given a good list of options. Let's keep in mind this is a simple question of not wasting money, of being financially efficient and in doing so allowing attendants to participate in Meetings without unnecessary hindrances. Gustavo Paiva. July 13 2018.

1 0