ALAC/At-Large Improvements Project -- important update
Dear ALAC members, I want to inform you of some changes to the Improvements report based on information Heidi and Seth received. After consulting with ICANN Legal, it has been suggested that the only "final report" appropriate for Board approval would come once the ALAC can report having implemented *all* the recommendations of the ALAC Review WG. At this stage, however, we could report that the ALAC has completed a substantial amount of ALAC Improvements work, including developing specific proposals for the implementation of the ALAC Review WG recommendations. Consequently, it was suggested that the current status report – which need only be submitted by staff (not by the ALAC) – not be called a “final report”’; we are thinking of calling it the "ALAC/At-Large Improvements Project Milestone Report." Still, an endorsement of this Milestone Report by the ALAC would send a strong message to the Board. So I have instructed Staff to start a vote endorsing the report on Sunday. The next steps in the At-Large Improvements Project will be for the ALAC to discuss the implementation of the remaining ALAC Review recommendations and WT proposals in Dakar, including allocating them to existing At-Large Working Groups, creating timelines for their completion, and determining potential resource implications. I would like to be able to submit these details to the Board as soon as practical but hopefully no later than the meeting in Costa Rica (11-16 March 2012). The ALAC could then aim to submit the actual final Final Report -- marking the completion of the implementation of all Improvements recommendations -- to the Board in Prague (24-28 June 2012). Comments/Questions are welcome. Seth and others are working to convert the report into a "Milestone" report as we speak. Best regards, Olivier Crépin-Leblond ALAC Chair
Just one suggestion. Perhaps, rather than calling this an interim or milestone report, the one we submit could be called "phase one". This brings across the point that some of the Improvements have been completed and some are still in progress. A milestone or interim report suggests that none of what was started had been completed. This way we can say that "phase one" (which includes the bylaw revisions) had been completed. Comments? - Evan (on my mobile) On Oct 9, 2011 12:53 PM, "Olivier MJ Crepin-Leblond" <ocl@gih.com> wrote:
Dear ALAC members,
I want to inform you of some changes to the Improvements report based on information Heidi and Seth received. After consulting with ICANN Legal, it has been suggested that the only "final report" appropriate for Board approval would come once the ALAC can report having implemented *all* the recommendations of the ALAC Review WG.
At this stage, however, we could report that the ALAC has completed a substantial amount of ALAC Improvements work, including developing specific proposals for the implementation of the ALAC Review WG recommendations. Consequently, it was suggested that the current status report – which need only be submitted by staff (not by the ALAC) – not be called a “final report”’; we are thinking of calling it the "ALAC/At-Large Improvements Project Milestone Report."
Still, an endorsement of this Milestone Report by the ALAC would send a strong message to the Board. So I have instructed Staff to start a vote endorsing the report on Sunday.
The next steps in the At-Large Improvements Project will be for the ALAC to discuss the implementation of the remaining ALAC Review recommendations and WT proposals in Dakar, including allocating them to existing At-Large Working Groups, creating timelines for their completion, and determining potential resource implications.
I would like to be able to submit these details to the Board as soon as practical but hopefully no later than the meeting in Costa Rica (11-16 March 2012). The ALAC could then aim to submit the actual final Final Report -- marking the completion of the implementation of all Improvements recommendations -- to the Board in Prague (24-28 June 2012).
Comments/Questions are welcome.
Seth and others are working to convert the report into a "Milestone" report as we speak.
Best regards,
Olivier Crépin-Leblond ALAC Chair
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
Hello Evan, thanks for your kind suggestion. However, I believe that we are not actually at "phase one" of the At-Large Improvements. The whole process started with the external review report, a few years ago -- and I am not sure what phase we are in since I've not tracked exactly what constitutes a "phase". "Phase one" would convey the wrong idea that we're actually at the very beginning of the process when we're actually closer to its conclusion. IMHO "Milestone" is more neutral. Warm regards, Olivier On 09/10/2011 23:02, Evan Leibovitch wrote :
Just one suggestion.
Perhaps, rather than calling this an interim or milestone report, the one we submit could be called "phase one". This brings across the point that some of the Improvements have been completed and some are still in progress.
A milestone or interim report suggests that none of what was started had been completed. This way we can say that "phase one" (which includes the bylaw revisions) had been completed.
Comments?
- Evan (on my mobile)
On Oct 9, 2011 12:53 PM, "Olivier MJ Crepin-Leblond" <ocl@gih.com <mailto:ocl@gih.com>> wrote:
Dear ALAC members,
I want to inform you of some changes to the Improvements report based on information Heidi and Seth received. After consulting with ICANN Legal, it has been suggested that the only "final report" appropriate for Board approval would come once the ALAC can report having implemented *all* the recommendations of the ALAC Review WG.
At this stage, however, we could report that the ALAC has completed a substantial amount of ALAC Improvements work, including developing specific proposals for the implementation of the ALAC Review WG recommendations. Consequently, it was suggested that the current status report – which need only be submitted by staff (not by the ALAC) – not be called a “final report”’; we are thinking of calling it the "ALAC/At-Large Improvements Project Milestone Report."
Still, an endorsement of this Milestone Report by the ALAC would send a strong message to the Board. So I have instructed Staff to start a vote endorsing the report on Sunday.
The next steps in the At-Large Improvements Project will be for the ALAC to discuss the implementation of the remaining ALAC Review recommendations and WT proposals in Dakar, including allocating them to existing At-Large Working Groups, creating timelines for their completion, and determining potential resource implications.
I would like to be able to submit these details to the Board as soon as practical but hopefully no later than the meeting in Costa Rica (11-16 March 2012). The ALAC could then aim to submit the actual final Final Report -- marking the completion of the implementation of all Improvements recommendations -- to the Board in Prague (24-28 June 2012).
Comments/Questions are welcome.
Seth and others are working to convert the report into a "Milestone" report as we speak.
Best regards,
Olivier Crépin-Leblond ALAC Chair
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) <https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A...>
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
Hello Olivier, Evan, the question is not just about choosing "phase" or "milestone": it should be about the way ALAC considers its role within ICANN. Let me offer a few thoughts: 1) When to publish? It is common sense that the Final Report should be completed before publication. However, 2 separate things should be considered here: * The legal or formal aspect: General Counsel's office (GCO) is right, and common sense would also have it that a report be considered "final" when all pending matters have been brought to a close. * But more importantly, there is a "political" aspect as well: ALAC should assert itself according to its own assessment of ICANN's overall situation, and not only in reaction to the ALAC Review WG recommendations or GCO's advice on timing. Thus, we should determine if and whether there is a need to call the Board's and our community's attention to progress already made, challenges ahead, and our timeline. 2) "Phase" or "milestone"? We need to take a wider and longer-term view of things. Yes, At-Large has come a long way from (unfairly) perceived irrelevance to being a natural partner. And yes, this progress has been achieved by sending the right type of signals (advice requested from ALAC is provided in a more professional and timely way, better coordination now between different elements of At-Large...). So I would suggest that if we want to send something to the Board now, we should do so by placing our current work in perspective: step 1 was the ALAC Review WG's recommendations, step 2 entailed implementing what could be done quickly, step 3 was taking stock of the ATRT's additional layer of recommendations, step 4 is where we are at now, and step 5 will be the Final Report. The advantage of this (truthful) presentation is that we show we have the bigger picture in mind, and that we're already at step 4 out of 5. If necessary, we should also point out that, several years after the Board Review WG recommendations (e.g. compensation for Directors), some of those latter have still not been implemented either, so we're on an equal footing, and will not accept people in glass houses throwing stones at us (ALAC members all reside in yurts, so there's no risk). IT's high time that the famed multi-stakeholder model, which implies equality, be more thoroughly implemented within ICANN's ACs and SOs, so that advice from ALAC will be considered equivalent to what comes, say, from the GAC. 3) Make the best use of ICANN-42 in Dakar. From Dakar onwards, the Board will go into "sorry I can't look at that now we've got to implement new gTLDs and search for the next CEO" mode. So Dakar is our last chance in 2011 to really get the Board's attention. But what message do we want to deliver? IMO, we should use the joint breakfast opportunity to * Demonstrate that ALAC, though determined to carry out ongoing obligations (implementing the Improvement recommendations, churning out reactive advice), is now sufficiently autonomous in its thinking to have its own, dynamic agenda (how we expect ALAC's advice to be acted upon by the Board; also, I'd be glad to say a few words about our FCWG) * Offer to each member of the Board a 2-page résumé of where ALAC stands now (we're at step 4 out of 5, what else we do, how we are now organized). The idea is that each individual member of the Board should take away from our breakfast, a sense that ALAC has indeed matured, and is worthy of being heeded. Regards, Jean-Jacques. From: Olivier CREPIN-LEBLOND <ocl@gih.com> Date: Sun, 09 Oct 2011 23:35:39 +0200 To: Evan Leibovitch <evan@telly.org> Cc: ALAC Working List <alac@atlarge-lists.icann.org> Subject: Re: [ALAC] ALAC/At-Large Improvements Project -- important update
Hello Evan,
thanks for your kind suggestion. However, I believe that we are not actually at "phase one" of the At-Large Improvements. The whole process started with the external review report, a few years ago -- and I am not sure what phase we are in since I've not tracked exactly what constitutes a "phase". "Phase one" would convey the wrong idea that we're actually at the very beginning of the process when we're actually closer to its conclusion. IMHO "Milestone" is more neutral. Warm regards,
Olivier
On 09/10/2011 23:02, Evan Leibovitch wrote :
Just one suggestion.
Perhaps, rather than calling this an interim or milestone report, the one we submit could be called "phase one". This brings across the point that some of the Improvements have been completed and some are still in progress.
A milestone or interim report suggests that none of what was started had been completed. This way we can say that "phase one" (which includes the bylaw revisions) had been completed.
Comments?
- Evan (on my mobile)
On Oct 9, 2011 12:53 PM, "Olivier MJ Crepin-Leblond" <ocl@gih.com <mailto:ocl@gih.com>> wrote:
Dear ALAC members,
I want to inform you of some changes to the Improvements report based on information Heidi and Seth received. After consulting with ICANN Legal, it has been suggested that the only "final report" appropriate for Board approval would come once the ALAC can report having implemented *all* the recommendations of the ALAC Review WG.
At this stage, however, we could report that the ALAC has completed a substantial amount of ALAC Improvements work, including developing specific proposals for the implementation of the ALAC Review WG recommendations. Consequently, it was suggested that the current status report which need only be submitted by staff (not by the ALAC) not be called a ³final report²¹; we are thinking of calling it the "ALAC/At-Large Improvements Project Milestone Report."
Still, an endorsement of this Milestone Report by the ALAC would send a strong message to the Board. So I have instructed Staff to start a vote endorsing the report on Sunday.
The next steps in the At-Large Improvements Project will be for the ALAC to discuss the implementation of the remaining ALAC Review recommendations and WT proposals in Dakar, including allocating them to existing At-Large Working Groups, creating timelines for their completion, and determining potential resource implications.
I would like to be able to submit these details to the Board as soon as practical but hopefully no later than the meeting in Costa Rica (11-16 March 2012). The ALAC could then aim to submit the actual final Final Report -- marking the completion of the implementation of all Improvements recommendations -- to the Board in Prague (24-28 June 2012).
Comments/Questions are welcome.
Seth and others are working to convert the report into a "Milestone" report as we speak.
Best regards,
Olivier Crépin-Leblond ALAC Chair
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki:
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC>> )
<https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A LAC%29>
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
Hello Jean-Jacques, thank you for your kind message. My answers inline: On 10/10/2011 04:22, Jean-Jacques SUBRENAT wrote :
/Hello Olivier, Evan,/ / / /the question is not just about choosing "phase" or "milestone": it should be about the way ALAC considers its role within ICANN. Let me offer a few thoughts:/ / / /_1) When to publish?_ It is common sense that the Final Report should be completed before publication. However, 2 separate things should be considered here:/
* /The legal or formal aspect: General Counsel's office (GCO) is right, and common sense would also have it that a report be considered "final" when all pending matters have been brought to a close./ * /But more importantly, there is a "political" aspect as well: ALAC should assert itself _according to its own assessment of ICANN's overall situation_, and not only in reaction to the ALAC Review WG recommendations or GCO's advice on timing. Thus, we should determine if and whether there is a need to call the Board's and our community's attention to progress already made, challenges ahead, and our timeline./
I believe that it is good practice, in the interest of transparency and good cross communication, leading by example, to have a report that provides public information about the ALAC's progress - and the very hard work which this community has furnished in the past few years, in addition to all of its work in public policy comments etc. A report was eagerly awaited since we had set ourselves deadlines on completing the work. As it happened, with a new challenges being unearthed at every new stone upturned, we are running late. But we are running late not because of our lazyness; we are running late because of the thoroughness that we are applying to our job. I think that this reflects positively on the level of professionalism that this community is showing - and the Board needs to be reminded of that.
/_2) "Phase" or "milestone"?_ We need to take a wider and longer-term view of things. Yes, At-Large has come a long way from (unfairly) perceived irrelevance to being a natural partner. And yes, this progress has been achieved by sending the right type of signals (advice requested from ALAC is provided in a more professional and timely way, better coordination now between different elements of At-Large...). So I would suggest that if we want to send something to the Board now, we should do so by _placing our current work in perspective_: step 1 was the ALAC Review WG's recommendations, step 2 entailed implementing what could be done quickly, step 3 was taking stock of the ATRT's additional layer of recommendations, step 4 is where we are at now, and step 5 will be the Final Report. The advantage of this (truthful) presentation is that we show we have the bigger picture in mind, and that we're already at step 4 out of 5. If necessary, we should also point out that, several years after the Board Review WG recommendations (e.g. compensation for Directors), some of those latter have still not been implemented either, so we're on an equal footing, and will not accept people in glass houses throwing stones at us (ALAC members all reside in yurts, so there's no risk). IT's high time that the famed multi-stakeholder model, which implies equality, be more thoroughly implemented within ICANN's ACs and SOs, so that advice from ALAC will be considered equivalent to what comes, say, from the GAC. /
I totally agree with you, Jean-Jacques. The report, I think, encompasses all of what you have mentioned here.
/ / /_3) Make the best use of ICANN-42 in Dakar_. From Dakar onwards, the Board will go into "sorry I can't look at that now we've got to implement new gTLDs and search for the next CEO" mode. So Dakar is our last chance in 2011 to really get the Board's attention. But what message do we want to deliver? IMO, we should use the joint breakfast opportunity to/
* /Demonstrate that ALAC, though determined to carry out ongoing obligations (implementing the Improvement recommendations, churning out reactive advice), is now sufficiently autonomous in its thinking to have its own, dynamic agenda (how we expect ALAC's advice to be acted upon by the Board; also, I'd be glad to say a few words about our FCWG)/
Completely agree.
* /Offer to each member of the Board a 2-page résumé of where ALAC stands now (we're at step 4 out of 5, what else we do, how we are now organized). The idea is that each individual member of the Board should take away from our breakfast, a sense that ALAC has indeed matured, and is worthy of being heeded. /
Good idea. Would the document's Executive Summary be enough? With regards to your comment predicting that the Board will go into: "/"sorry I can't look at that now we've got to implement new gTLDs and search for the next CEO"/ mode, I am very concerned about that possibility. I Dearly hope that this is not going to be the case. This kind of thinking for the Board would be totally inadmissible. It is about time that the Board members get organised so as not to end up working on a single subject at a time. I therefore really hope your scenario will not happen. If it does, I believe it is the ALAC's DUTY to pull the alarm trigger that something's systematically wrong at ICANN and needs to be fixed if the organization is to survive. Kind regards, Olivier -- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
A lot of wisdom distilled here. Thank you, Jean Jacques. Carlton ________________________________________ From: alac-bounces@atlarge-lists.icann.org [alac-bounces@atlarge-lists.icann.org] On Behalf Of Jean-Jacques SUBRENAT [jjs.global@gmail.com] Sent: Sunday, October 09, 2011 10:22 PM To: Olivier MJ Crepin-Leblond; Evan Leibovitch Cc: ALAC Working List Subject: Re: [ALAC] ALAC/At-Large Improvements Project -- important update Hello Olivier, Evan, the question is not just about choosing "phase" or "milestone": it should be about the way ALAC considers its role within ICANN. Let me offer a few thoughts: 1) When to publish? It is common sense that the Final Report should be completed before publication. However, 2 separate things should be considered here: * The legal or formal aspect: General Counsel's office (GCO) is right, and common sense would also have it that a report be considered "final" when all pending matters have been brought to a close. * But more importantly, there is a "political" aspect as well: ALAC should assert itself according to its own assessment of ICANN's overall situation, and not only in reaction to the ALAC Review WG recommendations or GCO's advice on timing. Thus, we should determine if and whether there is a need to call the Board's and our community's attention to progress already made, challenges ahead, and our timeline. 2) "Phase" or "milestone"? We need to take a wider and longer-term view of things. Yes, At-Large has come a long way from (unfairly) perceived irrelevance to being a natural partner. And yes, this progress has been achieved by sending the right type of signals (advice requested from ALAC is provided in a more professional and timely way, better coordination now between different elements of At-Large...). So I would suggest that if we want to send something to the Board now, we should do so by placing our current work in perspective: step 1 was the ALAC Review WG's recommendations, step 2 entailed implementing what could be done quickly, step 3 was taking stock of the ATRT's additional layer of recommendations, step 4 is where we are at now, and step 5 will be the Final Report. The advantage of this (truthful) presentation is that we show we have the bigger picture in mind, and that we're already at step 4 out of 5. If necessary, we should also point out that, several years after the Board Review WG recommendations (e.g. compensation for Directors), some of those latter have still not been implemented either, so we're on an equal footing, and will not accept people in glass houses throwing stones at us (ALAC members all reside in yurts, so there's no risk). IT's high time that the famed multi-stakeholder model, which implies equality, be more thoroughly implemented within ICANN's ACs and SOs, so that advice from ALAC will be considered equivalent to what comes, say, from the GAC. 3) Make the best use of ICANN-42 in Dakar. From Dakar onwards, the Board will go into "sorry I can't look at that now we've got to implement new gTLDs and search for the next CEO" mode. So Dakar is our last chance in 2011 to really get the Board's attention. But what message do we want to deliver? IMO, we should use the joint breakfast opportunity to * Demonstrate that ALAC, though determined to carry out ongoing obligations (implementing the Improvement recommendations, churning out reactive advice), is now sufficiently autonomous in its thinking to have its own, dynamic agenda (how we expect ALAC's advice to be acted upon by the Board; also, I'd be glad to say a few words about our FCWG) * Offer to each member of the Board a 2-page résumé of where ALAC stands now (we're at step 4 out of 5, what else we do, how we are now organized). The idea is that each individual member of the Board should take away from our breakfast, a sense that ALAC has indeed matured, and is worthy of being heeded. Regards, Jean-Jacques. From: Olivier CREPIN-LEBLOND <ocl@gih.com> Date: Sun, 09 Oct 2011 23:35:39 +0200 To: Evan Leibovitch <evan@telly.org> Cc: ALAC Working List <alac@atlarge-lists.icann.org> Subject: Re: [ALAC] ALAC/At-Large Improvements Project -- important update
Hello Evan,
thanks for your kind suggestion. However, I believe that we are not actually at "phase one" of the At-Large Improvements. The whole process started with the external review report, a few years ago -- and I am not sure what phase we are in since I've not tracked exactly what constitutes a "phase". "Phase one" would convey the wrong idea that we're actually at the very beginning of the process when we're actually closer to its conclusion. IMHO "Milestone" is more neutral. Warm regards,
Olivier
On 09/10/2011 23:02, Evan Leibovitch wrote :
Just one suggestion.
Perhaps, rather than calling this an interim or milestone report, the one we submit could be called "phase one". This brings across the point that some of the Improvements have been completed and some are still in progress.
A milestone or interim report suggests that none of what was started had been completed. This way we can say that "phase one" (which includes the bylaw revisions) had been completed.
Comments?
- Evan (on my mobile)
On Oct 9, 2011 12:53 PM, "Olivier MJ Crepin-Leblond" <ocl@gih.com <mailto:ocl@gih.com>> wrote:
Dear ALAC members,
I want to inform you of some changes to the Improvements report based on information Heidi and Seth received. After consulting with ICANN Legal, it has been suggested that the only "final report" appropriate for Board approval would come once the ALAC can report having implemented *all* the recommendations of the ALAC Review WG.
At this stage, however, we could report that the ALAC has completed a substantial amount of ALAC Improvements work, including developing specific proposals for the implementation of the ALAC Review WG recommendations. Consequently, it was suggested that the current status report which need only be submitted by staff (not by the ALAC) not be called a ³final report²¹; we are thinking of calling it the "ALAC/At-Large Improvements Project Milestone Report."
Still, an endorsement of this Milestone Report by the ALAC would send a strong message to the Board. So I have instructed Staff to start a vote endorsing the report on Sunday.
The next steps in the At-Large Improvements Project will be for the ALAC to discuss the implementation of the remaining ALAC Review recommendations and WT proposals in Dakar, including allocating them to existing At-Large Working Groups, creating timelines for their completion, and determining potential resource implications.
I would like to be able to submit these details to the Board as soon as practical but hopefully no later than the meeting in Costa Rica (11-16 March 2012). The ALAC could then aim to submit the actual final Final Report -- marking the completion of the implementation of all Improvements recommendations -- to the Board in Prague (24-28 June 2012).
Comments/Questions are welcome.
Seth and others are working to convert the report into a "Milestone" report as we speak.
Best regards,
Olivier Crépin-Leblond ALAC Chair
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki:
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC>> )
<https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A LAC%29>
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
On 10 October 2011 19:14, SAMUELS,Carlton A <carlton.samuels@uwimona.edu.jm>wrote:
A lot of wisdom distilled here.
Thank you, Jean Jacques.
+1 Excellently stated, - Evan
Carlton ________________________________________ From: alac-bounces@atlarge-lists.icann.org [ alac-bounces@atlarge-lists.icann.org] On Behalf Of Jean-Jacques SUBRENAT [ jjs.global@gmail.com] Sent: Sunday, October 09, 2011 10:22 PM To: Olivier MJ Crepin-Leblond; Evan Leibovitch Cc: ALAC Working List Subject: Re: [ALAC] ALAC/At-Large Improvements Project -- important update
Hello Olivier, Evan,
the question is not just about choosing "phase" or "milestone": it should be about the way ALAC considers its role within ICANN. Let me offer a few thoughts:
1) When to publish? It is common sense that the Final Report should be completed before publication. However, 2 separate things should be considered here: * The legal or formal aspect: General Counsel's office (GCO) is right, and common sense would also have it that a report be considered "final" when all pending matters have been brought to a close. * But more importantly, there is a "political" aspect as well: ALAC should assert itself according to its own assessment of ICANN's overall situation, and not only in reaction to the ALAC Review WG recommendations or GCO's advice on timing. Thus, we should determine if and whether there is a need to call the Board's and our community's attention to progress already made, challenges ahead, and our timeline. 2) "Phase" or "milestone"? We need to take a wider and longer-term view of things. Yes, At-Large has come a long way from (unfairly) perceived irrelevance to being a natural partner. And yes, this progress has been achieved by sending the right type of signals (advice requested from ALAC is provided in a more professional and timely way, better coordination now between different elements of At-Large...). So I would suggest that if we want to send something to the Board now, we should do so by placing our current work in perspective: step 1 was the ALAC Review WG's recommendations, step 2 entailed implementing what could be done quickly, step 3 was taking stock of the ATRT's additional layer of recommendations, step 4 is where we are at now, and step 5 will be the Final Report. The advantage of this (truthful) presentation is that we show we have the bigger picture in mind, and that we're already at step 4 out of 5. If necessary, we should also point out that, several years after the Board Review WG recommendations (e.g. compensation for Directors), some of those latter have still not been implemented either, so we're on an equal footing, and will not accept people in glass houses throwing stones at us (ALAC members all reside in yurts, so there's no risk). IT's high time that the famed multi-stakeholder model, which implies equality, be more thoroughly implemented within ICANN's ACs and SOs, so that advice from ALAC will be considered equivalent to what comes, say, from the GAC.
3) Make the best use of ICANN-42 in Dakar. From Dakar onwards, the Board will go into "sorry I can't look at that now we've got to implement new gTLDs and search for the next CEO" mode. So Dakar is our last chance in 2011 to really get the Board's attention. But what message do we want to deliver? IMO, we should use the joint breakfast opportunity to * Demonstrate that ALAC, though determined to carry out ongoing obligations (implementing the Improvement recommendations, churning out reactive advice), is now sufficiently autonomous in its thinking to have its own, dynamic agenda (how we expect ALAC's advice to be acted upon by the Board; also, I'd be glad to say a few words about our FCWG) * Offer to each member of the Board a 2-page résumé of where ALAC stands now (we're at step 4 out of 5, what else we do, how we are now organized). The idea is that each individual member of the Board should take away from our breakfast, a sense that ALAC has indeed matured, and is worthy of being heeded. Regards, Jean-Jacques.
From: Olivier CREPIN-LEBLOND <ocl@gih.com> Date: Sun, 09 Oct 2011 23:35:39 +0200 To: Evan Leibovitch <evan@telly.org> Cc: ALAC Working List <alac@atlarge-lists.icann.org> Subject: Re: [ALAC] ALAC/At-Large Improvements Project -- important update
Hello Evan,
thanks for your kind suggestion. However, I believe that we are not actually at "phase one" of the At-Large Improvements. The whole process started with the external review report, a few years ago -- and I am not sure what phase we are in since I've not tracked exactly what constitutes a "phase". "Phase one" would convey the wrong idea that we're actually at the very beginning of the process when we're actually closer to its conclusion. IMHO "Milestone" is more neutral. Warm regards,
Olivier
On 09/10/2011 23:02, Evan Leibovitch wrote :
Just one suggestion.
Perhaps, rather than calling this an interim or milestone report, the one we submit could be called "phase one". This brings across the point that some of the Improvements have been completed and some are still in progress.
A milestone or interim report suggests that none of what was started had been completed. This way we can say that "phase one" (which includes the bylaw revisions) had been completed.
Comments?
- Evan (on my mobile)
On Oct 9, 2011 12:53 PM, "Olivier MJ Crepin-Leblond" <ocl@gih.com <mailto:ocl@gih.com>> wrote:
Dear ALAC members,
I want to inform you of some changes to the Improvements report based on information Heidi and Seth received. After consulting with ICANN Legal, it has been suggested that the only "final report" appropriate for Board approval would come once the ALAC can report having implemented *all* the recommendations of the ALAC Review WG.
At this stage, however, we could report that the ALAC has completed
a
substantial amount of ALAC Improvements work, including developing specific proposals for the implementation of the ALAC Review WG recommendations. Consequently, it was suggested that the current status report which need only be submitted by staff (not by the ALAC) not be called a ³final report²¹; we are thinking of calling it the "ALAC/At-Large Improvements Project Milestone Report."
Still, an endorsement of this Milestone Report by the ALAC would send a strong message to the Board. So I have instructed Staff to start a vote endorsing the report on Sunday.
The next steps in the At-Large Improvements Project will be for the ALAC to discuss the implementation of the remaining ALAC Review recommendations and WT proposals in Dakar, including allocating them to existing At-Large Working Groups, creating timelines for their completion, and determining potential resource implications.
I would like to be able to submit these details to the Board as soon as practical but hopefully no later than the meeting in Costa Rica
(11-16
March 2012). The ALAC could then aim to submit the actual final
Final
Report -- marking the completion of the implementation of all Improvements recommendations -- to the Board in Prague (24-28 June 2012).
Comments/Questions are welcome.
Seth and others are working to convert the report into a
"Milestone"
report as we speak.
Best regards,
Olivier Crépin-Leblond ALAC Chair
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki:
)
<
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A
LAC%29>
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki:
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)<https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC%29>
Plus 1 more appreciation for your thoughts and sophisticated orientation -- thanks a lot, Jean-Jacques! Best, Wolf SAMUELS,Carlton A wrote Mon, 10 Oct 2011 18:14:
A lot of wisdom distilled here.
Thank you, Jean Jacques.
Carlton ________________________________________ From: alac-bounces@atlarge-lists.icann.org [alac-bounces@atlarge-lists.icann.org] On Behalf Of Jean-Jacques SUBRENAT [jjs.global@gmail.com] Sent: Sunday, October 09, 2011 10:22 PM To: Olivier MJ Crepin-Leblond; Evan Leibovitch Cc: ALAC Working List Subject: Re: [ALAC] ALAC/At-Large Improvements Project -- important update
Hello Olivier, Evan,
the question is not just about choosing "phase" or "milestone": it should be about the way ALAC considers its role within ICANN. Let me offer a few thoughts:
1) When to publish? It is common sense that the Final Report should be completed before publication. However, 2 separate things should be considered here: * The legal or formal aspect: General Counsel's office (GCO) is right, and common sense would also have it that a report be considered "final" when all pending matters have been brought to a close. * But more importantly, there is a "political" aspect as well: ALAC should assert itself according to its own assessment of ICANN's overall situation, and not only in reaction to the ALAC Review WG recommendations or GCO's advice on timing. Thus, we should determine if and whether there is a need to call the Board's and our community's attention to progress already made, challenges ahead, and our timeline. 2) "Phase" or "milestone"? We need to take a wider and longer-term view of things. Yes, At-Large has come a long way from (unfairly) perceived irrelevance to being a natural partner. And yes, this progress has been achieved by sending the right type of signals (advice requested from ALAC is provided in a more professional and timely way, better coordination now between different elements of At-Large...). So I would suggest that if we want to send something to the Board now, we should do so by placing our current work in perspective: step 1 was the ALAC Review WG's recommendations, step 2 entailed implementing what could be done quickly, step 3 was taking stock of the ATRT's additional layer of recommendations, step 4 is where we are at now, and step 5 will be the Final Report. The advantage of this (truthful) presentation is that we show we have the bigger picture in mind, and that we're already at step 4 out of 5. If necessary, we should also point out that, several years after the Board Review WG recommendations (e.g. compensation for Directors), some of those latter have still not been implemented either, so we're on an equal footing, and will not accept people in glass houses throwing stones at us (ALAC members all reside in yurts, so there's no risk). IT's high time that the famed multi-stakeholder model, which implies equality, be more thoroughly implemented within ICANN's ACs and SOs, so that advice from ALAC will be considered equivalent to what comes, say, from the GAC.
3) Make the best use of ICANN-42 in Dakar. From Dakar onwards, the Board will go into "sorry I can't look at that now we've got to implement new gTLDs and search for the next CEO" mode. So Dakar is our last chance in 2011 to really get the Board's attention. But what message do we want to deliver? IMO, we should use the joint breakfast opportunity to * Demonstrate that ALAC, though determined to carry out ongoing obligations (implementing the Improvement recommendations, churning out reactive advice), is now sufficiently autonomous in its thinking to have its own, dynamic agenda (how we expect ALAC's advice to be acted upon by the Board; also, I'd be glad to say a few words about our FCWG) * Offer to each member of the Board a 2-page résumé of where ALAC stands now (we're at step 4 out of 5, what else we do, how we are now organized). The idea is that each individual member of the Board should take away from our breakfast, a sense that ALAC has indeed matured, and is worthy of being heeded. Regards, Jean-Jacques.
From: Olivier CREPIN-LEBLOND <ocl@gih.com> Date: Sun, 09 Oct 2011 23:35:39 +0200 To: Evan Leibovitch <evan@telly.org> Cc: ALAC Working List <alac@atlarge-lists.icann.org> Subject: Re: [ALAC] ALAC/At-Large Improvements Project -- important update
Hello Evan,
thanks for your kind suggestion. However, I believe that we are not actually at "phase one" of the At-Large Improvements. The whole process started with the external review report, a few years ago -- and I am not sure what phase we are in since I've not tracked exactly what constitutes a "phase". "Phase one" would convey the wrong idea that we're actually at the very beginning of the process when we're actually closer to its conclusion. IMHO "Milestone" is more neutral. Warm regards,
Olivier
On 09/10/2011 23:02, Evan Leibovitch wrote :
Just one suggestion.
Perhaps, rather than calling this an interim or milestone report, the one we submit could be called "phase one". This brings across the point that some of the Improvements have been completed and some are still in progress.
A milestone or interim report suggests that none of what was started had been completed. This way we can say that "phase one" (which includes the bylaw revisions) had been completed.
Comments?
- Evan (on my mobile)
On Oct 9, 2011 12:53 PM, "Olivier MJ Crepin-Leblond" <ocl@gih.com <mailto:ocl@gih.com>> wrote:
Dear ALAC members,
I want to inform you of some changes to the Improvements report based on information Heidi and Seth received. After consulting with ICANN Legal, it has been suggested that the only "final report" appropriate for Board approval would come once the ALAC can report having implemented *all* the recommendations of the ALAC Review WG.
At this stage, however, we could report that the ALAC has completed a substantial amount of ALAC Improvements work, including developing specific proposals for the implementation of the ALAC Review WG recommendations. Consequently, it was suggested that the current status report which need only be submitted by staff (not by the ALAC) not be called a ³final report²¹; we are thinking of calling it the "ALAC/At-Large Improvements Project Milestone Report."
Still, an endorsement of this Milestone Report by the ALAC would send a strong message to the Board. So I have instructed Staff to start a vote endorsing the report on Sunday.
The next steps in the At-Large Improvements Project will be for the ALAC to discuss the implementation of the remaining ALAC Review recommendations and WT proposals in Dakar, including allocating them to existing At-Large Working Groups, creating timelines for their completion, and determining potential resource implications.
I would like to be able to submit these details to the Board as soon as practical but hopefully no later than the meeting in Costa Rica (11-16 March 2012). The ALAC could then aim to submit the actual final Final Report -- marking the completion of the implementation of all Improvements recommendations -- to the Board in Prague (24-28 June 2012).
Comments/Questions are welcome.
Seth and others are working to convert the report into a "Milestone" report as we speak.
Best regards,
Olivier Crépin-Leblond ALAC Chair
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org <mailto:ALAC@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki:
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC>> )
<https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28A LAC%29>
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
EuroDIG Secretariat http://www.eurodig.org/ mobile +41 79 204 83 87 Skype: Wolf-Ludwig EURALO - ICANN's Regional At-Large Organisation http://euralo.org Profile on LinkedIn http://ch.linkedin.com/in/wolfludwig
Dear Olivier, I think that "nous aurons du pain sur la planche" as the French people say. There is a problem in the poll dates: while it was written in the announce that it opens on 9 October 2011 and closes on 14 October 2011, the dates on the poll are 31 March 2011 - 6 April 2011. So, the vote is not possible since we are far behind 6 April. ---------------------------------------------------------- Tijani BEN JEMAA Executive Director Mediterranean Federation of Internet Associations Phone : + 216 70 825 231 Mobile : + 216 98 330 114 Fax : + 216 70 825 231 ---------------------------------------------------------- -----Message d'origine----- De : alac-bounces@atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] De la part de Olivier MJ Crepin-Leblond Envoyé : dimanche 9 octobre 2011 17:52 À : ALAC Working List Objet : [ALAC] ALAC/At-Large Improvements Project -- important update Dear ALAC members, I want to inform you of some changes to the Improvements report based on information Heidi and Seth received. After consulting with ICANN Legal, it has been suggested that the only "final report" appropriate for Board approval would come once the ALAC can report having implemented *all* the recommendations of the ALAC Review WG. At this stage, however, we could report that the ALAC has completed a substantial amount of ALAC Improvements work, including developing specific proposals for the implementation of the ALAC Review WG recommendations. Consequently, it was suggested that the current status report which need only be submitted by staff (not by the ALAC) not be called a final report; we are thinking of calling it the "ALAC/At-Large Improvements Project Milestone Report." Still, an endorsement of this Milestone Report by the ALAC would send a strong message to the Board. So I have instructed Staff to start a vote endorsing the report on Sunday. The next steps in the At-Large Improvements Project will be for the ALAC to discuss the implementation of the remaining ALAC Review recommendations and WT proposals in Dakar, including allocating them to existing At-Large Working Groups, creating timelines for their completion, and determining potential resource implications. I would like to be able to submit these details to the Board as soon as practical but hopefully no later than the meeting in Costa Rica (11-16 March 2012). The ALAC could then aim to submit the actual final Final Report -- marking the completion of the implementation of all Improvements recommendations -- to the Board in Prague (24-28 June 2012). Comments/Questions are welcome. Seth and others are working to convert the report into a "Milestone" report as we speak. Best regards, Olivier Crépin-Leblond ALAC Chair _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA C) ----- Aucun virus trouvé dans ce message. Analyse effectuée par AVG - www.avg.fr Version: 10.0.1390 / Base de données virale: 1518/3785 - Date: 24/07/2011 La Base de données des virus a expiré.
Dear Tijani, you are absolutely right, there is much work to be done. As for error in dates, this is being corrected as we speak. Kind regards, Olivier On 10/10/2011 10:44, tijani.benjemaa@fmai.org wrote :
Dear Olivier,
I think that "nous aurons du pain sur la planche" as the French people say.
There is a problem in the poll dates: while it was written in the announce that it opens on 9 October 2011 and closes on 14 October 2011, the dates on the poll are 31 March 2011 - 6 April 2011. So, the vote is not possible since we are far behind 6 April.
---------------------------------------------------------- Tijani BEN JEMAA Executive Director Mediterranean Federation of Internet Associations Phone : + 216 70 825 231 Mobile : + 216 98 330 114 Fax : + 216 70 825 231 ----------------------------------------------------------
-----Message d'origine----- De : alac-bounces@atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] De la part de Olivier MJ Crepin-Leblond Envoyé : dimanche 9 octobre 2011 17:52 À : ALAC Working List Objet : [ALAC] ALAC/At-Large Improvements Project -- important update
Dear ALAC members,
I want to inform you of some changes to the Improvements report based on information Heidi and Seth received. After consulting with ICANN Legal, it has been suggested that the only "final report" appropriate for Board approval would come once the ALAC can report having implemented *all* the recommendations of the ALAC Review WG.
At this stage, however, we could report that the ALAC has completed a substantial amount of ALAC Improvements work, including developing specific proposals for the implementation of the ALAC Review WG recommendations. Consequently, it was suggested that the current status report – which need only be submitted by staff (not by the ALAC) – not be called a “final report”’; we are thinking of calling it the "ALAC/At-Large Improvements Project Milestone Report."
Still, an endorsement of this Milestone Report by the ALAC would send a strong message to the Board. So I have instructed Staff to start a vote endorsing the report on Sunday.
The next steps in the At-Large Improvements Project will be for the ALAC to discuss the implementation of the remaining ALAC Review recommendations and WT proposals in Dakar, including allocating them to existing At-Large Working Groups, creating timelines for their completion, and determining potential resource implications.
I would like to be able to submit these details to the Board as soon as practical but hopefully no later than the meeting in Costa Rica (11-16 March 2012). The ALAC could then aim to submit the actual final Final Report -- marking the completion of the implementation of all Improvements recommendations -- to the Board in Prague (24-28 June 2012).
Comments/Questions are welcome.
Seth and others are working to convert the report into a "Milestone" report as we speak.
Best regards,
Olivier Crépin-Leblond ALAC Chair
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA C)
----- Aucun virus trouvé dans ce message. Analyse effectuée par AVG - www.avg.fr Version: 10.0.1390 / Base de données virale: 1518/3785 - Date: 24/07/2011 La Base de données des virus a expiré.
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
participants (6)
-
Evan Leibovitch -
Jean-Jacques SUBRENAT -
Olivier MJ Crepin-Leblond -
SAMUELS,Carlton A -
tijani.benjemaa＠fmai.org -
Wolf Ludwig