[NCSG-PC] Fwd: Operating Procedures for allocation of travel slots at NCSG

[Stephanie Perrin]

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.

cheers SP

On 2018-06-17 13:15, farzaneh badii wrote:
> 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.
>
> Farzaneh
>
> On Sun, Jun 17, 2018 at 12:49 PM, Stephanie Perrin 
> <stephanie.perrin at mail.utoronto.ca 
> <mailto:stephanie.perrin at mail.utoronto.ca>> wrote:
>
>     Since Arsene is not able to come either, is there a replacement
>     action pending for his slot as well?
>
>     Stephanie
>
>     On 2018-06-17 08:25, farzaneh badii wrote:
>>     Hi Ayden
>>
>>     At thanks I had this guideline from Terri :
>>
>>     *ADDITIONS*: All additional traveler requests MUST BE SUBMITTED
>>     60 days prior to the meeting. The deadline date is*" " *.
>>     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.
>>
>>     *REPLACEMENTS*: TBD’s or drop replacements must be final 30 days
>>     prior to the meeting. The deadline date is "..". 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 iftraveldates are reduced for
>>     the replacement.
>>
>>
>>     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.
>>
>>
>>
>>     Farzaneh
>>
>>     On Sun, Jun 17, 2018 at 6:12 AM, Ayden Férdeline
>>     <icann at ferdeline.com <mailto:icann at ferdeline.com>> wrote:
>>
>>         Thanks Farzi, I've made some suggested edits too.
>>
>>         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.
>>
>>         —Ayden
>>
>>
>>         ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>         On 17 June 2018 4:44 AM, Rafik Dammak <rafik.dammak at gmail.com
>>         <mailto:rafik.dammak at gmail.com>> wrote:
>>
>>>         Hi Farzaneh,
>>>
>>>         I added few edits but I think it is quite exhaustive procedures.
>>>
>>>         Best,
>>>
>>>         Rafik
>>>
>>>         Le dim. 17 juin 2018 à 10:57, farzaneh badii
>>>         <farzaneh.badii at gmail.com <mailto:farzaneh.badii at gmail.com>>
>>>         a écrit :
>>>
>>>             Please comment.
>>>
>>>
>>>             Farzaneh
>>>
>>>             ---------- Forwarded message ----------
>>>             From: *farzaneh badii* <farzaneh.badii at gmail.com
>>>             <mailto:farzaneh.badii at gmail.com>>
>>>             Date: Sat, Jun 16, 2018 at 9:56 PM
>>>             Subject: Operating Procedures for allocation of travel
>>>             slots at NCSG
>>>             To: NCSG List <NCSG-DISCUSS at listserv.syr.edu
>>>             <mailto:NCSG-DISCUSS at listserv.syr.edu>>
>>>
>>>
>>>             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.
>>>
>>>             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.
>>>
>>>             https://docs.google.com/document/d/1sSJWajPGAIz9_mwNFiS7YlUg5CYtKdN5HejtaVojXo0/edit?usp=sharing
>>>             <https://docs.google.com/document/d/1sSJWajPGAIz9_mwNFiS7YlUg5CYtKdN5HejtaVojXo0/edit?usp=sharing>
>>>
>>>
>>>             Best
>>>             Farzaneh
>>>
>>>             _______________________________________________
>>>             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>
>>>
>>
>>
>>
>>     _______________________________________________
>>     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>
>
>     _______________________________________________
>     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>
>
>
>
> _______________________________________________
> 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-pc/attachments/20180617/bb4586e8/attachment.htm>