<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] MSI Panel - updated response
- To: jrobinson@xxxxxxxxxxxx
- Subject: Re: [council] MSI Panel - updated response
- From: Amr Elsadr <aelsadr@xxxxxxxxxxx>
- Date: Tue, 29 Apr 2014 11:05:57 +0200
- Cc: council@xxxxxxxxxxxxxx
- In-reply-to: <006501cf6382$5a886420$0f992c60$@afilias.info>
- List-id: council@xxxxxxxxxxxxxx
- References: <CF84454E.30832%marika.konings@icann.org> <006501cf6382$5a886420$0f992c60$@afilias.info>
- Sender: owner-council@xxxxxxxxxxxxxx
Hi,
Thanks for the edits, John. I personally like them and feel they are helpful in
providing stronger language clarifying the GNSO’s position on the “DRAFT”
blueprint. I have one question though, regarding the added comment on the use
of expert networks:
“At times, ICANN budget has been cited as a barrier to such additional
resources, but in general, the Council has not found this a barrier and has
welcomed ICANN policy staff full engagement in identifying and bringing onboard
subject matter experts specific to PDPs.”
Is there a reference available to support this statement? I’d be interested in
learning more about the circumstances when/why additional expert resources were
deemed desirable, why the ICANN budget was determined to be the limiting factor
in obtaining these resources and how ICANN policy staff managed to resolve the
issue to the Council’s satisfaction.
I bring this up because over the past couple of years, I have observed that
both GNSO PDPs and other ICANN activities have come up short in answering
questions relevant to how gTLD policies are or may be in conflict with privacy
and data protection laws. Examples include the “thick” WHOIS PDP WG’s findings,
the RDS EWG status update report (check section IV-d) and the data retention
requirements of the RAA. These questions aren’t impossible to answer, but in
these circumstances, it appears the necessary expertise was not available.
I was not aware that ICANN’s budget was an issue in our (the ICANN community's)
ability to resolve issues such as these. If it is, I hope we can address it
with a more constructive approach than just affirming it as a barrier. This
seems to be a problem we need to find a solution for. I wouldn’t mind having
something to that effect in our response to the MSI panel.
Thanks.
Amr
On Apr 29, 2014, at 10:09 AM, Jonathan Robinson <jrobinson@xxxxxxxxxxxx> wrote:
> All,
>
> Please see the proposed final response to the MSI Strategy Panel Output in
> both redline and clean versions.
> Thanks to Marika for assisting me in the preparation of these.
>
> This will be submitted by the deadline (tomorrow) unless I receive any other
> final comments.
>
> Thanks,
>
>
> Jonathan
> <Draft Response to MSI Strategy Panel Output - updated 28 April
> 2014.doc><Draft Response to MSI Strategy Panel Output - updated 28 April -
> redline.doc>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|