<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<p class="MsoNoSpacing" style="font-family: 'Times New Roman', serif; font-size: 12pt; margin: 0in 0in 0.0001pt;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Dear All,<o:p></o:p></span></p>
<p class="MsoNoSpacing" style="font-family: 'Times New Roman', serif; font-size: 12pt; margin: 0in 0in 0.0001pt;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNoSpacing" style="font-family: 'Times New Roman', serif; margin: 0in 0in 0.0001pt; font-size: 12pt;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Please find the attendance of the call attached to this email and the MP3 recording below for the Next-Gen RDS PDP Working group call held on Tuesday, 26 April 2016 at 15:30 UTC.<o:p></o:p></span></p>
<p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; line-height: 15.6pt;">
<font face="Calibri"><b>Data Sub-Team Mp3:</b> </font><a href="http://audio.icann.org/gnso/gnso-nextgen-rds-data-26apr16-en.mp3" style="font-size: 14px;">http://audio.icann.org/gnso/gnso-nextgen-rds-data-26apr16-en.mp3</a></p>
<p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; line-height: 15.6pt;">
<font face="Calibri"><b>Privacy Sub-Team Mp3:</b> </font><a href="http://audio.icann.org/gnso/gnso-nextgen-rds-privacy-26apr16-en.mp3" style="font-size: 14px;">http://audio.icann.org/gnso/gnso-nextgen-rds-privacy-26apr16-en.mp3</a></p>
<p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; line-height: 15.6pt;">
<font face="Calibri"><b>Purpose Sub-Team Mp3:</b> </font><a href="http://audio.icann.org/gnso/gnso-nextgen-rds-purpose-26apr16-en.mp3" style="font-size: 14px;">http://audio.icann.org/gnso/gnso-nextgen-rds-purpose-26apr16-en.mp3</a></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:<o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"><a href="http://gnso.icann.org/en/group-activities/calendar#nov" style="color: purple;">http://gnso.icann.org/en/group-activities/calendar</a><o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">** Please let me know if your name has been left off the list **<o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Mailing list archives:<a href="http://mm.icann.org/pipermail/gnso-rds-pdp-wg/" style="color: purple;">http://mm.icann.org/pipermail/gnso-rds-pdp-wg/</a><o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Wiki page: <a href="https://community.icann.org/x/rjJ-Ag" style="color: purple;">https://community.icann.org/x/rjJ-Ag</a> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-family: 'Times New Roman', serif;">
<span style="font-family: Calibri, sans-serif;">Thank you.<o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-family: 'Times New Roman', serif;">
<span style="font-family: Calibri, sans-serif;">Kind regards,<font size="3"><o:p></o:p></font></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt;"><font face="Calibri">Michelle DeSmyter<span style="font-size: 12pt;"> </span></font></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">-------------------------------<o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Adobe Connect chat transcript for Tuesday, 26 April 2016</span></b></p>
<div> Michelle DeSmyter:Dear All, Welcome to the Next-Gen RDS PDP Working Group call on Tuesday, 27 April 2016. </div>
<div> Michelle DeSmyter:: member page/SOI: <a href="https://community.icann.org/x/I4xlAw">https://community.icann.org/x/I4xlAw</a></div>
<div> Michelle DeSmyter:Agenda page: <a href="https://community.icann.org/x/-0WAAw">https://community.icann.org/x/-0WAAw</a></div>
<div> Michelle DeSmyter:: If you do wish to speak during the call, please either dial into the audio bridge and give the operator the password RDS, OR click on the telephone icon at the top of the AC room to activate your AC mics. Please remember to mute your
phone and mics when not talking.</div>
<div> Jim Galvin (Afilias):We're back to the small chat room. Any chance of changing that before we get started?</div>
<div> Michele Neylon:afternoon</div>
<div> Marika Konings:@Jim - we will be live editing on the screen so for this specific meeting we thought it would be better to have that content displayed as big as possible.</div>
<div> Marika Konings:We'll change it back for the next meeting.</div>
<div> Jim Galvin (Afilias):@Marika - Understand. Thanks.</div>
<div> Jim Galvin (Afilias):@Michele - morning.</div>
<div> Ayden Férdeline:Hello to all</div>
<div> Amr Elsadr:Hi Michele and all.</div>
<div> Richard Padilla:Hi everyone</div>
<div> Vlad Dinculescu:Hi All.</div>
<div> Aarti Bhavana:Hello all</div>
<div> Jennifer Gore:hello</div>
<div> Nathalie Coupet:Hello</div>
<div> Sana Ali:Hi</div>
<div> Chuck Gomes:Great turnout from the Data Team.</div>
<div> Vlad Dinculescu:Yes probably. Come back to me later</div>
<div> Vlad Dinculescu:Sorry :(</div>
<div> Amr Elsadr:Dislaimer: I've been extremely inactive on all subteams. Been busy lately, but am trying to catch up.</div>
<div> Vlad Dinculescu:Yes, thw Whois Task Force 2003 I believe</div>
<div> Vlad Dinculescu:That was superceded by the 2007 report</div>
<div> Lisa Phifer:@Vlad 2012 WHOIS RT report is arguably a successor to the 2007 TF report, but the reports are all relevant as history of discussion on this issue</div>
<div> Alex Deacon:Current focus seems to be more on data that is currently displayed in WHOIS. I suppose this is a subset of data collected by registratrs during registration. Do we need to account for data collected but not made available in the (current)
WHOIS? </div>
<div> Vlad Dinculescu:@Lisa Completely agree. That would have been my first point if my mic hadnt failed me :)</div>
<div> Amr Elsadr:@Michele: There was another EWG specific to IRD. I believe Jim chaired that.</div>
<div> Lisa Phifer:@Amr we should probably add IRD report to list of inputs</div>
<div> Ayden Férdeline:@Alex - Hi, what data is being collected but not published? Do you mean registrar-registrant contract information?</div>
<div> Amr Elsadr:If there is still time, I'd be happy to do some work on IRD.</div>
<div> Lisa Phifer:@Amr that would be great - shall I add to input list and assign summary to you?</div>
<div> Alex Deacon:sorry - switching to land line. give me a few mins. </div>
<div> Amr Elsadr:@Lisa: Yes, thank you.</div>
<div> Vlad Dinculescu:@Michele: I think those are the most important. The WTF Final Report is a good foundation for what was required in the past, and mostly whst is still required</div>
<div> Amr Elsadr:@Michele: Could you please repeat the question?</div>
<div> Amr Elsadr:Thanks.</div>
<div> Vlad Dinculescu:@Michele: SAC 54 and the RA gives us the "now" of what is requried</div>
<div> Jeffrey Eckhaus:It may not be important , but could be relevant to discussions </div>
<div> Amr Elsadr:WTF report!! :)</div>
<div> Lisa Phifer:Awhile back Scott and Andrew identified RFC 7485 is also very helpful to understand what data elements are collected today</div>
<div> Vlad Dinculescu:@MIchele: EWG Report gives us insight into what might be required in the future, where data elements might be moving towards</div>
<div> Vlad Dinculescu:I dont believe so</div>
<div> Vlad Dinculescu:Nope, computer says no</div>
<div> Norm Ritchie:+1 for RFC 7485</div>
<div> Elaine Pruis:was the RDAP advisory reviewed? </div>
<div> Alex Deacon:Agree RFC7485 is a good overview of data currently displayed in WHOIS.</div>
<div> Elaine Pruis:the one in development </div>
<div> Vlad Dinculescu:@Michele: the last bit is to do with the proposed additional contact types that are not currently in the WHOIS such as the Legal Contact. </div>
<div> Elaine Pruis:RYSG recently commented </div>
<div> Vlad Dinculescu:Yes</div>
<div> Elaine Pruis:(sorry I'm not in front of my desk) </div>
<div> Lisa Phifer:EWG report also provides principles regarding why data elements should or should not be collected/displayed or made mandatory/optional, as well as the concept of purpose-based contact data</div>
<div> Elaine Pruis:just asking as it could influence what has to be collected and published such as reseller info</div>
<div> Lisa Phifer:@Elaine do you have a link to it?</div>
<div> Elaine Pruis:no I'm on mobile but will send as soon as I'm in front of my desktop </div>
<div> Kathy Kleiman:Quick note: that on the EWG, STephanie (author of Canadian Data Protection Law) has noted that the EWG did not go through the legal analysis under EU/Canadian law re: the collection of data elements</div>
<div> Lisa Phifer:SAC54 certainly triggered several emails on the data list</div>
<div> Alex Deacon:I don't think so - mostly we were in data collection mode.</div>
<div> Kathy Kleiman:That might be a controversial concept, Michele :-)</div>
<div> Lisa Phifer:@Kathy, it is correct that the EWG did not analyze any specific laws but rather stuck to principles - including a principle of compliance with laws</div>
<div> Norm Ritchie:Is "Whowas" data captured in any reports?</div>
<div> Norm Ritchie:yes</div>
<div> Stephanie Perrin:When and how???? I remember being shocked to hear about it?</div>
<div> Kathy Kleiman:@Lisa: there is dissent on this one. I defer to Stephanie</div>
<div> Sara Bockey:Apologies for being late</div>
<div> Berry Cobb:WHOWAS was briefly touched on in the WHOIS Survey WG, which was a survey built more on the technical requirements of a WHOIS system.</div>
<div> Berry Cobb:<a href="http://gnso.icann.org/en/group-activities/inactive/2013/whois-requirements">http://gnso.icann.org/en/group-activities/inactive/2013/whois-requirements</a></div>
<div> Lisa Phifer:@Norm Page 29 of EWG report lists purposes for which WhoWas is important</div>
<div> Norm Ritchie:cool .. thakns Lisa</div>
<div> Berry Cobb:The survey results were submitted to the Council, but no subsequent work was spawn from that effort.</div>
<div> Stephanie Perrin:But it is a value added service produced by a third party, no?\</div>
<div> Norm Ritchie:currnetly whowas is offered by some 3rd parties ... but no one was a complete view of whowas</div>
<div> ELAINE PRUIS:RDAP link <a href="https://whois.icann.org/sites/default/files/files/gtld-rdap-operational-profile-draft-03dec15-en.pdf">https://whois.icann.org/sites/default/files/files/gtld-rdap-operational-profile-draft-03dec15-en.pdf</a></div>
<div> Stephanie Perrin:Thanks Norm....that was what I did recall. </div>
<div> Lisa Phifer:@Elaine, thanks - will add to wiki and data team list</div>
<div> Jody Kolker:Verisign did offer the whowas service, but it was discontinued.</div>
<div> Jody Kolker:but it did not contain contact information.</div>
<div> Alex Deacon:One could describe "whowas" as an industry innovation to fill a market need. </div>
<div> Norm Ritchie:+1 Alex</div>
<div> Alex Deacon:a great example of permissionless innovation :)</div>
<div> Lisa Phifer:@Berry - I can add requirements survey to wiki for completeness</div>
<div> Stephanie Perrin:Yes but the person who complained had to pay 10 per year to get his cellphone out.....now he uses a proxy, but cannot get the old record out</div>
<div> Alex Deacon:I'm not sure WHOWAS is relevant to the data subgroup. May be more relevant to another subteam. </div>
<div> Alex Deacon:agree</div>
<div> Norm Ritchie:Whowas should be discussed in all WGs</div>
<div> Norm Ritchie:likely should be defined first thoigh</div>
<div> Stephanie Perrin:Indeed. </div>
<div> Fabricio Vayra:FWIW: Article 29 WP 76 Opinion 2/2003 seems to say that the processing of personal data in reverse directories or multi-criteria searching services with unambiguous and informed consent by the individual is fair and lawful</div>
<div> Fabricio Vayra:goes to WHOWAS</div>
<div> Nathalie Coupet:There is no consensus on data collection</div>
<div> Kathy Kleiman:@Fabricio: there are other opinions of the Article 29 WP that indicate otherwise...</div>
<div> Stephanie Perrin:THe catch is the unambiguous consent....it has never existed.</div>
<div> Nathalie Coupet:Consent is utopic worlwide</div>
<div> Lisa Phifer:re WhoWas, covered in EWG report recs 49, 50, 166, including definition of WhoWas</div>
<div> Nathalie Coupet:Humans always trade privacy for immediate gains</div>
<div> Fabricio Vayra:@ Kathy, Do you mean like this one: Article 29 WP 33 Opinion 5/2000 "Specific and informed consent of the subscriber must be obtained prior to the inclusion of his personal data into all kinds of public directories (traditional telephony,
mobile telephony, electronic mail, electronic signatures etc.) used for reverse or multi-criteria searches." Implying that once consent is received it's ok.</div>
<div> Nick Shorey - UK Gov:on this point: What data? What users? What privacy? - would be my suggestion for order of approach</div>
<div> Nick Shorey - UK Gov:To Chuck's comment</div>
<div> Luc Seufer:What about the rectification and erasure rights?</div>
<div> Luc Seufer:It's tied to the consent IMHO.</div>
<div> Sana Ali:@Nick I disagree, what privacy doesn't make sense. What purpose should be first because it leads the discussion about the rest of the questions </div>
<div> Lisa Phifer:@Nick - the charter recommends agreeing upon purposes and users before data so that data needs can be put into context</div>
<div> Sana Ali:+1 Lisa</div>
<div> Vlad Dinculescu:@Stephanie: +1</div>
<div> Sana Ali:+1 To stephanie's point</div>
<div> Jim Galvin (Afilias):+1 to stephanie's point</div>
<div> Chris Pelling:+1 to Stephanie </div>
<div> Kathy Kleiman:@Lisa: we agreed that the order is noit key</div>
<div> Stephanie Perrin:Purpose of the RDS collection use and disclosure comes first</div>
<div> Kathy Kleiman:Not a single drafter of the Charter in Marrakech thought that we (WG) would not rethink and reevaluate the order</div>
<div> Lisa Phifer:This is really a venn diagram - a large set of possible data, a subset of data for each user/purpose, and a subset of that as permitted by laws in each applicable jurisdiction. (not a perfect description, but the point is that all are inter-related)</div>
<div> Sana Ali:subject to purpose</div>
<div> Nathalie Coupet:Striking a balance between privacy and security. </div>
<div> Sana Ali:yes</div>
<div> Kathy Kleiman:(at least the ones I talked with)</div>
<div> Jim Galvin (Afilias):I'm not supporting privacy first, per se, but I do think it is integral to all steps. What I think is first is the "purpose of the data".</div>
<div> Jennifer Gore:i agree</div>
<div> Nathalie Coupet:Privacy AND security</div>
<div> Alex Deacon:I think the reality of this disucsison is that these three topics are intertwined and interrelated. </div>
<div> Sana Ali:+1 Agree Purpose absolutely have to be first. Let's not equate purpose with privacy </div>
<div> Fabricio Vayra:According to Article 29 WP 76 Opinion 2/2003 "essential to determine in very clear terms what is the purpose of the Whois and which purpose(s) can be considered as legitimate and compatible to the original purpose" -- original [purpose
was defined in the green and white papers that establishe WHOIS / ICANN.</div>
<div> Daniel K. Nanghaka:I think the data must seek purpose before it is served </div>
<div> Jennifer Gore:yes </div>
<div> Vlad Dinculescu:yes</div>
<div> Jennifer Gore:that seems reasonable</div>
<div> Daniel K. Nanghaka:@Sana, Purpose cannot be equated with Privacy </div>
<div> ELAINE PRUIS:yes</div>
<div> Amr Elsadr:Hmmm...., not sure I'll be able to finish everything on IRD by Friday, but will try.</div>
<div> Sana Ali:@Daniel, thats what I'm saying, but it seems to keep happening in the discussion.</div>
<div> Jim Galvin (Afilias):@amr - there were two IRD working groups. I co-chaired the first. the second was an expert working group and I chaired that group. What do you need with respect to the two groups?</div>
<div> Farell FOLLY:hello all.. </div>
<div> Lisa Phifer:Silence?</div>
<div> Chris Pelling:cross line ?</div>
<div> Luc Seufer:let them give their pin code!</div>
<div> Farell FOLLY:i was in since the beginning, but I decicde not to intervene before the time slot for my sub group come</div>
<div> Amr Elsadr:@Jim: I'm thinking to summarize the final reports of those two groups as part of the "data" sub-team, along with the translation/transliteration PDP. Any insight you can offer would be great. I'll get in touch with you offline, if that's OK.</div>
<div> Jim Galvin (Afilias):@amr - that would be great.</div>
<div> Amr Elsadr:Just thinking that IRD is something that should be considered as part of "data elements".</div>
<div> Jim Galvin (Afilias):@amr - IRD does affect the quality of the data that is collected. I think that is pretty straightforward.</div>
<div> Lisa Phifer:@Amr, is that GNSO PDP on Translation/Transliteration of Contact Information and Final Report (2015)</div>
<div> Amr Elsadr:@Lisa: Yes. That one is rather straight forward. The other two may need some more work on my part. :)</div>
<div> Amr Elsadr:@Jim: Certainly agree.</div>
<div> Jim Galvin (Afilias):Two other principles I think that matter are what is required in the presence of translation and transliteration and what is required to support an appropriate user experience.</div>
<div> Luc Seufer:Iron Mountain for their RDE did</div>
<div> Jim Galvin (Afilias):That's where things get interesting because there are a few different opinions about requirements versus options.</div>
<div> Amr Elsadr:@Jim: User experience is one of the things I'm thinking about, if by user you mean registrant. Have heard from registrars in my region that they are eager to provide end-to-end services in Arabic to their clients.</div>
<div> Amr Elsadr:@Jim: and on what's requred re: translation/transliteration, the standing policy is that it isn't mandatory, but I don't need to tell you that. ;-)</div>
<div> Jim Galvin (Afilias):@amr - I carefully worded my comment to say, "when T&T is present, what is required?" Issues include tagging (language and script), noting which is authoritative, keeping related elements in sync, and other logging considerations.
:-)</div>
<div> Amr Elsadr::)</div>
<div> Marika Konings:David, you may be on mute</div>
<div> Nick Shorey - UK Gov:Interesting point Susan</div>
<div> Nathalie Coupet:No sound</div>
<div> Greg Shatan:Street address is not per se required -- just a mailing address.</div>
<div> Alex Deacon:So - is facebooks HG mailing address personal or sensitive data?</div>
<div> Alex Deacon:HQ </div>
<div> Susan Kawaguchi:@Alex neither in my opinion it is publicly available </div>
<div> Daniel K. Nanghaka:Street Address are attached to users location which I could term as Sensitive Data </div>
<div> Susan Kawaguchi:As Kathy describes it we may have 3 categories personal, sensitive and commercial data. </div>
<div> Susan Kawaguchi:I just want to be sure that we do not convey to commercial entities protection that they do not have a legal right to </div>
<div> Kathy Kleiman:+1 Daniel</div>
<div> Lisa Phifer:@Susan, do we have documents included in our inventory that detail data protection laws that apply to commercial entitites?</div>
<div> Alex Deacon:@susan - agreed there will be multiple catagories. </div>
<div> Luc Seufer:The EU Data Protection Regulation is actually the most important IMHO.</div>
<div> Daniel K. Nanghaka:I agree with Kathy the categorisation of the Data </div>
<div> Kathy Kleiman:@Susan, every 501(c)(3) non-profit entity in the US is a corporation - required by law</div>
<div> Susan Kawaguchi:@ Lisa not sure have not done that review </div>
<div> Kathy Kleiman:and some deal with the most sensitive data of all </div>
<div> Susan Kawaguchi:but every corporation in the US is not a 501(c) 3 so that could be an easy distinction to start with </div>
<div> Daniel K. Nanghaka:Data such as Phone Contacts, addresses whethere email or not is sensitive data </div>
<div> Greg Shatan:Not every 501(c)(3) has "sensitive information". Indeed, the vast majority do not, and should be considered no different than any other corporation. Which, in most cases, they are under relevant law.</div>
<div> Kiran:Hi Kathy, many 501(c)(3)s do deal with highly sensitive topics, but they have to have contactable information displayed ad registered by law. Why would that same data be inappropriate to display in an RDS system? </div>
<div> Kiran:Also agree with Susan that the distinction is easily made</div>
<div> Lisa Phifer:@Susan, @Kathy - could be useful to include WHOIS Reg ID study findings which differentiated between type of entity (eg corp, individual) and presence of potentially commercial activities associated with domain</div>
<div> Susan Kawaguchi:I agree Lisa please add to the list </div>
<div> Kathy Kleiman:@Lisa: and found that banks used privacy/proxy extensively</div>
<div> Kathy Kleiman:I see no reason to include this study</div>
<div> Kiran Malancharuvil:I think it's very important to include the study. If you want to make the point, it must be examined</div>
<div> Daniel K. Nanghaka:Banks use privacy proxy because of the sensitive data that they are using like transacations details and this data cannot be made open </div>
<div> Fabricio Vayra:According to Article 29 WP 76 Opinion 2/2003 "registration of domain names by individuals raises different legal considerations than that of companies or other legal persons registering domain names" ... "the publication of certain information
about the company or organisation (such as their identification and their physical address) is often a requirement by law in the framework of the commercial or professional activities they perform" </div>
<div> Farell FOLLY:I agree that the study should be included in our review</div>
<div> steve metalitz:@Kathy, a 501 c 3 organization need not be a corporation but it cannot be an individual. <a href="https://www.irs.gov/Charities-&-Non-Profits/Charitable-Organizations/Organizational-Test-Internal-Revenue-Code-Section-501(c)(3)">https://www.irs.gov/Charities-&-Non-Profits/Charitable-Organizations/Organizational-Test-Internal-Revenue-Code-Section-501(c)(3)</a></div>
<div> Susan Kawaguchi:None of my banks use PP I wont do business with them but i also require they registry lock their domain names </div>
<div> Fabricio Vayra:+1 Steve</div>
<div> Kiran Malancharuvil:Also, frankly, just because banks may use p/p because it's permissible for them to do so doesn't mean that is a good idea. We should examine the issue as a whole, it would impact all equally. </div>
<div> Luc Seufer:Sorry to be late to the party but have you looked at the GDPR? 2017 is just around the corner. </div>
<div> Daniel K. Nanghaka:I think there must be nuetral data handler such that incase there is a request of data about the individual, the individual must give consent to the data handler to grant access to the requester </div>
<div> Michele Neylon:Irish banks all use .ie domain names so the entire question is moot :)</div>
<div> Greg Shatan:Under the Data Protection Act, Sensitive Personal Data does not incliude phone contacts and addresses. It does include:(a) the racial or ethnic origin of the data subject,(b) his political opinions,(c ) his religious beliefs or other beliefs
of a similar nature,(d) whether he is a member of a trade union (within the meaning of the Trade Union and Labour Relations (Consolidation) Act 1992),(e) his physical or mental health or condition,(f) his sexual life,(g) the commission or alleged commission
by him of any offence, or(h) any proceedings for any offence committed or alleged to have been committed by him, the disposal of such proceedings or the sentence of any court in such proceedings."</div>
<div> Susan Kawaguchi:@ Daniel That doesn't work well in acquisitions, MA and other transactions </div>
<div> Fabricio Vayra:+1 Greg</div>
<div> steve metalitz:@Luc, impact of GDPR on opinions under 1995 directive has bene raised on list. When we get to question (iv) this may be addressed. </div>
<div> Nick Shorey - UK Gov:let's be careful on this 'banks use pp' statement</div>
<div> Luc Seufer:thanks Steve</div>
<div> Daniel K. Nanghaka:@Susan, Yes, it also has restrictions </div>
<div> Grace Mutung'u:I did the African Union Convention on Cybersecurity...it is still a work in progress as it is not yet in effect but iit is worth considering as it is an authority</div>
<div> Kiran Malancharuvil:It's an ongoing debate whether it would be within ICANNs remit. The issue needs to be examined. </div>
<div> Kathy Kleiman:@Susan: Mergers & Acquisitions are the essence of corporate data that is kept private - so that there is expressly not disclosure prior to full market knowledge per SEC mandate</div>
<div> Amr Elsadr:@Grace: Is the AUC on cybersecurity an authority?</div>
<div> Grace Mutung'u:@Amr, it is, or will be once it is in effect</div>
<div> Fabricio Vayra:Article 29 WP 217 Opinion 4/2014 says that "personal data shall only be processed (a) based on the data subject's unambiguous consent; or if -briefly put -" ... "(c) compliance with a legal obligation imposed on the controller" and
government regulation would fall under this.</div>
<div> Daniel K. Nanghaka:The AUC on Cybersecurity is still a work in progress </div>
<div> Stephanie Perrin:Could the record please delete my apologies for not making it to this meeting, since I made it after all?</div>
<div> Marika Konings:@Stephanie - done</div>
<div> Stephanie Perrin:thanks!</div>
<div> Amr Elsadr:@Grace: My understanding is (and I may be wrong) is that local legislation is required as a follow-up to the convention, because it isn't actally authoritative as far as member states are concerned.</div>
<div> Grace Mutung'u:depends on the country...For example, in Kenya you can depend on conventions in court even before ratification </div>
<div> Farell FOLLY:Grace; I was unable to download this convention document form the link provided, can you share it with me again ?</div>
<div> Fabricio Vayra:@Kathy, is that an opinion or fact?</div>
<div> Fabricio Vayra:I'd hate to base our work on speculation</div>
<div> Lisa Phifer:@Kathy we haven't received a request from Peter Kimpian to join subteam, we will follow up</div>
<div> Amr Elsadr:@Farell: Is this what you're looking for? <a href="http://au.int/en/cyberlegislation">http://au.int/en/cyberlegislation</a></div>
<div> Grace Mutung'u:@ Farell, here you go <a href="http://pages.au.int/sites/default/files/en_AU%20Convention%20on%20CyberSecurity%20Pers%20Data%20Protec%20AUCyC%20adopted%20Malabo.pdf">http://pages.au.int/sites/default/files/en_AU%20Convention%20on%20CyberSecurity%20Pers%20Data%20Protec%20AUCyC%20adopted%20Malabo.pdf</a></div>
<div> Lisa Phifer:Stephanie's statement is indeed in the privacy team's list, summarized by Nathalie Coupet</div>
<div> Farell FOLLY:yes thank you both Amr and Grace</div>
<div> Greg Shatan:That's not what McIntyre says. It dealt only with an election law, and did not cover speech generally, except in dictum (the musings of the court). As such, it has no legal effect outside the issue of election pamphlets.</div>
<div> Fabricio Vayra:@Stephanie, or wait for the report comes out and not speculate on the outcome</div>
<div> Amr Elsadr:@Grace: Thanks. The link I found isn't working. :)</div>
<div> Luc Seufer:They are rebranding to European Data Protection Board</div>
<div> Kathy Kleiman:@Lisa: it belongs with the EWG Report. Per ICANN's transparency, Final Reports are always issued with their dissents; final decisions of the ICANN are similarly always listed with the dissent. Tx Lisa for including in the bullet lists!</div>
<div> Greg Shatan:Of course, one can use McIntyre to advocate for broader things. But that's advocacy, not a statement of the case's holding.</div>
<div> Stephanie Perrin:no sounds???</div>
<div> Kathy Kleiman:@Lisa: shall I have Peter Kimpian write to you directly to join this subgroup? He keeps trying...</div>
<div> Lisa Phifer:@Kathy, I have asked GNSO sec to reach out to Peter</div>
<div> Luc Seufer:They will starting 2017</div>
<div> Stephanie Perrin:They are a group of data protection authorities. Each one has its own powers of enforcement.</div>
<div> Fabricio Vayra:Great point, Steve.</div>
<div> Sana Ali:+1 Kathy on including the Article 29 opinions</div>
<div> Amr Elsadr:@Kathy: +1</div>
<div> Luc Seufer:Agreed</div>
<div> Chris Pelling:+1 to Kathy </div>
<div> steve metalitz:The material (opinions, working documents, letters etc.) issued by the Article 29 Working Party (Art. 29 WP), available on this website reflect the views only of the Art. 29 WP which has an advisory status and acts independently. (Art.
29 WP website)</div>
<div> Kathy Kleiman:@Lisa: Could you kindly put EWG Dissent in brackets next to EWG Recommendations. That will keep the point and allow us to continue the discussions!</div>
<div> Kathy Kleiman:Tx All for the discussion!</div>
<div> Greg Shatan:Maybe there's been no enforcement actions in this area because there's been no violations. That seems at least as valid a conclusion.</div>
<div> Fabricio Vayra:To be clear, is one of these documents the March 12, 2007 letter to Vint that says "The Article 29 WP therefore recommends to modify the proposal in such a way that at least for private domain holders that use domains solely in a non-commercial
context the name of the domain holder should only be published in the WHOIS service with the explicit, freely given consent of the data subject"?</div>
<div> Lisa Phifer:RegID report was tasked to answer GAC questions identified as important to understanding WHOIS data actually supplied by registrants of various types, engaged in various kinds of activities</div>
<div> Fabricio Vayra:Thanks, David!</div>
<div> Marika Konings:In red, input that was received on the mailing list following the circulation of the template. </div>
<div> Sana Ali:sorry!</div>
<div> Stephanie Perrin:yes</div>
<div> Fabricio Vayra:I think yes</div>
<div> Susan Prosser:yes.</div>
<div> Chuck Gomes:Kathy has her hand up</div>
<div> Fabricio Vayra:I think the Green and White papers should be added.</div>
<div> Kiran Malancharuvil:Agree Fab</div>
<div> Greg Shatan:+1 Fab</div>
<div> Susan Prosser:Also agree with Fab on the other docs </div>
<div> Lisa Phifer:please recap that list</div>
<div> Kathy Kleiman:I think we need to do a summary first</div>
<div> Fabricio Vayra:Summaries were already submitted for Green and White papers</div>
<div> Stephanie Perrin:How about the art 29 opinion on purpose limitation 3/2013.....could be a typo, the Opinion on whois is 2/2003</div>
<div> Greg Shatan:The docs named by Kathy are really privacy and data protection documents and should be (and are) dealt with under that list.</div>
<div> Kiran Malancharuvil:I also think some of the international laws that have been identified with relation to consumer protection and transparency of contact information is relevant to purpose. </div>
<div> Stephanie Perrin:They are purpose docs</div>
<div> Greg Shatan:Disagree.</div>
<div> Fabricio Vayra:@Kathy, I already submitted the summaries and both have extensive terms to purpose</div>
<div> Stephanie Perrin:please note the typos in the doc being displayed. </div>
<div> Kiran Malancharuvil:Summary was completed by Fab already</div>
<div> Lisa Phifer:STephanie which document please</div>
<div> Greg Shatan:They already exist, Susan....</div>
<div> Stephanie Perrin:Art 29 2/2003 on WHois, art 29 3/2013 on purpose</div>
<div> Kathy Kleiman:@Fabricio - sorry to miss that!@</div>
<div> Stephanie Perrin:Coming soon....</div>
<div> Fabricio Vayra:@Kathy. No worries. To make it easier to find in the emails, summaries sent Mon 4/11/2016 12:08 PM</div>
<div> Kathy Kleiman:@Fabricio - I'll read closely!</div>
<div> Klaus Stoll:I have a lot of cut outs in audio, is it just me?</div>
<div> Nathalie Coupet:Could I have more time to find other sources? I'm sure there are many more. </div>
<div> Nathalie Coupet:Yes</div>
<div> Nathalie Coupet:Sure. </div>
<div> Chuck Gomes:Keep in mind that we can always add info sources as we proceed with our work.</div>
<div> Greg Aaron:+1 on what Stephanie just said</div>
<div> Kiran Malancharuvil:I can't hear the speaker</div>
<div> Kathy Kleiman:@Susan: the ones being listed are directly related to Purpose (Article 29 WP)</div>
<div> Fabricio Vayra:+1 Susan P</div>
<div> Daniel K. Nanghaka:please dial me </div>
<div> Daniel K. Nanghaka:Could you please dial me - I got a call dropped </div>
<div> Kathy Kleiman:Needs to be considered....</div>
<div> Maryan Rizinski:Susan, all, I will miss the rest of the meeting because of a family engagement for which I apologize. I will listen to the recording later this evening. Thank you and have a great day!</div>
<div> Kathy Kleiman:Comments are good!</div>
<div> Kathy Kleiman:@Lisa: are we still missing some summaries??</div>
<div> Stephanie Perrin:Lisa good point. Sadly I have not had time to look at everything yet.</div>
<div> Daniel K. Nanghaka:Please dial me - I have network issues </div>
<div> Kathy Kleiman:How can we get those?</div>
<div> Nathalie Coupet:Is the psychology of the end-user taken into account at this tage in order to appreciate wether the purposes considered will actually meet their goals?</div>
<div> Daniel K. Nanghaka:+256772898298</div>
<div> Kiran Malancharuvil:Mine are missing, sorry. Getting to the group today. </div>
<div> Kathy Kleiman:Tx Lisa!</div>
<div> Marika Konings:For the latest versions of the check lists and summaries, please see <a href="https://community.icann.org/x/p4xlAw">https://community.icann.org/x/p4xlAw</a>. </div>
<div> Kathy Kleiman:Tx Kiran!</div>
<div> Sana Ali:Thanks for that link Marika</div>
<div> Kiran Malancharuvil:Thanks for your patience!</div>
<div> Amr Elsadr:@Marika: Thnx.</div>
<div> Sana Ali:@Nathalie, by psychology do we mean end user expectations or something else?</div>
<div> Nathalie Coupet:I can do it</div>
<div> Nathalie Coupet:@Sana: yes</div>
<div> Nathalie Coupet:Yes for expectations, fears reactions, etc. </div>
<div> Lisa Phifer:Nathalie, you may wish to refer to the Individual Internet User purpose as outlined in the EWG report, and to Carlton Samuels' blog</div>
<div> Sana Ali:Thanks for the clarification, Nathalie, are there examples of documents we could turn to for this kind of informaton? If you have suggestions I'd be happy ot look into it as I certainly think it is an important element to br considered. </div>
<div> Sana Ali:*be</div>
<div> Kathy Kleiman:I like that phrase -- Embarrassment of riches!</div>
<div> Nathalie Coupet:@Lisa: Where can I find Carlton Samuels' blog?</div>
<div> Lisa Phifer:Refer to the Purpose team's consolidated summaries, page 41, and linked blog</div>
<div> Nathalie Coupet:@Lisa: Tx!</div>
<div> Kiran Malancharuvil:Slightly burned out and I even joined late! :) </div>
<div> Kiran Malancharuvil:Agree with Stephanie</div>
<div> Kiran Malancharuvil:Can we continue on the list? </div>
<div> Chris Pelling:we could rotate each section on each call</div>
<div> Kathy Kleiman:Chuck - sorry, where is your question? Is it in writing?</div>
<div> Chris Pelling:giving a fair chance for each section</div>
<div> Stephanie Perrin:no stamina, compared to the CCWG</div>
<div> Fabricio Vayra:Thanks, Chuck!</div>
<div> Fabricio Vayra:Thanks, Susan</div>
<div> Ayden Férdeline:Thanks to all</div>
<div> Kathy Kleiman:Tx Susan, Chuck, All!</div>
<div> Luc Seufer:Merci à tous !</div>
<div> Susan Prosser:thanks all</div>
<div> Amr Elsadr:Thanks all. Bye.</div>
<div> Vlad Dinculescu:Thanks All.</div>
<div> Greg Shatan:By all!</div>
<div> Susan Kawaguchi:Thanks all! </div>
<div> Jim Galvin (Afilias):thanks all bye</div>
<div> Chris Pelling:thanks all</div>
<div> Sana Ali:Bye everyone!</div>
<div><br>
</div>
</div>
</div>
</div>
</body>
</html>