<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</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, 14 June 2016 at 16:00 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> Mp3:</b> </font><a href="http://audio.icann.org/gnso/gnso-nextgen-rds-14jun16-en.mp3
" style="font-size: 14px;">http://audio.icann.org/gnso/gnso-nextgen-rds-14jun16-en.mp3
<br>
</a><a href="http://audio.icann.org/gnso/gnso-nextgen-rds-24may16-en.mp3" style="font-size: 14px;"> </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: </span><a href="https://community.icann.org/x/ix2OAw" style="font-family: -webkit-standard; font-size: 14px;">https://community.icann.org/x/ix2OAw</a></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, 14 June 2016</span></b></p>
<div> Michelle DeSmyter:Dear All, Welcome to the GNSO Next-Gen RDS Working Group call on Tuesday, 14 June 2016 at 16:00 UTC. </div>
<div> Michelle DeSmyter:Agenda page: <a href="https://community.icann.org/x/ix2OAw">https://community.icann.org/x/ix2OAw</a></div>
<div> Michelle DeSmyter:Member page/SOI: <a href="https://community.icann.org/x/I4xlAw">https://community.icann.org/x/I4xlAw</a></div>
<div> Chuck Gomes:Welcome all.</div>
<div> Farell FOLLY:hi chuck !</div>
<div> Ayden Férdeline:Hello everyone</div>
<div> Chuck Gomes:Let's wait one more minute before starting the recording.</div>
<div> Marika Konings:No, nothing from me</div>
<div> Lisa Phifer:no</div>
<div> Lisa Phifer:fyi, all responses will be posted here:</div>
<div> Lisa Phifer:SO/AC/SG/C Input Page: <a href="https://community.icann.org/x/pYxlAw">https://community.icann.org/x/pYxlAw</a></div>
<div> Alan Greenberg:ALAC has submitted a statement</div>
<div> Richard Padilla:Hi all</div>
<div> Marika Konings:@Alan - can you confirm where the statement has been submitted?</div>
<div> Marika Konings:I don't recall seeing it. </div>
<div> Alan Greenberg:Will check. </div>
<div> Marika Konings:thanks</div>
<div> Alan Greenberg:Submitted to GNSO Secretariat on 10 June</div>
<div> Lisa Phifer:Cross-Community Session Abstract <a href="http://sched.co/7NCc">http://sched.co/7NCc</a></div>
<div> Alan Greenberg:By Ariel</div>
<div> Marika Konings:ah, Glen is on vacation so she may not have forwarded it yet. I'll check in with Ariel to see if she can forward it to me as well. </div>
<div> steve metalitz:So we have completed our initial requirements list? Everything I have seen has been marked "draft." </div>
<div> Lisa Phifer:initial, yes</div>
<div> Lisa Phifer:the work plan item was just to get a first cut out for outreach message #2</div>
<div> Vicky Sheckler:agree w metalitz re we shouldn't be foreclosing potential reuiements</div>
<div> Lisa Phifer:All, the draft slide deck will be posted with the meeting minutes</div>
<div> Lisa Phifer:The possible reuqirements list is a living document. It states that additions are expected on an on-going basis</div>
<div> Ayden Férdeline:hmmm.... would these cards really be useful? this isn't a referendum... :)</div>
<div> Vicky Sheckler:lisa - thx for the clarification</div>
<div> steve metalitz:What will be the significance of the "vote" you propose to take at the cross-community meeting? </div>
<div> Marika Konings:it could be used to take the temperature of the room, if deemed appropriate as part of the discussion. It is not intended to be anything more than that. </div>
<div> David Cake:I believe vote is intended only to gauge mood/opinion. </div>
<div> Scott Hollenbeck (Verisign):@Lisa, the document containing possible requirements is 110 pages long. Will someone attempt to remove duplication before the public sees the document?</div>
<div> David Cake:Not a vote, just a very informal poll. </div>
<div> Lisa Phifer:@Scott, no, but we will discuss this in the next agenda item</div>
<div> Alan Greenberg:My hand is up...</div>
<div> steve metalitz:Not sure how useful it is to gauge mood/opinion of whoever happens to show up in Helsinki for cross-community meeting. But accept it as a possible means to keep people awake/engaged...... </div>
<div> Kathy Kleiman:awake is always good</div>
<div> Vicky Sheckler:agree w/ ayden & metalitz</div>
<div> Sana Ali:vote will surely include remote participants, as well, steve</div>
<div> Greg Shatan:I thought it wasn't a vote.</div>
<div> Ayden Férdeline:I'm with Steve here, I'm afraid. That a number of special interest groups may be able to make it to Helsinki to participate in the conversation doesn't mean we necessarily need an RDS.</div>
<div> Marika Konings:@Sana - yes, adobe allows for agree / disagree (but again, it wouldn't be a vote)</div>
<div> Sana Ali:yes, okay *poll</div>
<div> Lisa Phifer:@Steve et al, it is intended to help the community understand that this WG must try to answer that question in its Phase 1 report</div>
<div> Ayden Férdeline:I am sure some will not like my usage of the term, “special interest group”, maybe there is a better word to describe those who find the RDS useful.</div>
<div> Kathy Kleiman:Can we control the slides?</div>
<div> Lisa Phifer:While it is too early to answer the question based on requirements, it helps attendees understand that's the reason we are looking at possible requirements</div>
<div> Greg Shatan:@Ayden, every group represented here is a special interest group. </div>
<div> Greg Shatan:Including yours.</div>
<div> Lisa Phifer:@Kathy, I ithink Chuck wants to address what's on these two slides first</div>
<div> Holly Raiche:Maybe have a slide either with the EWG list of data involved or SAC054 - the list of information required at each stage</div>
<div> Ayden Férdeline:@Greg: That is one perspective. I see a special interest group as any entity which is seeking to use inordinate socioeconomic power to twist the RDS so to serve their own interests. </div>
<div> Carlton Samuels:Howdy all. Apologies. Unscheduled task for work</div>
<div> Ayden Férdeline:@Greg: But, it is fair to say this definition can be applied to many different stakeholder groups.</div>
<div> Lisa Phifer:@Holly we could display an existing WHOIS record</div>
<div> Kathy Kleiman:@Lisa: it's always a good idea to display an existing Whois record! It always surprises people...</div>
<div> Lisa Phifer:In Marrkech we ran this on the screen before the meeting start to help set context for those unfamiliar with WHOIS</div>
<div> Holly Raiche:@ Lisa - the issue isall the information - not just the traditional notion of Whois aswhat is required to be publicly available under the RAA</div>
<div> Carlton Samuels:@Lisa....Holly just answered</div>
<div> Carlton Samuels:I think it is important to show and distinguish the existing WHOIS dataset from the corpus of data collected in the registration transaction</div>
<div> Lisa Phifer:@Holly, could use that approach and add a slide with a few examples from 054 to show what other data is collected by some</div>
<div> Holly Raiche:Agree with Kathy's suggestion</div>
<div> Holly Raiche:@ Lisa - even just the tables inSAC054 - to show the range of information required at each phase of registration</div>
<div> Carlton Samuels:Then a followup slide might show the data elements that are of hightened importance - the PIIs</div>
<div> Holly Raiche:Glad to see documents beyond the RAA</div>
<div> Holly Raiche:Agree with Carlton's suggestion as well</div>
<div> Lisa Phifer:@Holly, Carlton, Kathy - staff can take a crack at expanding the rolling display used in Marrakech to add 054 examples and highligh some of the PII if you like</div>
<div> Holly Raiche:ThanksLisa - that would be great</div>
<div> Carlton Samuels:@Lisa Perfect! I know you will get that done in ways that communicate the message</div>
<div> Carlton Samuels:@JIm would be perfect spokesperson</div>
<div> Lisa Phifer:@Jim, hopefully WG volunteers will suggest possible requirements not listed on this slide - could you do that?</div>
<div> Greg Shatan:@Ayden, thank you for clarifying that you are using "special interest group" as a pejorative and stereotyped phrase. That's helpful in understanding your viewpoint.</div>
<div> Lisa Phifer:hmm, don't know where sterotyped came from - autocorrect....</div>
<div> Lisa Phifer:@Greg, never mind - I thought that was in my last chat</div>
<div> Jim Galvin (Afilias):@NOTES - Jim is volunteering to speak with respecting to any examples we choose from SSAC documents, not just SAC054.</div>
<div> Marika Konings:@Jim - updated. Thanks :-)</div>
<div> Lisa Phifer:@Lisa - to clarify, I was suggesting that we display a series of slides BEFORE the session starts, illustrating what's in a WHOIS record, plus a little bit of SAC054 to show additions that some entities collect, to set context - but that
would not be presented</div>
<div> Benny Samuelsen / Nordreg AB:About the Validation part, news was coming todaiy about a new naming system Mongolia are going to put in place</div>
<div> Benny Samuelsen / Nordreg AB:<a href="http://qz.com/705273/mongolia-is-changing-all-its-addresses-to-three-word-phrases/">http://qz.com/705273/mongolia-is-changing-all-its-addresses-to-three-word-phrases/</a></div>
<div> Carlton Samuels:@Chuck: I strongly suggest that we first address the policy question at the broad level BEFORE we go to asking what should be collected, validated and disclosed.</div>
<div> Benny Samuelsen / Nordreg AB:According to the rumours I have heard this will be rolled out in Africa too</div>
<div> Benny Samuelsen / Nordreg AB:Will this affect our work here? Or can we safely ignore this for now?</div>
<div> Holly Raiche:@ Carlton - maybe we work though my one slide?</div>
<div> Holly Raiche:I like Lisa'ssuggestion</div>
<div> Holly Raiche:@Lisa - have the information up even before the session would be really helpful</div>
<div> Greg Shatan:This is all part of the Meeting B "Policy Forum" experiment....</div>
<div> Lisa Phifer:@Holly, we can take a pass at this and circulate to WG for finalization at next week's WG meeting</div>
<div> Greg Shatan:We have a WG meeting as well in Helsinki.</div>
<div> Greg Shatan:This is more of a "crowdsourcing" meeting....</div>
<div> Lisa Phifer:RDS PDP F2F Session: <a href="http://sched.co/7GqJ">http://sched.co/7GqJ</a></div>
<div> steve metalitz:Possibly another jargon-free way to draw out views from the audience is to ask them what they would like to see changed from or maintained in the current Whois system. </div>
<div> Greg Shatan:Yes, less jargon, more plain English/Finnish.</div>
<div> Carlton Samuels:@Chuck Got you. just that I'm always keen to establish context first.</div>
<div> Holly Raiche:Maybe let's stop using the term Whois - as the SAC suggestion a while ago - and start using RDS</div>
<div> Lisa Phifer:@Steve, it that a reword for the first bullet on this slide?</div>
<div> Holly Raiche:I'll ask for Jim's help</div>
<div> Carlton Samuels:@Holly That would be helpful. And in my view a way to [re]frame their headspace.</div>
<div> steve metalitz:@Lisa, yes, and more balanced because it also asks what they want to see preserved in status quo. </div>
<div> Kathy Kleiman:I'll try Privacy</div>
<div> Carlton Samuels:Would love to volunteer but I won't be in Helsinki...and the timing is bad for me</div>
<div> Carlton Samuels:Ask Michele</div>
<div> Kathy Kleiman:I think we should cover the big 3 - Data Elements, Privacy, Users/Purposes</div>
<div> Carlton Samuels:@Scott - would you volunteer for Gated Access?</div>
<div> Holly Raiche:Agree with volunteering Scott</div>
<div> Carlton Samuels:At least I know you were deep into that aspect in the EWG Subteam</div>
<div> Scott Hollenbeck (Verisign):No</div>
<div> Ayden Férdeline:Please remind me which ones we are looking for volunteers for still?</div>
<div> Carlton Samuels:@Scott Aaaah, pity!</div>
<div> Scott Hollenbeck (Verisign):Sorry ;)</div>
<div> Holly Raiche:We are also sorry</div>
<div> Lisa Phifer:accuracy</div>
<div> Lisa Phifer:<a href="https://community.icann.org/display/gTLDRDS/WG+Charter">https://community.icann.org/display/gTLDRDS/WG+Charter</a></div>
<div> Carlton Samuels:This A/C room kick me out time and again!</div>
<div> Ayden Férdeline:I support the proposal from the Leadership team. Two initial reports</div>
<div> Holly Raiche:Happy with that</div>
<div> Carlton Samuels:@Chuck - How are the Initial Reports connected? DO we have a scope for each already determined?</div>
<div> Lisa Phifer:@Carlton, the first initial report would just address the 5 fundamental questions; the second would address all phase 1 questions</div>
<div> Carlton Samuels:@Lisa - Thanks</div>
<div> Ayden Férdeline:re: 1 b) ii) rather than "supported by most" can we indicate which stakeholder groups have either rejected or accepted something?</div>
<div> Kal Feher:will the WG pause during the comment period for the initial report, or do we continue work in parallel?</div>
<div> steve metalitz:@Lisa, this doc suggests that the first initial report woudl cover 5 charter questions, "General Requirements," and "Fundamental Questions". For those of us who have not committed the charter to memory, could you list these 7 questions? </div>
<div> Sana Ali:Agree with Kathy</div>
<div> Carlton Samuels:@Kathy - +1 Makes perfect sense</div>
<div> Kathy Kleiman:Can you remind us what 4 and 5 are?</div>
<div> Ayden Férdeline:+1 @Kathy </div>
<div> Lisa Phifer:The 5 fundamental questions posed by the board are: user/purpose, gated access, data accuracy data elements and privacy</div>
<div> Holly Raiche:ThanksKathy - not everyone - even on this WG - haveYEARS of experience with the Whois issue</div>
<div> Carlton Samuels:@Chuck This is what I was feeling for in my question on scope!</div>
<div> Vicky Sheckler:should we include accuracy in the initial phase?</div>
<div> Ayden Férdeline:@Vicky: I would suggest otherwise</div>
<div> steve metalitz:Since we were first presented with this document 10 minutes ago it is premature for some of us to express agreement or not. </div>
<div> Holly Raiche:@ Lisa - I think that is part of the privacy issue</div>
<div> Fabricio Vayra:+1 Lisa. We can't make decisions on data in a vacuum. What is or is not gated is an important framework to the question of elements.</div>
<div> Fabricio Vayra:+2 Lisa</div>
<div> Vicky Sheckler:agree w/ lisa</div>
<div> Ayden Férdeline:My feeling is that there should be a general policy of openness about developments, practices, and policies with respect to the collection of data, and for that reason I like the idea of having as many opportunities as possible for public
comment. I think we should be establishing, however, the nature of what (if any) personal data is collected before we go into the specifics of whether it should be accurate or not, or whether there should be gated access.</div>
<div> Lisa Phifer:fyi, draft 3 contains roughly 780 possible requirements, drawn from 46 sources</div>
<div> Vicky Sheckler:apologies. got to run.</div>
<div> Vaibhav Aggarwal:@Ayden this is good - I also feel that if v can develop a short survey for the Genral public on some issues that we all differ, then we can collect some sample data During the Meeting from a LArger group</div>
<div> steve metalitz:isn't there some need to refine/triage list earlier in the process? There is a great deal of duplcication and overlap as well. </div>
<div> Holly Raiche:That wwould be really useful</div>
<div> Carlton Samuels:@Chuck NO I'm not! </div>
<div> Vaibhav Aggarwal:and then v can delebrate</div>
<div> Fabricio Vayra:+1 Steve</div>
<div> steve metalitz:When would this triage occur? Only after the first two initial reports? </div>
<div> Carlton Samuels:Staff is surely competent to do all that</div>
<div> Lisa Phifer:@Steve, that's what Chuck is suggesting we do now, before moving ahead to deliberation</div>
<div> steve metalitz:@Lisa, OK, confusing because it is listed as step 2. </div>
<div> Kathy Kleiman:Yes</div>
<div> Greg Shatan:I am happy for staff to take the first cut.</div>
<div> Holly Raiche:Yes - have staff take a first go</div>
<div> Kathy Kleiman:If staff takes a first crack and tracks the changes (or keeps notes in text), I think that will help a lot</div>
<div> Greg Shatan:Something we can agree on!</div>
<div> Ayden Férdeline:Perhaps staff could group similar requirements together, but not remove any?</div>
<div> Greg Shatan:Steve, I think Item 1 is not really a step -- it's an overview of the entire lifecycle of the process.</div>
<div> Farell FOLLY:I also agree on workin on grouping similar requirements together</div>
<div> steve metalitz:Agree with triage first. Is the doc being triaged the "draft 3" that Lisa sent out on Saturday? </div>
<div> Lisa Phifer:@Kathy, this would be moving possible requirements around but not deleting any of them. The numbering scheme allows for that, to ensure we don't lose anything in the process of organizing the list.</div>
<div> Lisa Phifer:@Steve, I think draft 4</div>
<div> Kathy Kleiman:Lisa, what I was recommending is that a note follow move (e..g, "originally in XYZ")</div>
<div> Lisa Phifer:All of the possible requirements have unique numbers assigned to them, including the source document, so moving them retains that context</div>
<div> Kathy Kleiman:@Lisa, I don't think that's enough. Sorry, but if someone wrote something and thinks it should be in X and you move it to Y, they should be able to find it quickly and recommend that it go back...</div>
<div> Marc Anderson:I have to drop off. thank you everyone.</div>
<div> steve metalitz:. @Lisa, thanks, was draft 4 distributed? </div>
<div> Lisa Phifer:Oh, you mean changing the question it's mapped to? The question is also part of the unique number, so would not be lost.</div>
<div> Lisa Phifer:@Steve, we have asked for additions to draft 3 and some WG members are stil turning in assignments, so I'm suggesting probably all of that goes into draft 4 and then we do that organization in one pass.</div>
<div> Ayden Férdeline:+1 @Kathy</div>
<div> Carlton Samuels:@Chuck I still believe it would be extremely useful for this WG to decide and recommend the baseline policy question: Is there a basis for collecting, validating and curating registration data and should ICANN mandate so in it contracts?</div>
<div> Fabricio Vayra:+1 Greg.</div>
<div> Susan Prosser:+1 agree with Greg</div>
<div> Scott Hollenbeck (Verisign):Sorry, time to go - bye!</div>
<div> Ayden Férdeline:@Carlton - Yes... I tend to agree. It is not too late to change our approach.</div>
<div> steve metalitz:@Lisa, thanks for clarifying status of drafts. For purposes of outreach #2, wouldn't it be more useful to have the "triaged" version of the document and ask our constituent groups to react to that? </div>
<div> Nathalie Coupet:@Greg +1 </div>
<div> Carlton Samuels:@Greg Applying the law to the facts I'm suggesting we lay down the law first!</div>
<div> Lisa Phifer:@Steve, outreach message #2 already went out with draft 3, but no doubt you are right that feedback on the list at various stages will be helpful - and easier for reviewers later</div>
<div> Greg Shatan:Carlton, that's backwards.</div>
<div> Greg Shatan:PII is part of the legal analysis of potential data itemes.</div>
<div> Carlton Samuels:I think we must establish a policy first!</div>
<div> Sara Bockey:thank you all</div>
<div> Greg Shatan:Can't estabilish a policy in a factual vacuum.</div>
<div> Fabricio Vayra:thanks</div>
<div> Vlad Dinculescu:Thanks all</div>
<div> David Cake:Thank you all, good meeting. </div>
<div> Richard Padilla:thanks all</div>
<div> Vaibhav Aggarwal:Thanks Guys</div>
<div> Susan Prosser:thanks all bye</div>
<div> Carlton Samuels:Bye all</div>
<div> Nathalie Coupet:bye</div>
<div><br>
</div>
</div>
</div>
</div>
</body>
</html>