<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Lisa,</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Well,</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Im extremely impressed at your ability to document how to find this. I could never have accomplished it.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">But perhaps we can more succinctly document agreements along the way in a single document with each item of agreement coupled with citations? That way everyone has the same access you have carefully described.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">And, since we are now going to discuss what should and should not be included in TD, perhaps the agreements will need revision.</div><div id="AppleMailSignature"><br>Sent from my iPad</div><div><br>On 9 Jun 2017, at 00:01, Lisa Phifer <<a href="mailto:lisa@corecom.com">lisa@corecom.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
Hi Tim,<br><br>
In general, to find the deliberation leading to any WG agreement, check
the first page of the working document to identify the date of the call
which produced the agreement. Consult the wiki page for that meeting to
review notes, transcript, and recordings. Often it is helpful to review
the previous or following meeting too, since agreements proposed in one
call are polled on after that call and revisited in the next
call.<br><br>
Here, WG Agreement #14 is located in section 4.1 of the working document.
As noted on the first page of the working document, agreements from the
14 February call were added to section 4.1. The meeting page for the 14
February call is found here:
<a href="https://community.icann.org/display/gTLDRDS/2017-02-14+Next+Gen+RDS+PDP+Working+Group" eudora="autourl">
https://community.icann.org/display/gTLDRDS/2017-02-14+Next+Gen+RDS+PDP+Working+Group<br>
<br>
</a>Consulting the 14 February meeting page, this proposed agreement was
discussed under agenda item 3) Continue deliberation on the Privacy
charter question. You can read deliberation leading to this agreement in
the transcript:
<a href="https://community.icann.org/download/attachments/64065654/transcript%20RDS%2014%20Feb%202017.pdf" eudora="autourl">
https://community.icann.org/download/attachments/64065654/transcript%20RDS%2014%20Feb%202017.pdf</a>
, or play back the MP3 recording. The bulk of this meeting covered data
protection principles around purpose specification; the meeting concluded
with a "red X green check" test of support for this proposed WG
agreement. Given support from those on the call, the proposed agreement
was tested in this poll:
<a href="https://community.icann.org/download/attachments/64069381/SummaryResults-Poll-on-Privacy-from-14FebCall.pdf" eudora="autourl">
https://community.icann.org/download/attachments/64069381/SummaryResults-Poll-on-Privacy-from-14FebCall.pdf</a>
<br><br>
Poll results are always discussed the following week; see the notes,
transcript, and recording of the 22 February call, found here:
<a href="https://community.icann.org/display/gTLDRDS/2017-02-22+Next+Gen+RDS+PDP+Working+Group" eudora="autourl">
https://community.icann.org/display/gTLDRDS/2017-02-22+Next+Gen+RDS+PDP+Working+Group</a>
. In this case, notes indicate that poll respondents supported the
agreement 11:2, with some further discussion.<br><br>
I hope you find this helpful to find and review this WG's deliberation
leading to rough consensus on WG Agreement #14.<br><br>
Additionally, you note below "I'm challenged in understanding how
the EWG concluded that, pertaining to only thin whois, this statement #14
is relevant or even accurate." <br><br>
To be clear, the EWG didn't. The EWG never deliberated on WG agreement
#14, or even on thin data. The EWG's mandate was to re-examine and define
the purpose of collecting and maintaining registration data, consider how
to safeguard the data, and propose a next-generation solution to better
server the needs of the global Internet community. Excerpts from the EWG
Report are included in our working document as a starting point to inform
this WG's deliberation. However, as you note, usually those excerpts
touch on non-thin data because the EWG never cut the problem into
"thin" and "thick" as this WG has done. It was this
WG that formulated Agreement #14 as a proposed answer to this WG's
charter question on Privacy, reframed to focus on "thin data"
only.<br><br>
Best, Lisa<br><br>
<br>
At 04:19 PM 6/7/2017, Chen, Tim wrote:<br>
<blockquote type="cite" class="cite" cite="">Hi Chuck,<br><br>
Not meaning to start a long thread here, but copying the RDS WG in case
anyone else has a comment.<br><br>
I reviewed the recently routed
<a href="https://community.icann.org/download/attachments/59644409/Next%20Generation%20RDS%20PDP%20-%20Newsletter%20-%20April-May%202017.pdf?version=1&modificationDate=1496694757381&api=v2">
April/May update newsletter</a>. Thank you to the person or people
who worked to put that together, it was a useful summary.<br><br>
My question regards item #14 in the initial points of rough consensus,
found on Page 3 of that document. For reference here is what it
says:<br><br>
"For thin data only, do existing gTLD registration directory
services policies sufficiently address compliance with applicable data
protection, privacy and free speech laws about purpose?<br>
#14. Â <i>Existing gTLD RDS policies do NOT sufficiently address
compliance with applicable data protection, privacy, and free speech laws
about purpose.</i>"<br><br>
First I want to note that I engaged in this WG around the time of
Copenhagen so I'm very open to you pointing me to something that I may
have missed prior, or some poll that I missed along the way.<br><br>
But I have no recall of when we agreed that this was a 'rough
consensus'. It strikes me that a lot of the dialogue on this WG
recently has been about how thin data is not where we need to be fighting
the privacy battle, and more specifically there are foundational reasons
today's thin data is necessary in an open and ungated protocol. Â
<br><br>
I went to the linked "31 May, 2017 Working Draft on Key Concepts,
Deliberation document" (see Page 2) and navigated to Section 4.1 on
page 15. A lot of that referred text from the EWG is talking about
"contact information" and such things only found in thick
whois. I'm challenged in understanding how the EWG concluded that,
pertaining to only thin whois, this statement #14 is relevant or even
accurate. Maybe there is something specific to the words 'about
purpose' at the end of the statement that I am not comprehending well.Â
<br><br>
Thank you in advance for any context you (or anyone else) can
provide.<br><br>
-Tim Chen<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><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>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>gnso-rds-pdp-wg mailing list</span><br><span><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div></blockquote></body></html>