<html>
<body>
Thanks to Carlton and Greg Mounier for forwarding this letter.<br><br>
I found this letter refreshing. Looking at:<br><br>
- the presence of words such as "pragmatic" and
"workable" (both of which occur twice);<br><br>
- a strong focus not only on law enforcement but the investigations that
lead up to legal action;<br><br>
- the references to the public interest/policy (5 references);<br><br>
- acknowledgement of ICANN's statement "to ensure compliance with
the GDPR while maintaining WHOIS to the greatest extent
possible"<br><br>
gives me some hope that we may get through this mess without destroying
the usability of the Internet.<br><br>
Alan<br><br>
<br><br>
At 30/01/2018 07:57 PM, Carlton Samuels wrote:<br><br>
<blockquote type=cite class=cite cite="">...and while were at it, take a
load of this....<br><br>
<font face="comic sans ms" size=4>
<a href="https://www.icann.org/en/system/files/correspondence/avramopoulos-et-al-to-marby-29jan18-en.pdf">
https://www.icann.org/en/system/files/correspondence/avramopoulos-et-al-to-marby-29jan18-en.pdf</a>
</font><br>
<font face="comic sans ms" size=4><br>
</font>-Carlton<br><br>
<br>
==============================<br>
<font face="comic sans ms"><i>Carlton A Samuels</i></font><br>
<font face="comic sans ms"><i>Mobile: 876-818-1799<br>
</font><font face="comic sans ms" color="#33CC00">Strategy, Planning,
Governance, Assessment & Turnaround</i></font><br>
=============================<br><br>
On Tue, Jan 30, 2018 at 7:13 PM, Lisa Phifer
<<a href="mailto:lisa@corecom.com">lisa@corecom.com</a>>
wrote:<br>
<dl><br>
<dd>Dear all,<br>
</b><br>
<dd>Below please find notes from today’s RDS PDP WG meeting.<br>
</b><br>
<dd>To recap Action Items from today’s call:
<a href="https://community.icann.org/x/8ge8B">
https://community.icann.org/x/8ge8B</a><br>
</b><br>
<dd>Action:</b> Chair to confirm change of VC on mailing list.<br><br>
<dd>Proposed WG agreement (subject to revision and confirmation via
poll):</b> The WG will use the following non-exhaustive list of criterion
to determine if any proposed purpose for processing registration data may
be legitimate: (a) The purpose must not be inconsistent with ICANN's
mission, (d) The purpose must be inherent to the functionality of the
DNS, AND (x) The purpose must satisfy at least one legal basis for
processing as defined by data protection laws.<br><br>
<dd>Action:</b> Leadership team to refine above proposed agreement to
develop poll about this point, along with repeat of Q3 from last week's
poll, with additional granularity, based on agreed criteria. WG members
encouraged to participate in poll no later than Saturday COB.<br><br>
<dd>Best regards,</b><br>
<dd>Lisa<br>
</b><br>
<dd> <br>
</b><br>
<dd>Action Items and Notes from RDS PDP WG Call – 30 January 2018<br>
</u><br>
<dd>These high-level notes are designed to help PDP WG members navigate
through the content of the call and are not meant as a substitute for the
transcript and/or recording. The MP3, transcript, and chat are provided
separately and are posted on the wiki.<br>
</i><br>
<dd>1. Roll Call/SOI Updates
<dd>Please mute when not speaking and give your name when speaking for
the transcript
<dd>SOI Updates:
<ul>
<li>Andrew Sullivan will be a member of the IETF Administrative Oversight
Committee starting at the IETF meeting in March
<li>Chuck Gomes updated his SoI to reflect his support from Verisign
although he is no longer representing Verisign's interests or the RySG
<li>Mason Cole has left Donuts and joined Perkins Coie
</ul>
<li>Confirm Alex Deacon as a member of the WG Leadership Team to replace
Susan.<br>
Action:</b> Chair to confirm change of VC on mailing list.<br><br>
2. Discuss list of criteria that make purposes legitimate for
processing<br><br>
a. See GDPR definition of processing and
<a href="https://community.icann.org/download/attachments/79431666/CommentSummary-24JanuaryPoll-v3.pdf?version=1&modificationDate=1517268227000&api=v2">
Q2 poll results</a>
<li>Handout:
<a href="https://community.icann.org/download/attachments/79431666/Handout-30January-RDSWGCall.pdf">
https://community.icann.org/download/attachments/79431666/Handout-30January-RDSWGCall.pdf</a>
<li>Question 2 from last week's poll:
<li>Do you support the proposed WG Agreement from last week: Criteria to
be used to determine whether any proposed purpose is legitimate for
processing registration data are: a) In support of ICANN's mission; b) A
legitimate interest pursued by the data controller; c) Necessary for the
fulfillment of a contract; d) Inherent to functionality of the DNS; e) In
the public interest; or f) Necessary for compliance with a legal
obligation.</i>
<li>See GDPR definition on
<a href="https://community.icann.org/download/attachments/79431666/Handout-30January-RDSWGCall.pdf">
handout slide 3</a>
<li>Comment Summary:
<a href="https://community.icann.org/download/attachments/79431666/CommentSummary-24JanuaryPoll-v3.pdf">
https://community.icann.org/download/attachments/79431666/CommentSummary-24JanuaryPoll-v3.pdf</a>
<li>Overall, 54% supported ALL listed criteria
<li>Comment Summary shows level of support for each listed criteria,
ranging from 74 - 57%
<li>Summary also shows level of explicit opposition to each listed
criteria
<li>General Comments Discussion:
<ul>
<li>All are encouraged to review the AC recording or transcript of the
previous call to catch up before participating poll whenever possible -
this will improve efficiency of discussions
<li>Does anyone disagree with the statement that this list of criteria
must be non-exhaustive?
<li>Comments: Criteria should be fixed because ICANN's mission is fixed,
GDPR should apply to personal data collected in applicable jurisdictions,
as Internet evolves we may find that other data is needed so cannot be
static, "Valuable and useful to law enforcement" is not enough
to mandate collection - or another view: it is if that information is
deemed important for protecting the DNS. and confidence in it
</ul>
</ul><br>
<dd>Option a) In support of ICANN's mission
<ul>
<ul>
<li>74% support, 1 person explicitly opposed this criteria
<li>Comments about Option a:
<ul>
<li>Are a) AND d) the only valid criteria? No, they are required but
other reasons are valid as well
<li>Do we need to examine all of the criteria before polling (as we did
on the last call)?
<li>Show of hands show more disagreement than agreement at this stage of
discussion
<li>Proposal: (a) would better be phrased as "not inconsistent
with ICANN's mission"
</ul>
<li>Conclusion: Reasonably strong support for a) as one criteria for
determining whether a purpose is legimate for processing registration
data in some way.
</ul>
</ul><br>
<dd> Option b) A legitimate interest pursued by data controller(s)
<ul>
<ul>
<li>60% supported, 7 comments explicitly opposed this
<li>Comments about Option b:
<ul>
<li>Not clear at this point precisely who the data controllers ARE
<li>This shouldn't exclude legitimate interests of third parties or data
processors as enumerated by GDPR
<li>This is a legal basis for processing not a criteria or a purpose
<li>Why do we have criteria other than a) and d) or e)?
<li>Are "third parties" = "operators on the Internet
not involved in the registration of the domain name"
<li>Is this a proxy discussion for how WG members view availability of
registration data?
</ul>
<li>Conclusion: Possible approach to simplify list without enumerating
all of the legal bases from GDPR:
<ul>
<li>The list of criteria could be [ a) plus d) ] plus a new criteria that
the purpose must satisfy at least one legal basis for processing as
defined by GDPR and other data protection laws (where a/d may be
reworded)
<li>Is a) a superset of d) - if so are both needed? They are not
exclusive.
<li>What is the implication of AND or OR in the proposed WG agreement?
Would a purpose have to satisfy all 3 (AND) or just one (OR)?
</ul>
</ul>
</ul><br>
<dd> b. Determine next steps to reach agreement on criteria<br><br>
<dd>Proposed WG agreement (subject to revision and confirmation via
poll):</b> The WG will use the following non-exhaustive list of criterion
to determine if any proposed purpose for processing registration data may
be legitimate: (a) The purpose must not be inconsistent with ICANN's
mission, (d) The purpose must be inherent to the functionality of the
DNS, AND (x) The purpose must satisfy at least one legal basis for
processing as defined by data protection laws.<br><br>
<dd>Action:</b> Leadership team to refine above proposed agreement to
develop poll about this point, along with repeat of Q3 from last week's
poll, with additional granularity, based on agreed criteria. WG members
encouraged to participate in poll no later than Saturday COB.<br><br>
<dd>3. Discuss list of purposes to determine which are legitimate for
processing based on criteria - DEFERRED TO NEXT WEEK<br><br>
<dd>4. Confirm agreements for polling & next steps<br><br>
<dd>Action:</b> Chair to confirm change of VC on mailing list.<br><br>
<dd>Proposed WG agreement (subject to revision and confirmation via
poll):</b> The WG will use the following non-exhaustive list of criterion
to determine if any proposed purpose for processing registration data may
be legitimate: (a) The purpose must not be inconsistent with ICANN's
mission, (d) The purpose must be inherent to the functionality of the
DNS, AND (x) The purpose must satisfy at least one legal basis for
processing as defined by data protection laws.<br><br>
<dd>Action:</b> Leadership team to refine above proposed agreement to
develop poll about this point, along with repeat of Q3 from last week's
poll, with additional granularity, based on agreed criteria. WG members
encouraged to participate in poll no later than Saturday COB.<br><br>
<dd>5. Confirm next meeting: Tuesday 6 February at 17:00 UTC
<dd>February call schedule Tuesdays @ 17:00 except for Wednesday Feb 21 @
06.00<br>
<dd>Meeting Materials</b>:
<a href="https://community.icann.org/x/8ge8B">
https://community.icann.org/x/8ge8B</a><br><br>
<dd>_______________________________________________<br>
<dd>gnso-rds-pdp-wg mailing list<br>
<dd><a href="mailto:gnso-rds-pdp-wg@icann.org">
gnso-rds-pdp-wg@icann.org</a><br>
<dd>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" eudora="autourl">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br><br>
</dl><br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;YQXPR0101MB1589;27:EYZ5yCT5wqwEDnAFyM6J63tg5euDooq+nvuNDubOyijZjl9gquj02AJMr2sR4sWZvlPsZK5jCZSq7djZXF/G9/dFCqBDSkG5NwbFbZxy/WySksmFGj+3tyHBNFMBGVt6<br>
X-Microsoft-Antispam-Message-Info:<br>
<x-tab> </x-tab>
1Grwrwo1bHgdfC88upsJ1FzyjWNExzf2iBTg6jrBWI25yDPaFMuRUkfNZh44RFiRUtR0YSJl7suT7B2qqn8OdhcLaz564Yc1f1KLUukAN8VwsaPjfY2NaCsYXKt8KLp8ImLq1lKhy9U3EpxS2su/LQ==<br>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
gnso-rds-pdp-wg@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" eudora="autourl">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote>
</body>
</html>