Colleagues... I have some questions on this -- apologies I have not kept on top of it, due to recent personal circumstances. This document seems vague about the at-large travel budget itself. Here's what I get from these documents referenced in the below news alert: 1. The supporting organizations want and are going to get some additional ICANN funds for travel. So are nomcom appointed people. 2. Chairs and such get some more flexibility and discretion with how travel funding is spent. 3. Because of the expense of the forthcoming at-large summit, the at-large will be considered after the summit to be "matured," and this means: -- limited to no travel funds for those outside the ALAC, i.e., people in ALSs, RALOs, etc. (?) -- limited to no travel funds for the 18-odd people on the ALAC itself (?) Is this correct? -----Original Message----- From: ICANN News Alert [mailto:communications@icann.org] Sent: Wed 8/13/2008 2:35 PM To: Brendler, Beau Subject: ICANN News Alert -- ICANN Posts Revised Community Travel Support Procedure for FY09 ICANN News Alert http://www.icann.org/en/announcements/announcement-13aug08-en.htm ________________________________ ICANN Posts Revised Community Travel Support Procedure for FY09 13 August 2008 The work to create a community travel support procedure began with a specific call for travel support in late 2007 by some in the community (though this issue has been discussed for some time). There has been extensive consultation on community travel support. It began as a workshop in Delhi, with comments received and an analysis posted. Further, a draft was posted in June, discussed in budget meetings in Paris, and again with fairly extensive comment in person, via email and on the web. These second round of comments were summarized and analyzed. This last summary is available at: http://forum.icann.org/lists/travel-support-draft/msg00013.html The revised Community Travel Support Procedure for FY09 http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08.htm document strives to accommodate the community feedback. Of course, this is a subject about which complete agreement is not possible. However, there is strong agreement within the community that a procedure exist that is documented, transparent, consistent, adhered-to, and reviewed/revised for efficacy. Comparing the final procedure with the draft discussed in Paris, some key changes include: * Guarantees travel support for NomCom-nominated counselors * Stresses transparency in application and post-meeting reporting * Allows for some flexibility in the allocation mechanism within a SO without overburdening the Chair The document strives to be complete without being overly-detailed. This will leave many specific questions unanswered. ICANN staff will develop and post a FAQ (frequently asked questions document) to capture questions, and provide consistent answers to the entire community. If you have questions, please send them to the ICANN staff member with whom you work most closely, or send them to travel-support@icann.org. Staff will collect feedback on issues that arise in the first implementation of this procedure, now through the Cairo meeting, and Staff will make clarifications, as needed. Additionally, Staff will conduct a complete review of the Community Travel Support Procedure at year end with a public consultation at the June ICANN meeting, and this will be an opportunity for RSSAC to provide additional input if desired. ________________________________ Sign up for ICANN's Monthly Magazine http://www.icann.org/magazine/ This message was sent by: ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601 Powered by iContact: http://freetrial.icontact.com Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=10248929&l=6333&s=96FD&m=167... *** Scanned **************************************************************************** ******** SCANNED **************************************************************************** ********
Dear All: As questions arise, we are compiling them so that we can get answers for you. There is a teleconference amongst the staff to discuss the questions that arise next Tuesday. My understanding is that the procedure intends that the support provided to At-Large for the NEXT FY (that is, the FY that begins July 2009) would be the same as that extended to the various communities explicitly referenced in the travel procedure. At the same time, the entire procedure is subject to review at the end of this FY. On 13/08/2008 21:06, "Beau Brendler" <brenbe@consumer.org> wrote: Colleagues... I have some questions on this -- apologies I have not kept on top of it, due to recent personal circumstances. This document seems vague about the at-large travel budget itself. Here's what I get from these documents referenced in the below news alert: 1. The supporting organizations want and are going to get some additional ICANN funds for travel. So are nomcom appointed people. 2. Chairs and such get some more flexibility and discretion with how travel funding is spent. 3. Because of the expense of the forthcoming at-large summit, the at-large will be considered after the summit to be "matured," and this means: -- limited to no travel funds for those outside the ALAC, i.e., people in ALSs, RALOs, etc. (?) -- limited to no travel funds for the 18-odd people on the ALAC itself (?) Is this correct? -----Original Message----- From: ICANN News Alert [mailto:communications@icann.org] Sent: Wed 8/13/2008 2:35 PM To: Brendler, Beau Subject: ICANN News Alert -- ICANN Posts Revised Community Travel Support Procedure for FY09 ICANN News Alert http://www.icann.org/en/announcements/announcement-13aug08-en.htm ________________________________ ICANN Posts Revised Community Travel Support Procedure for FY09 13 August 2008 The work to create a community travel support procedure began with a specific call for travel support in late 2007 by some in the community (though this issue has been discussed for some time). There has been extensive consultation on community travel support. It began as a workshop in Delhi, with comments received and an analysis posted. Further, a draft was posted in June, discussed in budget meetings in Paris, and again with fairly extensive comment in person, via email and on the web. These second round of comments were summarized and analyzed. This last summary is available at: http://forum.icann.org/lists/travel-support-draft/msg00013.html The revised Community Travel Support Procedure for FY09 http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08.htm document strives to accommodate the community feedback. Of course, this is a subject about which complete agreement is not possible. However, there is strong agreement within the community that a procedure exist that is documented, transparent, consistent, adhered-to, and reviewed/revised for efficacy. Comparing the final procedure with the draft discussed in Paris, some key changes include: * Guarantees travel support for NomCom-nominated counselors * Stresses transparency in application and post-meeting reporting * Allows for some flexibility in the allocation mechanism within a SO without overburdening the Chair The document strives to be complete without being overly-detailed. This will leave many specific questions unanswered. ICANN staff will develop and post a FAQ (frequently asked questions document) to capture questions, and provide consistent answers to the entire community. If you have questions, please send them to the ICANN staff member with whom you work most closely, or send them to travel-support@icann.org. Staff will collect feedback on issues that arise in the first implementation of this procedure, now through the Cairo meeting, and Staff will make clarifications, as needed. Additionally, Staff will conduct a complete review of the Community Travel Support Procedure at year end with a public consultation at the June ICANN meeting, and this will be an opportunity for RSSAC to provide additional input if desired. ________________________________ Sign up for ICANN's Monthly Magazine http://www.icann.org/magazine/ This message was sent by: ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601 Powered by iContact: http://freetrial.icontact.com Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=10248929=6333=96FD=167951=16... *** Scanned **************************************************************************** ******** SCANNED **************************************************************************** ******** _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac -- Regards, Nick Ashton-Hart Director for At-Large Internet Corporation for Assigned Names and Numbers (ICANN) Main Tel: +33 (450) 40 46 88 USA DD: +1 (310) 578-8637 Fax: +41 (22) 594-85-44 Mobile: +41 (79) 595 54-68 email: nick.ashton-hart@icann.org Win IM: ashtonhart@hotmail.com / AIM/iSight: nashtonhart@mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart
Here's a question to add to your list. Bullet 3 of 2.1 says "funding can only be used for air fare and other travel expenses to and from ICANN meetings for active SO members". Past policy is that ICANN will fund the actual travel expenses (that is, getting from one place to another) PLUS living expenses while at the meeting (actual reasonable expenses for the Board, per diem for the rest of the rabble). Does the quote above mean they will not fund living expenses for SO members, or is the "to and from" simply meant to imply that they will not fund private side-trips. The reason the question is not frivolous is that for the Delhi meeting, ICANN explicitly funded some GNSO members for TRAVEL and explicitly not for expenses while in Delhi. Alan At 13/08/2008 03:13 PM, Nick Ashton-Hart wrote:
Dear All:
As questions arise, we are compiling them so that we can get answers for you. There is a teleconference amongst the staff to discuss the questions that arise next Tuesday.
My understanding is that the procedure intends that the support provided to At-Large for the NEXT FY (that is, the FY that begins July 2009) would be the same as that extended to the various communities explicitly referenced in the travel procedure.
At the same time, the entire procedure is subject to review at the end of this FY.
On 13/08/2008 21:06, "Beau Brendler" <brenbe@consumer.org> wrote:
Colleagues...
I have some questions on this -- apologies I have not kept on top of it, due to recent personal circumstances. This document seems vague about the at-large travel budget itself. Here's what I get from these documents referenced in the below news alert:
1. The supporting organizations want and are going to get some additional ICANN funds for travel. So are nomcom appointed people. 2. Chairs and such get some more flexibility and discretion with how travel funding is spent. 3. Because of the expense of the forthcoming at-large summit, the at-large will be considered after the summit to be "matured," and this means: -- limited to no travel funds for those outside the ALAC, i.e., people in ALSs, RALOs, etc. (?) -- limited to no travel funds for the 18-odd people on the ALAC itself (?)
Is this correct?
-----Original Message----- From: ICANN News Alert [mailto:communications@icann.org] Sent: Wed 8/13/2008 2:35 PM To: Brendler, Beau Subject: ICANN News Alert -- ICANN Posts Revised Community Travel Support Procedure for FY09
ICANN News Alert http://www.icann.org/en/announcements/announcement-13aug08-en.htm ________________________________
ICANN Posts Revised Community Travel Support Procedure for FY09 13 August 2008
The work to create a community travel support procedure began with a specific call for travel support in late 2007 by some in the community (though this issue has been discussed for some time). There has been extensive consultation on community travel support. It began as a workshop in Delhi, with comments received and an analysis posted. Further, a draft was posted in June, discussed in budget meetings in Paris, and again with fairly extensive comment in person, via email and on the web. These second round of comments were summarized and analyzed. This last summary is available at:
http://forum.icann.org/lists/travel-support-draft/msg00013.html
The revised Community Travel Support Procedure for FY09 http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08.htm document strives to accommodate the community feedback. Of course, this is a subject about which complete agreement is not possible. However, there is strong agreement within the community that a procedure exist that is documented, transparent, consistent, adhered-to, and reviewed/revised for efficacy.
Comparing the final procedure with the draft discussed in Paris, some key changes include:
* Guarantees travel support for NomCom-nominated counselors * Stresses transparency in application and post-meeting reporting * Allows for some flexibility in the allocation mechanism within a SO without overburdening the Chair
The document strives to be complete without being overly-detailed. This will leave many specific questions unanswered. ICANN staff will develop and post a FAQ (frequently asked questions document) to capture questions, and provide consistent answers to the entire community. If you have questions, please send them to the ICANN staff member with whom you work most closely, or send them to travel-support@icann.org.
Staff will collect feedback on issues that arise in the first implementation of this procedure, now through the Cairo meeting, and Staff will make clarifications, as needed. Additionally, Staff will conduct a complete review of the Community Travel Support Procedure at year end with a public consultation at the June ICANN meeting, and this will be an opportunity for RSSAC to provide additional input if desired. ________________________________
Sign up for ICANN's Monthly Magazine http://www.icann.org/magazine/
This message was sent by: ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601
Powered by iContact: http://freetrial.icontact.com
Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=10248929=6333=96FD=167951=16...
*** Scanned
**************************************************************************** ******** SCANNED
**************************************************************************** ******** _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
--
Regards,
Nick Ashton-Hart Director for At-Large Internet Corporation for Assigned Names and Numbers (ICANN) Main Tel: +33 (450) 40 46 88 USA DD: +1 (310) 578-8637 Fax: +41 (22) 594-85-44 Mobile: +41 (79) 595 54-68 email: nick.ashton-hart@icann.org Win IM: ashtonhart@hotmail.com / AIM/iSight: nashtonhart@mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
for the Delhi meeting, ICANN explicitly funded some GNSO members for TRAVEL and explicitly not for expenses while in Delhi.<
Well, there's a good place to start trimming expenses. Along with the expensive galas that take place at the meetings. -----Original Message----- From: alac-bounces@atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Alan Greenberg Sent: Wednesday, August 13, 2008 4:41 PM To: ALAC Working List Subject: Re: [ALAC] travel policy Here's a question to add to your list. Bullet 3 of 2.1 says "funding can only be used for air fare and other travel expenses to and from ICANN meetings for active SO members". Past policy is that ICANN will fund the actual travel expenses (that is, getting from one place to another) PLUS living expenses while at the meeting (actual reasonable expenses for the Board, per diem for the rest of the rabble). Does the quote above mean they will not fund living expenses for SO members, or is the "to and from" simply meant to imply that they will not fund private side-trips. The reason the question is not frivolous is that for the Delhi meeting, ICANN explicitly funded some GNSO members for TRAVEL and explicitly not for expenses while in Delhi. Alan At 13/08/2008 03:13 PM, Nick Ashton-Hart wrote:
Dear All:
As questions arise, we are compiling them so that we can get answers for you. There is a teleconference amongst the staff to discuss the questions that arise next Tuesday.
My understanding is that the procedure intends that the support provided to At-Large for the NEXT FY (that is, the FY that begins July 2009) would be the same as that extended to the various communities explicitly referenced in the travel procedure.
At the same time, the entire procedure is subject to review at the end of this FY.
On 13/08/2008 21:06, "Beau Brendler" <brenbe@consumer.org> wrote:
Colleagues...
I have some questions on this -- apologies I have not kept on top of it, due to recent personal circumstances. This document seems vague about the at-large travel budget itself. Here's what I get from these documents referenced in the below news alert:
1. The supporting organizations want and are going to get some additional ICANN funds for travel. So are nomcom appointed people. 2. Chairs and such get some more flexibility and discretion with how travel funding is spent. 3. Because of the expense of the forthcoming at-large summit, the at-large will be considered after the summit to be "matured," and this means: -- limited to no travel funds for those outside the ALAC, i.e., people in ALSs, RALOs, etc. (?) -- limited to no travel funds for the 18-odd people on the ALAC itself (?)
Is this correct?
-----Original Message----- From: ICANN News Alert [mailto:communications@icann.org] Sent: Wed 8/13/2008 2:35 PM To: Brendler, Beau Subject: ICANN News Alert -- ICANN Posts Revised Community Travel Support Procedure for FY09
ICANN News Alert http://www.icann.org/en/announcements/announcement-13aug08-en.htm ________________________________
ICANN Posts Revised Community Travel Support Procedure for FY09 13 August 2008
The work to create a community travel support procedure began with a specific call for travel support in late 2007 by some in the community (though this issue has been discussed for some time). There has been extensive consultation on community travel support. It began as a workshop in Delhi, with comments received and an analysis
posted. Further, a draft was posted in June, discussed in budget meetings in Paris, and again with fairly extensive comment in person, via email and on the web. These second round of comments were summarized and analyzed. This last summary is available at:
http://forum.icann.org/lists/travel-support-draft/msg00013.html
The revised Community Travel Support Procedure for FY09 http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08 .htm document strives to accommodate the community feedback. Of course,
this is a subject about which complete agreement is not possible. However, there is strong agreement within the community that a procedure exist that is documented, transparent, consistent, adhered-to, and reviewed/revised for efficacy.
Comparing the final procedure with the draft discussed in Paris, some key changes include:
* Guarantees travel support for NomCom-nominated counselors * Stresses transparency in application and post-meeting reporting * Allows for some flexibility in the allocation mechanism within a SO without overburdening the Chair
The document strives to be complete without being overly-detailed. This will leave many specific questions unanswered. ICANN staff will develop and post a FAQ (frequently asked questions document) to capture
questions, and provide consistent answers to the entire community. If you have questions, please send them to the ICANN staff member with whom you work most closely, or send them to travel-support@icann.org.
Staff will collect feedback on issues that arise in the first implementation of this procedure, now through the Cairo meeting, and Staff will make clarifications, as needed. Additionally, Staff will conduct a complete review of the Community Travel Support Procedure at year end with a public consultation at the June ICANN meeting, and this
will be an opportunity for RSSAC to provide additional input if desired. ________________________________
Sign up for ICANN's Monthly Magazine http://www.icann.org/magazine/
This message was sent by: ICANN, 4676 Admiralty Way, Suite 330 , Marina
del Rey, CA 90292-6601
Powered by iContact: http://freetrial.icontact.com
Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=10248929=6333=96FD=1679 51=165637
*** Scanned
*********************************************************************** ***** ******** SCANNED
*********************************************************************** ***** ******** _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.ican n.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
--
Regards,
Nick Ashton-Hart Director for At-Large Internet Corporation for Assigned Names and Numbers (ICANN) Main Tel: +33 (450) 40 46 88 USA DD: +1 (310) 578-8637 Fax: +41 (22) 594-85-44 Mobile: +41 (79) 595 54-68 email: nick.ashton-hart@icann.org Win IM: ashtonhart@hotmail.com / AIM/iSight: nashtonhart@mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.ican n.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann .org At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac *** Scanned **************************************************************************** ******** SCANNED **************************************************************************** ********
The Gala is usually not an ICANN cost, but sponsored by the local host. Similarly,most of the other evening events are sponsored. Jacqueline Brendler, Beau wrote:
for the Delhi meeting, ICANN explicitly funded some GNSO members for
TRAVEL and explicitly not for expenses while in Delhi.<
Well, there's a good place to start trimming expenses. Along with the expensive galas that take place at the meetings.
-----Original Message----- From: alac-bounces@atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Alan Greenberg Sent: Wednesday, August 13, 2008 4:41 PM To: ALAC Working List Subject: Re: [ALAC] travel policy
Here's a question to add to your list.
Bullet 3 of 2.1 says "funding can only be used for air fare and other travel expenses to and from ICANN meetings for active SO members". Past policy is that ICANN will fund the actual travel expenses (that is, getting from one place to another) PLUS living expenses while at the meeting (actual reasonable expenses for the Board, per diem for the rest of the rabble). Does the quote above mean they will not fund living expenses for SO members, or is the "to and from" simply meant to imply that they will not fund private side-trips. The reason the question is not frivolous is that for the Delhi meeting, ICANN explicitly funded some GNSO members for TRAVEL and explicitly not for expenses while in Delhi.
Alan
At 13/08/2008 03:13 PM, Nick Ashton-Hart wrote:
Dear All:
As questions arise, we are compiling them so that we can get answers for you. There is a teleconference amongst the staff to discuss the questions that arise next Tuesday.
My understanding is that the procedure intends that the support provided to At-Large for the NEXT FY (that is, the FY that begins July 2009) would be the same as that extended to the various communities explicitly referenced in the travel procedure.
At the same time, the entire procedure is subject to review at the end of this FY.
On 13/08/2008 21:06, "Beau Brendler" <brenbe@consumer.org> wrote:
Colleagues...
I have some questions on this -- apologies I have not kept on top of it, due to recent personal circumstances. This document seems vague about the at-large travel budget itself. Here's what I get from these documents referenced in the below news alert:
1. The supporting organizations want and are going to get some additional ICANN funds for travel. So are nomcom appointed people. 2. Chairs and such get some more flexibility and discretion with how travel funding is spent. 3. Because of the expense of the forthcoming at-large summit, the at-large will be considered after the summit to be "matured," and this
means:
-- limited to no travel funds for those outside the ALAC, i.e., people in ALSs, RALOs, etc. (?) -- limited to no travel funds for the 18-odd people on the ALAC itself (?)
Is this correct?
-----Original Message----- From: ICANN News Alert [mailto:communications@icann.org] Sent: Wed 8/13/2008 2:35 PM To: Brendler, Beau Subject: ICANN News Alert -- ICANN Posts Revised Community Travel Support Procedure for FY09
ICANN News Alert http://www.icann.org/en/announcements/announcement-13aug08-en.htm ________________________________
ICANN Posts Revised Community Travel Support Procedure for FY09 13 August 2008
The work to create a community travel support procedure began with a specific call for travel support in late 2007 by some in the community (though this issue has been discussed for some time). There has been extensive consultation on community travel support. It began as a workshop in Delhi, with comments received and an analysis
posted. Further, a draft was posted in June, discussed in budget meetings in Paris, and again with fairly extensive comment in person, via email and on the web. These second round of comments were summarized and analyzed. This last summary is available at:
http://forum.icann.org/lists/travel-support-draft/msg00013.html
The revised Community Travel Support Procedure for FY09 http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08 .htm document strives to accommodate the community feedback. Of course,
this is a subject about which complete agreement is not possible. However, there is strong agreement within the community that a procedure exist that is documented, transparent, consistent, adhered-to, and reviewed/revised for efficacy.
Comparing the final procedure with the draft discussed in Paris, some key changes include:
* Guarantees travel support for NomCom-nominated counselors * Stresses transparency in application and post-meeting reporting * Allows for some flexibility in the allocation mechanism within a SO without overburdening the Chair
The document strives to be complete without being overly-detailed. This will leave many specific questions unanswered. ICANN staff will develop and post a FAQ (frequently asked questions document) to capture
questions, and provide consistent answers to the entire community. If you have questions, please send them to the ICANN staff member with whom you work most closely, or send them to travel-support@icann.org.
Staff will collect feedback on issues that arise in the first implementation of this procedure, now through the Cairo meeting, and Staff will make clarifications, as needed. Additionally, Staff will conduct a complete review of the Community Travel Support Procedure at year end with a public consultation at the June ICANN meeting, and this
will be an opportunity for RSSAC to provide additional input if desired. ________________________________
Sign up for ICANN's Monthly Magazine http://www.icann.org/magazine/
This message was sent by: ICANN, 4676 Admiralty Way, Suite 330 , Marina
del Rey, CA 90292-6601
Powered by iContact: http://freetrial.icontact.com
Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=10248929=6333=96FD=1679 51=165637
*** Scanned
*********************************************************************** ***** ******** SCANNED
*********************************************************************** ***** ******** _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.ican n.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
--
Regards,
Nick Ashton-Hart Director for At-Large Internet Corporation for Assigned Names and Numbers (ICANN) Main Tel: +33 (450) 40 46 88 USA DD: +1 (310) 578-8637 Fax: +41 (22) 594-85-44 Mobile: +41 (79) 595 54-68 email: nick.ashton-hart@icann.org Win IM: ashtonhart@hotmail.com / AIM/iSight: nashtonhart@mac.com / Skype: nashtonhart Online Bio: https://www.linkedin.com/in/ashtonhart _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.ican n.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann .org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
*** Scanned
**************************************************************************** ******** SCANNED
**************************************************************************** ********
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
Hi Beau To me it seems as if the suggestion is that ALAC has the same support as the SOs - that is - NomCom appointed members and then the Chair and half of the remaining ALAC members. Currently that means 5 NomCom, plus 5 others including Chair, so travel support for 10 ALAC persons to each ICANN meeting, with the Chair getting Business Class travel for flights over 5 hours. Discretion of the Chair can determine if the funding is applied to members or other people, such as WG people, Liaisons, RALO etc. NomCom appointed ppl have always had travel support, no matter where they sit (SO, ALAC, etc) and they will continue to have such. People on the NomCom will have funding to NomCom meetings, but only the Chair, Vice Chair will have support to ICANN meetings. Very importantly, this is for fiscal year 2009-2010, so will not take effect until July 2009. Jacqueline Brendler, Beau wrote:
Colleagues...
I have some questions on this -- apologies I have not kept on top of it, due to recent personal circumstances. This document seems vague about the at-large travel budget itself. Here's what I get from these documents referenced in the below news alert:
1. The supporting organizations want and are going to get some additional ICANN funds for travel. So are nomcom appointed people. 2. Chairs and such get some more flexibility and discretion with how travel funding is spent. 3. Because of the expense of the forthcoming at-large summit, the at-large will be considered after the summit to be "matured," and this means: -- limited to no travel funds for those outside the ALAC, i.e., people in ALSs, RALOs, etc. (?) -- limited to no travel funds for the 18-odd people on the ALAC itself (?)
Is this correct?
-----Original Message----- From: ICANN News Alert [mailto:communications@icann.org] Sent: Wed 8/13/2008 2:35 PM To: Brendler, Beau Subject: ICANN News Alert -- ICANN Posts Revised Community Travel Support Procedure for FY09
ICANN News Alert http://www.icann.org/en/announcements/announcement-13aug08-en.htm ________________________________
ICANN Posts Revised Community Travel Support Procedure for FY09 13 August 2008
The work to create a community travel support procedure began with a specific call for travel support in late 2007 by some in the community (though this issue has been discussed for some time). There has been extensive consultation on community travel support. It began as a workshop in Delhi, with comments received and an analysis posted. Further, a draft was posted in June, discussed in budget meetings in Paris, and again with fairly extensive comment in person, via email and on the web. These second round of comments were summarized and analyzed. This last summary is available at:
http://forum.icann.org/lists/travel-support-draft/msg00013.html
The revised Community Travel Support Procedure for FY09 http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08.htm document strives to accommodate the community feedback. Of course, this is a subject about which complete agreement is not possible. However, there is strong agreement within the community that a procedure exist that is documented, transparent, consistent, adhered-to, and reviewed/revised for efficacy.
Comparing the final procedure with the draft discussed in Paris, some key changes include:
* Guarantees travel support for NomCom-nominated counselors * Stresses transparency in application and post-meeting reporting * Allows for some flexibility in the allocation mechanism within a SO without overburdening the Chair
The document strives to be complete without being overly-detailed. This will leave many specific questions unanswered. ICANN staff will develop and post a FAQ (frequently asked questions document) to capture questions, and provide consistent answers to the entire community. If you have questions, please send them to the ICANN staff member with whom you work most closely, or send them to travel-support@icann.org.
Staff will collect feedback on issues that arise in the first implementation of this procedure, now through the Cairo meeting, and Staff will make clarifications, as needed. Additionally, Staff will conduct a complete review of the Community Travel Support Procedure at year end with a public consultation at the June ICANN meeting, and this will be an opportunity for RSSAC to provide additional input if desired. ________________________________
Sign up for ICANN's Monthly Magazine http://www.icann.org/magazine/
This message was sent by: ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601
Powered by iContact: http://freetrial.icontact.com
Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=10248929&l=6333&s=96FD&m=167...
*** Scanned
**************************************************************************** ******** SCANNED
**************************************************************************** ******** _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
If the reform of travel policy could make any sense, it should increase the funding for the people from the developing countries, rather than adopting a flat approach. The participants in the developed world can easily join through webcasting and other remote participation facilities, while developing countries have no or expensive access to broadband. With respect to this newly released document, I don't understand why I'm singled out for this policy analysis. Is it a negative comment on my work or for any other reasonable? On 8/14/08, Jacqueline A. Morris <jam@jacquelinemorris.com> wrote:
Hi Beau To me it seems as if the suggestion is that ALAC has the same support as the SOs - that is - NomCom appointed members and then the Chair and half of the remaining ALAC members. Currently that means 5 NomCom, plus 5 others including Chair, so travel support for 10 ALAC persons to each ICANN meeting, with the Chair getting Business Class travel for flights over 5 hours. Discretion of the Chair can determine if the funding is applied to members or other people, such as WG people, Liaisons, RALO etc. NomCom appointed ppl have always had travel support, no matter where they sit (SO, ALAC, etc) and they will continue to have such. People on the NomCom will have funding to NomCom meetings, but only the Chair, Vice Chair will have support to ICANN meetings.
Very importantly, this is for fiscal year 2009-2010, so will not take effect until July 2009.
Jacqueline
Brendler, Beau wrote:
Colleagues...
I have some questions on this -- apologies I have not kept on top of it, due to recent personal circumstances. This document seems vague about the at-large travel budget itself. Here's what I get from these documents referenced in the below news alert:
1. The supporting organizations want and are going to get some additional ICANN funds for travel. So are nomcom appointed people. 2. Chairs and such get some more flexibility and discretion with how travel funding is spent. 3. Because of the expense of the forthcoming at-large summit, the at-large will be considered after the summit to be "matured," and this means: -- limited to no travel funds for those outside the ALAC, i.e., people in ALSs, RALOs, etc. (?) -- limited to no travel funds for the 18-odd people on the ALAC itself (?)
Is this correct?
-----Original Message----- From: ICANN News Alert [mailto:communications@icann.org] Sent: Wed 8/13/2008 2:35 PM To: Brendler, Beau Subject: ICANN News Alert -- ICANN Posts Revised Community Travel Support Procedure for FY09
ICANN News Alert http://www.icann.org/en/announcements/announcement-13aug08-en.htm ________________________________
ICANN Posts Revised Community Travel Support Procedure for FY09 13 August 2008
The work to create a community travel support procedure began with a specific call for travel support in late 2007 by some in the community (though this issue has been discussed for some time). There has been extensive consultation on community travel support. It began as a workshop in Delhi, with comments received and an analysis posted. Further, a draft was posted in June, discussed in budget meetings in Paris, and again with fairly extensive comment in person, via email and on the web. These second round of comments were summarized and analyzed. This last summary is available at:
http://forum.icann.org/lists/travel-support-draft/msg00013.html
The revised Community Travel Support Procedure for FY09 http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08.htm document strives to accommodate the community feedback. Of course, this is a subject about which complete agreement is not possible. However, there is strong agreement within the community that a procedure exist that is documented, transparent, consistent, adhered-to, and reviewed/revised for efficacy.
Comparing the final procedure with the draft discussed in Paris, some key changes include:
* Guarantees travel support for NomCom-nominated counselors * Stresses transparency in application and post-meeting reporting * Allows for some flexibility in the allocation mechanism within a SO without overburdening the Chair
The document strives to be complete without being overly-detailed. This will leave many specific questions unanswered. ICANN staff will develop and post a FAQ (frequently asked questions document) to capture questions, and provide consistent answers to the entire community. If you have questions, please send them to the ICANN staff member with whom you work most closely, or send them to travel-support@icann.org.
Staff will collect feedback on issues that arise in the first implementation of this procedure, now through the Cairo meeting, and Staff will make clarifications, as needed. Additionally, Staff will conduct a complete review of the Community Travel Support Procedure at year end with a public consultation at the June ICANN meeting, and this will be an opportunity for RSSAC to provide additional input if desired. ________________________________
Sign up for ICANN's Monthly Magazine http://www.icann.org/magazine/
This message was sent by: ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601
Powered by iContact: http://freetrial.icontact.com
Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=10248929&l=6333&s=96FD&m=167...
*** Scanned
**************************************************************************** ******** SCANNED
**************************************************************************** ******** _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac
participants (5)
-
Alan Greenberg -
Brendler, Beau -
Hong Xue -
Jacqueline A. Morris -
Nick Ashton-Hart