[Ws2-jurisdiction] More Volunteers Needed: Litigation Review Team, Questionnaire Response Review Team

[Mathieu Weill]

Dear Christopher,



Can I suggest that you relay the questionnaire on the lists you are
mentioning ? I think we can all be part of the outreach effort.



Best

Mathieu



De : ws2-jurisdiction-bounces at icann.org
[mailto:ws2-jurisdiction-bounces at icann.org] De la part de CW Mail
Envoyé : samedi 4 mars 2017 11:05
À : Greg Shatan
Cc : ws2-jurisdiction
Objet : Re: [Ws2-jurisdiction] More Volunteers Needed: Litigation Review
Team, Questionnaire Response Review Team



Dear Greg:



1.         Litigation Review: I shall abstain for lack of legal
competence. I assume the team will review DCA and Karl Auerbach's original
case, among others.



2.         Questionnaires Review: In principle, I would volunteer. However
i would first like to be reassured as to whom the questionnaire has been
addressed. e.g.



            -           I believe that a request to respond has not yet
been addressed proactively to all the participants in any of the Lists  to
which I subscribe.



            -           I recall suggesting that the questionnaire should
be addressed, proactively by iCANN, to all the Registries and Registrars
and other parties that were addressed during the CCT Studies.

                        Has that been done?



This is important because responses from a limited group of CCWG faithful
will hardly contribute to the relevance of the enquiry.

Also, the relevant community is mostly not in the United Staters.



Regarding EU Privacy law, ICANN has been informed frequently and
authoritatively, over the years, that ICANN policy and US jurisdiction
(which?) are inconsistent with all EU-based gTLD Registrars and
Registrants respecting EU law.



I assume that the review team is not expecting to receive individual
responses from all of them to this effect!



Best regards



CW





On 03 Mar 2017, at 23:38, Greg Shatan <gregshatanipc at gmail.com> wrote:





All,



On this week's call, we discussed two small teams to be populated by
volunteers from the Subgroup.  We have some volunteers, but we need more.



1.  Litigation Review Team.  Mathieu Weill, David McAuley, myself, Avri
Doria and Vidushi Marda are in this team, reviewing and summarizing the
litigations that ICANN has been involved in.  We need a few more
volunteers.  Please respond if you can review -- even one review will be
helpful.



2.  Questionnaire Response Review Team.  We need a team to (a) develop a
proposal for how the team will review and evaluate responses to the
questionnaire (for the approval of the Subgroup), (b) carry out the review
and evaluation of the responses (both individually and in the aggregate,
to the extent contemplated by the proposal approved by the Subgroup, and
(c) recommend how the responses be applied to our work and documents.
Please respond if you can join this team (and if you are interested in
coordinating it).



Initial volunteers are Mathieu, David, Vidushi, Kavouss, Parminder and
myself.  If you can join this group, please respond.



While either group can be joined at any time (but sooner than later),
those joining the Questionnaire team now/soon will be there to participate
in the development of the proposal described in 2(a) above.



I want to thank Mathieu, David and Vidushi for doing "double duty" by
joining both teams.  However, given the number of participants in this
Subgroup, that really should not be necessary.  Please consider
volunteering for one of these groups if you haven't done so already.



Thank you!



Greg







--

Greg Shatan
C: 917-816-6428
S: gsshatan
Phone-to-Skype: 646-845-9428
 <mailto:gregshatanipc at gmail.com> gregshatanipc at gmail.com



_______________________________________________
Ws2-jurisdiction mailing list
Ws2-jurisdiction at icann.org
https://mm.icann.org/mailman/listinfo/ws2-jurisdiction



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ws2-jurisdiction/attachments/20170306/d2674c60/attachment.html>