<div>Arsene, can you please advise if you are coming to Panama or not? I was understand the impression you were going to enter with a 'visa on arrival'? But maybe I am mistaken - please can you clarify urgently.</div><div><br></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-user"><div>Best wishes, Ayden  <br></div></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div> On 18 June 2018 4:07 AM, Stephanie Perrin <stephanie.perrin@mail.utoronto.ca> wrote:<br></div><div> <br></div><blockquote type="cite" class="protonmail_quote"><p><span style="font-size:undefinedpx" class="size"><span style="font-family:Lucida Grande" class="font">June 4 Arsene said on
          the skype channel for councillors that he was not able to get
          a visa.  Should confirm, but that was what he said then.  It
          is a shame to waste the spot of someone else could come and
          participate.</span></span><br></p><p><span style="font-size:undefinedpx" class="size"><span style="font-family:Lucida Grande" class="font">cheers SP</span></span><br></p><div class="moz-cite-prefix">On 2018-06-17 13:15, farzaneh badii
      wrote:<br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I didn't know Arsene is
          not able to come. Arsene, are you having issues? It might be
          too late to be able to transfer airfare perhaps but might be
          possible to transfer hotel room. Let me know as soon as
          possible. I'll give it a try as soon as Arsene confirms he
          cannot attend. Thanks much.<br></div></div><div class="gmail_extra"><div><br></div><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="font-family:verdana, sans-serif" class="font">Farzaneh</span><br></div></div></div></div><div><br></div><div class="gmail_quote"><div>On Sun, Jun 17, 2018 at 12:49 PM,
          Stephanie Perrin <span dir="ltr"><<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.utoronto.ca</a>></span> wrote:<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF"><p><span style="font-size:undefinedpx" class="size"><span style="font-family:Lucida Grande" class="font">Since Arsene
                    is not able to come either, is there a replacement
                    action pending for his slot as well?</span></span><br></p><span class="HOEnZb"><span style="color:#888888" class="colour"><p><span style="font-size:undefinedpx" class="size"><span style="font-family:Lucida Grande" class="font">Stephanie</span></span><br></p></span></span><div><div class="h5"><div class="m_-3724735570436236531moz-cite-prefix">On
                    2018-06-17 08:25, farzaneh badii wrote:<br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Hi Ayden <br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">At thanks
                        I had this guideline from Terri :<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><p class="MsoNormal" style="margin: 0px; text-decoration-style: initial; text-decoration-color: initial;"><span style="background-color:rgb(255, 255, 255)" class="highlight"><span style="font-family:arial, sans-serif" class="font"><span style="font-size:12.8px" class="size"><b>ADDITIONS</b>:
                          All additional traveler requests MUST BE
                          SUBMITTED 60 days prior to the meeting. The
                          deadline date is<span> </span><b><span style="background-color:yellow" class="highlight">" " </span></b>.
                          Requests past the 60-day 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 and may
                          NOT be placed in the same hotel as their
                          funded traveler groups.</span></span></span><br></p><p class="MsoNormal" style="margin: 0px; text-decoration-style: initial; text-decoration-color: initial;"><span style="background-color:rgb(255, 255, 255)" class="highlight"><span style="font-family:arial, sans-serif" class="font"><span style="font-size:12.8px" class="size"> </span></span></span><br></p><p class="MsoNormal" style="margin: 0px; text-decoration-style: initial; text-decoration-color: initial;"><span style="background-color:rgb(255, 255, 255)" class="highlight"><span style="font-family:arial, sans-serif" class="font"><span style="font-size:12.8px" class="size"><b>REPLACEMENTS</b>:
                          TBD’s or drop replacements must be final 30
                          days prior to the meeting. The deadline date
                          is<span> ".."</span>. Replacement Requests
                          past 30 days will be evaluated on a case by
                          case basis by ICANN. Failure to replace TBD’s
                          30 days prior to the meeting will be
                          considered a “Drop.” Replacements will be
                          billed for the original request dates even
                          with if<span> </span><span class="m_-3724735570436236531gmail-il">travel</span><span> </span>dates
                          are reduced for the replacement.</span></span></span><br></p><p class="MsoNormal" style="margin: 0px; text-decoration-style: initial; text-decoration-color: initial;"><span style="background-color:rgb(255, 255, 255)" class="highlight"><span style="font-family:arial, sans-serif" class="font"><span style="font-size:12.8px" class="size"></span></span></span><br></p><p class="MsoNormal" style="margin: 0px; text-decoration-style: initial; text-decoration-color: initial;"><span style="background-color:rgb(255, 255, 255)" class="highlight"><span style="font-family:arial, sans-serif" class="font"><span style="font-size:12.8px" class="size">I
                          agree that transferring is not easy but
                          previously, there was little attempt to do
                          anything about it. So these operating
                          procedures can help fix that. </span></span></span><br></p><p class="MsoNormal" style="margin: 0px; text-decoration-style: initial; text-decoration-color: initial;"><span style="background-color:rgb(255, 255, 255)" class="highlight"><span style="font-family:arial, sans-serif" class="font"><span style="font-size:12.8px" class="size"> </span></span></span><br></p><div><br></div></div></div><div class="gmail_extra"><div><br></div><div><div class="m_-3724735570436236531gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="font-family:verdana, sans-serif" class="font">Farzaneh</span><br></div></div></div></div><div><br></div><div class="gmail_quote"><div>On Sun, Jun 17, 2018 at
                        6:12 AM, Ayden Férdeline <span dir="ltr"><<a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a>></span> wrote:<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0
                          0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex"><div>Thanks Farzi, I've made some suggested
                            edits too.<br></div><div><br></div><div>The proposed Travel Support Guidelines
                            (currently out for public comment) note that
                            "barring emergencies" (which are not
                            defined) replacement supported travellers
                            will only be possible if 60 days or more
                            notice is given to ICANN org. I note this
                            because of #6 of the procedure - just
                            something to be aware of, I suppose. It
                            might not always be so easy to re-allocate a
                            travel slot to another community member.<br></div><div><br></div><div class="m_-3724735570436236531m_4418175922329650880protonmail_signature_block"><div class="m_-3724735570436236531m_4418175922329650880protonmail_signature_block-user"><div>—Ayden  <br></div></div><div class="m_-3724735570436236531m_4418175922329650880protonmail_signature_block-proton
m_-3724735570436236531m_4418175922329650880protonmail_signature_block-empty"><br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div class="m_-3724735570436236531HOEnZb"><div class="m_-3724735570436236531h5"><div>On 17 June 2018 4:44 AM, Rafik
                                Dammak <<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>>
                                wrote:<br></div><div><br></div><blockquote type="cite" class="m_-3724735570436236531m_4418175922329650880protonmail_quote"><div dir="ltr"><div>Hi Farzaneh,<br></div><div><br></div><div>I added few edits but I think it
                                    is quite exhaustive procedures.<br></div><div><br></div><div>Best,<br></div><div><br></div><div><div>Rafik<br></div><div><br></div><div class="gmail_quote"><div dir="ltr">Le dim. 17 juin
                                        2018 à 10:57, farzaneh badii
                                        <<a href="mailto:farzaneh.badii@gmail.com" target="_blank">farzaneh.badii@gmail.com</a>>
                                        a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0
                                        .8ex;border-left:1px #ccc
                                        solid;padding-left:1ex"><div dir="ltr"><div style="font-family:verdana,sans-serif">Please
                                            comment.<br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div><div class="m_-3724735570436236531m_4418175922329650880m_64986479870458420gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="font-family:verdana, sans-serif" class="font">Farzaneh</span><br></div></div></div></div><div><br></div><div class="gmail_quote"><div>---------- Forwarded
                                              message ----------<br></div><div>From: <b class="gmail_sendername">farzaneh
                                                badii</b> <span dir="ltr"><<a href="mailto:farzaneh.badii@gmail.com" target="_blank">farzaneh.badii@gmail.com</a>></span><br></div><div>Date: Sat, Jun 16, 2018
                                              at 9:56 PM<br></div><div>Subject: Operating
                                              Procedures for allocation
                                              of travel slots at NCSG<br></div><div>To: NCSG List <<a href="mailto:NCSG-DISCUSS@listserv.syr.edu" target="_blank">NCSG-DISCUSS@listserv.syr.edu</a><wbr>><br></div><div><br></div><div><br></div><div dir="ltr"><div style="font-family:verdana,sans-serif">Dear
                                                all please find attached
                                                a draft of operating
                                                procedures for the
                                                allocation of travel
                                                slots. I will share this
                                                with NCSG EC and PC as
                                                well for comments. <br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">You
                                                can comment on this
                                                document until 8th July,
                                                we will then discuss it
                                                at NCSG EC finalize it
                                                and send you the final
                                                version. If changes are
                                                made by EC after 8th
                                                July, we will inform you
                                                about it and give some
                                                time for comments and
                                                then approve at EC
                                                level.<br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><a href="https://docs.google.com/document/d/1sSJWajPGAIz9_mwNFiS7YlUg5CYtKdN5HejtaVojXo0/edit?usp=sharing" style="color:rgb(17,85,204);font-size:12.8px;background-color:rgb(255,255,255)" target="_blank">https://docs.google.com/docume<wbr>nt/d/1sSJWajPGAIz9_mwNFiS7YlUg<wbr>5CYtKdN5HejtaVojXo0/edit?usp=<wbr>sharing</a><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Best<br></div><span class="m_-3724735570436236531m_4418175922329650880m_64986479870458420HOEnZb"><span style="color:rgb(136, 136, 136)" class="colour"><div><div class="m_-3724735570436236531m_4418175922329650880m_64986479870458420m_-142911003704323456gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="font-family:verdana, sans-serif" class="font">Farzaneh</span><br></div></div></div></div></span></span></div></div><div><br></div></div><div>______________________________<wbr>_________________<br></div><div>NCSG-PC mailing list<br></div><div><a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br></div><div><a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br></div></blockquote></div></div></div></blockquote><div><br></div></div></div></blockquote></div><div><br></div></div><div><br></div><pre class="m_-3724735570436236531moz-quote-pre">______________________________<wbr>_________________
NCSG-PC mailing list
<a class="m_-3724735570436236531moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a>
<a class="m_-3724735570436236531moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a>
<br></pre></blockquote></div></div></div><div><br></div><div>______________________________<wbr>_________________<br></div><div> NCSG-PC mailing list<br></div><div> <a href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a><br></div><div> <a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br></div><div> <br></div></blockquote></div><div><br></div></div><div><br></div><pre class="moz-quote-pre" wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
<br></pre></blockquote></blockquote><div><br></div>