Proposed Addition to Jurisdiction Subgroup Report
All, Based on the discussions in the Plenary at ICANN 60, the following task was decided: - Jurisdiction second reading of draft recommendations – Approved with 4 objections but certain edits are required. These include the proposed text from Jorge Cancio with respect to continuing the jurisdiction discussions .... Having reviewed the transcript, including Jorge's intervention, related interventions by others, and Thomas's recapitulation of this point, I have drafted the proposed language below (and also attached) to be added to the Subgroup Report, most likely at the end of the Subgroup Report. I hope that this has captured the spirit of the discussion reasonably well. Greg *FURTHER DISCUSSIONS OF JURISDICTION-RELATED CONCERNS* There were a number of concerns raised in the Subgroup where the Subgroup had substantive discussions, but did not get to a point of conclusion. As an example, there were discussions of limited or partial immunity for ICANN that did not come to conclusion. These concerns were put on the table by different stakeholders, and for these stakeholders, these are legitimate concerns. As these concerns were not discussed to the end, there should be a path forward for these concerns beyond the CCWG-Accountability, which was tasked to look into a limited number of issues within a limited period of time and with a limited budget. Therefore, the Subgroup suggests that a further other multistakeholder process of some kind should be considered to allow for further consideration, and potentially resolution, of these concerns. We believe that this Report, with its annexes, can be a very useful tool for further debates which will surely take place – whether in another cross-constituency effort or in a future ATRT Review, or in some other ICANN context. The appropriate forum for such discussions is beyond the mandate of the CCWG; however, we encourage the community to build on the work of the Subgroup and prior work in this area.
Dear Greg, all Thanks for that. It is fine by me. Best, 2017-11-02 4:36 GMT+01:00 Greg Shatan <gregshatanipc@gmail.com>:
All,
Based on the discussions in the Plenary at ICANN 60, the following task was decided:
- Jurisdiction second reading of draft recommendations – Approved with 4 objections but certain edits are required. These include the proposed text from Jorge Cancio with respect to continuing the jurisdiction discussions ....
Having reviewed the transcript, including Jorge's intervention, related interventions by others, and Thomas's recapitulation of this point, I have drafted the proposed language below (and also attached) to be added to the Subgroup Report, most likely at the end of the Subgroup Report.
I hope that this has captured the spirit of the discussion reasonably well.
Greg
*FURTHER DISCUSSIONS OF JURISDICTION-RELATED CONCERNS*
There were a number of concerns raised in the Subgroup where the Subgroup had substantive discussions, but did not get to a point of conclusion. As an example, there were discussions of limited or partial immunity for ICANN that did not come to conclusion.
These concerns were put on the table by different stakeholders, and for these stakeholders, these are legitimate concerns. As these concerns were not discussed to the end, there should be a path forward for these concerns beyond the CCWG-Accountability, which was tasked to look into a limited number of issues within a limited period of time and with a limited budget.
Therefore, the Subgroup suggests that a further other multistakeholder process of some kind should be considered to allow for further consideration, and potentially resolution, of these concerns. We believe that this Report, with its annexes, can be a very useful tool for further debates which will surely take place – whether in another cross-constituency effort or in a future ATRT Review, or in some other ICANN context. The appropriate forum for such discussions is beyond the mandate of the CCWG; however, we encourage the community to build on the work of the Subgroup and prior work in this area.
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community
-- Raphaël Beauregard-Lacroix LinkedIn <https://www.linkedin.com/in/rapha%C3%ABl-beauregard-lacroix-88733786/> - @rbl0012 <https://twitter.com/rbl0112> - M: +33 7 86 39 18 15
Dear Raphael Good afternoon I hope you are well Finally your baby bien « Menu « Was put on the Table I hope it would grow up and applied I have some doubt and uncertainty that it works but let us wait and test it before drawing any conclusion Regards Kavouss Sent from my iPhone
On 4 Nov 2017, at 15:55, Raphaël BEAUREGARD-LACROIX <raphael.beauregardlacroix@sciencespo.fr> wrote:
Dear Greg, all
Thanks for that. It is fine by me.
Best,
2017-11-02 4:36 GMT+01:00 Greg Shatan <gregshatanipc@gmail.com>:
All,
Based on the discussions in the Plenary at ICANN 60, the following task was decided: Jurisdiction second reading of draft recommendations – Approved with 4 objections but certain edits are required. These include the proposed text from Jorge Cancio with respect to continuing the jurisdiction discussions....
Having reviewed the transcript, including Jorge's intervention, related interventions by others, and Thomas's recapitulation of this point, I have drafted the proposed language below (and also attached) to be added to the Subgroup Report, most likely at the end of the Subgroup Report.
I hope that this has captured the spirit of the discussion reasonably well.
Greg
FURTHER DISCUSSIONS OF JURISDICTION-RELATED CONCERNS There were a number of concerns raised in the Subgroup where the Subgroup had substantive discussions, but did not get to a point of conclusion. As an example, there were discussions of limited or partial immunity for ICANN that did not come to conclusion. These concerns were put on the table by different stakeholders, and for these stakeholders, these are legitimate concerns. As these concerns were not discussed to the end, there should be a path forward for these concerns beyond the CCWG-Accountability, which was tasked to look into a limited number of issues within a limited period of time and with a limited budget. Therefore, the Subgroup suggests that a further other multistakeholder process of some kind should be considered to allow for further consideration, and potentially resolution, of these concerns. We believe that this Report, with its annexes, can be a very useful tool for further debates which will surely take place – whether in another cross-constituency effort or in a future ATRT Review, or in some other ICANN context. The appropriate forum for such discussions is beyond the mandate of the CCWG; however, we encourage the community to build on the work of the Subgroup and prior work in this area.
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community
-- Raphaël Beauregard-Lacroix LinkedIn - @rbl0012 - M: +33 7 86 39 18 15
_______________________________________________ Accountability-Cross-Community mailing list Accountability-Cross-Community@icann.org https://mm.icann.org/mailman/listinfo/accountability-cross-community
participants (3)
-
Arasteh -
Greg Shatan -
Raphaël BEAUREGARD-LACROIX