<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="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;">Dear All,<o:p></o:p></span></p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri; color: rgb(31, 73, 125);"> </span><span style="font-size: 11pt; font-family: Calibri;"><o:p></o:p></span></p>
<div style="font-family: -webkit-standard;">
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;">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, 30 May 2017 at 16:00 UTC.<o:p></o:p></span></p>
<p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; line-height: 15.6pt;">
<b><span style="font-size: 11pt; font-family: Calibri;">MP3: </span></b><a href="http://audio.icann.org/gnso/gnso-nextgen-rds-pdp-30may17-en.mp3
" style="font-family: -webkit-standard; font-size: 14px;">http://audio.icann.org/gnso/gnso-nextgen-rds-pdp-30may17-en.mp3</a></p>
<p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; line-height: 15.6pt;">
<b><span style="font-size: 11pt; font-family: Calibri;">AC recording:</span></b><span style="font-size: 11pt; font-family: Calibri;"> <o:p></o:p></span><a href="https://participate.icann.org/p4pshwjvr6e/" style="font-family: -webkit-standard; font-size: 14px;">https://participate.icann.org/p4pshwjvr6e/</a></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;">The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group-2Dactivities_calendar-23nov&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=GJMkY4Fbi9sry9Z53DaSWJm-mHxMfFxg7MEVDf2JU90&s=FI3QJYH6DWWCDQir6NDMSjPkzdqfTTUmf9Ua-AYpc14&e=" style="color: purple;">http://gnso.icann.org/en/group-activities/calendar</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;">** Please let me know if your name has been left off the list **<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;">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>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<b><span style="font-size: 11pt; font-family: Calibri;">Wiki page: </span></b><a href="https://community.icann.org/x/IMPRAw" style="font-family: -webkit-standard; font-size: 14px;">https://community.icann.org/x/IMPRAw</a></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;">Thank you.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;">Kind regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;">Michelle <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;">———————————————<o:p></o:p></span></p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11pt; font-family: Calibri;"> <o:p></o:p></span></p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<b><u><span style="font-size: 11pt; font-family: Calibri;">AC Chat Next-Gen RDS PDP WG Tuesday, 30 May 2017</span></u></b></p>
<div> Michelle DeSmyter:Dear All, Welcome to the Next-Gen RDS PDP Working Group call on Tuesday, 30 May 2017 at 16:00 UTC.</div>
<div> Michelle DeSmyter:Meeting agenda page: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_IMPRAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=gu_xEc0jIs-PVSa5yroc8eEfOjJfVo3EC4pHM_zlePM&s=ufGTX1fqLWMXlb4Z0cB1qHkIpQD-8ArT4lIrL9BJxd8&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_IMPRAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=gu_xEc0jIs-PVSa5yroc8eEfOjJfVo3EC4pHM_zlePM&s=ufGTX1fqLWMXlb4Z0cB1qHkIpQD-8ArT4lIrL9BJxd8&e=</a></div>
<div> Chuck Gomes:Hello all</div>
<div> Lisa Phifer:Document currently displayed: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078622_AnnotatedResults-2DPoll-2Dfrom-2D17MayCall.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=gu_xEc0jIs-PVSa5yroc8eEfOjJfVo3EC4pHM_zlePM&s=x5hsuUZWzQ4oP4DhClgm3vt5pODGKY08o9xRa_CBudc&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078622_AnnotatedResults-2DPoll-2Dfrom-2D17MayCall.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=gu_xEc0jIs-PVSa5yroc8eEfOjJfVo3EC4pHM_zlePM&s=x5hsuUZWzQ4oP4DhClgm3vt5pODGKY08o9xRa_CBudc&e=</a></div>
<div> Lisa Phifer:Q3 starts on page 4</div>
<div> Juan Manuel Rojas:Good morning/afternoon/evening</div>
<div> Rod Rasmussen:In now - looks like I have a bad link that still works for getting "close" to logging into this meeting. Odd</div>
<div> Benny Samuelsen / Nordreg AB:could someone close the Poll 2 window</div>
<div> Benny Samuelsen / Nordreg AB:thanks</div>
<div> Stephanie Perrin:apologies for being late.</div>
<div> Lisa Phifer:If anyone does not support option A) please raise hand</div>
<div> Lisa Phifer:Q3) option a) is A minimum set of "thin data" elements must be accessible by unauthenticated RDS users.</div>
<div> Greg Shatan 2:@Stephanie, Huzzah! Let's set a new Canadian holiday.</div>
<div> Lisa Phifer:Agreement #20 was discussed for the past few weeks, and is: "gTLD registration 'thin data' must be accessible without requestor identification, authentication, or stated purpose."</div>
<div> Lisa Phifer:Charter question on data elements is intended to address what data elements are needed</div>
<div> Lisa Phifer:The EWG defined a "minimum public data set" in its answers to the Data Elements charter question</div>
<div> Lisa Phifer:The EWG did not deal with "thin data" as a category but today's thin data elements are in the EWG's minimum public data set</div>
<div> Greg Shatan 2:But none of us know what it means....</div>
<div> Bill Fanelli:Substitute "as yet to be defined" for minimum.</div>
<div> Michael Hammer:Regardless of whether we leave it in or take it out, we are going to have to cross that bridge.</div>
<div> Stephanie Perrin:Thanks and sorry Lisa, I dont pay enough attention to how we number things....</div>
<div> Greg Shatan 2:"defined" would be better than "minimum."</div>
<div> Benny Samuelsen / Nordreg AB:Suggestion: A minimum set of "thin data" elements, agreed on as a minimum standard, must be accessible by unauthenticated RDS users</div>
<div> Stephanie Perrin:Yes it would be better, I agree with greg</div>
<div> steve metalitz:+1 Greg and Stephanie (another rare entry!)</div>
<div> Michael Hammer:Does "defined" allow additional data elements beyond "defined"?</div>
<div> Greg Shatan 2:Defined set can always be redefined, by the same process.</div>
<div> Lisa Phifer:Proposed alternative: A defined set of "thin data" elements must be accessible by unauthenticated RDS users. </div>
<div> steve metalitz:"At least a defined set..." ? </div>
<div> Stephanie Perrin:Bearing in mind that we have not described the mechanism by which we make the data elements accessible</div>
<div> Lisa Phifer:Proposed alternative redux: At least a defined set of "thin data" elements must be accessible by unauthenticated RDS users. </div>
<div> Michael Hammer:I could live with this...</div>
<div> Greg Shatan 2:I suggest reading "A Framework and Standardized Methodology for Developing Minimum Clinical Datasets" by Swenson-Ranallo, Adam & Sainfort.</div>
<div> Greg Shatan 2:"The term "minimum dataset" or MDS is a commonly used, but poorly defined, term...</div>
<div> Lisa Phifer:Q5 starts on page 8</div>
<div> Lisa Phifer:I think people are reading "stated purpose" differently - 1) must a purpose be stated in policy, vs. 2) must a purpose be supplied with each query</div>
<div> Volker Greimann:the purposes for the requester must be aligned with the purpose of the collection/provision</div>
<div> Lisa Phifer:Note that we already agreed to these concepts:</div>
<div> Lisa Phifer:WG Agreement #2: Every "thin data" element should have at least one legitimate purpose.WG Agreement #3: Every existing "thin data" element does have at least one legitimate purpose for collection.</div>
<div> Lisa Phifer:Do we need to re-poll or do we have sufficient agreement?</div>
<div> Lisa Phifer:Proposed WG Agreement (to be confirmed by poll): "To deter misuse and promote accountability, RDS policy must state purpose(s) for public access to "thin data."</div>
<div> Michael Hammer:deter is not the same as prevent. Probably closer to mitigate.</div>
<div> Lisa Phifer:Requestors could be presented with terms of service, for example, without having to state purpose on query</div>
<div> steve metalitz:Can math majors confirm that 19-4 does not = 16?</div>
<div> steve metalitz:(on page 6)</div>
<div> Lisa Phifer:Ok steve, I double checked my math but you found one!</div>
<div> steve metalitz:I figured there were not arithmetic majors on the call.....</div>
<div> Lisa Phifer:@Steve, I happen to be a math major myself, but apparently one with increasingly poor eyesight :-)</div>
<div> Stephanie Perrin:I will never forget the blessed relief of dropping stats at Christmas in first year.....</div>
<div> Stephanie Perrin:(although I will admit to regretting not having finished it occasionally. Still, there is some pain not worth enduring,.......)</div>
<div> Lisa Phifer:If I recall, this was to discourage tiered access - those who pay more get more access (faster, broader)</div>
<div> Rod Rasmussen:@Michele - I prefer red wine as the best way to give yourself a headache. You're guaranteed one if you're drinking it while reviewing ICANN policy docs. ;-b</div>
<div> Michael Hammer:Would that be QoS (Quality of Service)?</div>
<div> Lisa Phifer:Note this is not yet policy - it is stating a goal for policy yet to be defined</div>
<div> Volker Greimann:How about "non-discriminatory access for all permissable uses"</div>
<div> Stephanie Perrin:you are a lot geekier than me Michele.....</div>
<div> Stephanie Perrin:and I like Volker's formulation....</div>
<div> Michele Neylon:we're still talking about thin data</div>
<div> Michele Neylon:so I don't see the aggregation as an issue</div>
<div> Michele Neylon:only for thin</div>
<div> Michele Neylon:I do with thick :)</div>
<div> Michael Hammer:Who decides what are "permissable uses"?</div>
<div> Lisa Phifer:Volker's proposal: "RDS access to "thin data" must be non-discriminatory access for all permissable uses" (for consistency with other agreements that should be legitimate purposes not permissible uses)</div>
<div> Stephanie Perrin:I am not sure that we do need it, once we have said that we must provide unauthenticated (non-identified) access to thin data. I agree with Lisa that it seems likely in the EWG that we were trying to make sure access was not tiered
on the basis of $$ or power.</div>
<div> Lisa Phifer:Red X if no principle is needed</div>
<div> Lisa Phifer:Green check if some principle is needed</div>
<div> Stephanie Perrin:Let the records show Steve and I agree, this is a red letter day indeed!</div>
<div> Michael Hammer:I think a broad principle is needed but we shouldn't get in the weeds.</div>
<div> Rod Rasmussen:And does such a principle cause *problems* if included or is it just a confirmation of one of ICANN's AOC's?</div>
<div> Michael Hammer:RDS access to "thin data" must be non-discriminatory.</div>
<div> Stephanie Perrin:Having said this, I could live with Volker's language.</div>
<div> Michael Hammer:How do we know their "purpose"?</div>
<div> Stephanie Perrin:Non-discriminatory is a pretty big word. One has to be clear in policy that one can take action to deter misfeasance</div>
<div> Lisa Phifer:Proposed alternative redux: RDS access to "thin data" must be non-discriminatory</div>
<div> Michael Hammer:misfeasance?</div>
<div> Michael Hammer:I'd leave that to lawwyers and torts.</div>
<div> Lisa Phifer:Another: RDS policies for access to "thin data" must be non-discriminatory (i.e., create a level playing field for all requestors)</div>
<div> Lisa Phifer:Chuck with or without ie?</div>
<div> Lisa Phifer:Green check if you support: RDS policies for access to "thin data" must be non-discriminatory</div>
<div> Lisa Phifer:Red X if you do not support the above</div>
<div> Stephanie Perrin:for all permissible purposes</div>
<div> Lisa Phifer:@Stephanie, does for all legitimate purposes work? For consistency with other agreements</div>
<div> Michael Hammer:I have a problem with that modification.</div>
<div> Lisa Phifer:Green check if you support: RDS policies for access to "thin data" must be non-discriminatory for all permissible purposes</div>
<div> Michael Hammer:Putting a red X for the modification.</div>
<div> Nathalie Coupet:But, is it really necessary to add 'permissible puroses, if you cannot verify that such purposes are legitimate?</div>
<div> steve metalitz:are we re-polling with Stephane's modification? </div>
<div> Nathalie Coupet:purposes</div>
<div> Michael Hammer:Exactly what Nathalie wrote.</div>
<div> Lisa Phifer:Green check if you support: RDS policies for access to "thin data" must be non-discriminatory for all legitimate purposes.</div>
<div> Lisa Phifer:You can state terms of service with purposes that are allowed/disallowed and take steps to enforce ToS, just as WHOIS does today</div>
<div> Volker Greimann:But if we figure out their purpose, we then have a handle, in case it is abusive or illegitimate</div>
<div> Volker Greimann:who is King Canoot?</div>
<div> Stephanie Perrin:Exactly as Volker says</div>
<div> steve metalitz:@Volker, Canute</div>
<div> Benny Samuelsen / Nordreg AB:sound drops</div>
<div> Michael Hammer:<a href="https://en.wikipedia.org/wiki/King_Canute_and_the_waves">https://en.wikipedia.org/wiki/King_Canute_and_the_waves</a></div>
<div> Volker Greimann:IP addresses are personal data now</div>
<div> Bill Fanelli:Legitimate or permissable - we should use whichever term we can define</div>
<div> Volker Greimann:depending on how the data is used, this may become personal data as well</div>
<div> Stephanie Perrin:I am confident that there are some jurisdictions that will want to know the purpose. I am confident that an investigation into a data aggregation operation that is criminal in nature would inquire as to how the aggregator got the data,
some of which can only come from ICANN accredited providers.</div>
<div> Michael Hammer:Then the jurisdiction should investigate the purpose.</div>
<div> Stephanie Perrin:Sure, the point is that there is merit in ICANN attempting to do the right thing</div>
<div> Lisa Phifer:Suggest we poll on the statement as last revised</div>
<div> Benny Samuelsen / Nordreg AB:Have to leave this meating, conflicting meeting coming up. Have fun...</div>
<div> Nathalie Coupet:I have a sore throat</div>
<div> Nathalie Coupet:Can't talk sorry</div>
<div> Nathalie Coupet:I can type</div>
<div> Nathalie Coupet:I thought it would be best to include this principle as soon as possible, since it is central to the GDRP, and not wait until later</div>
<div> Tom Undernehr:I was in support of Natalie's recommendation</div>
<div> Lisa Phifer:Perhaps propose a principle on proportionality to the WG list for discussion</div>
<div> steve metalitz:@Nathalie, how does this apply to thin data? </div>
<div> Nathalie Coupet:Data that is not absolutely necessary for a query shpould not be shared</div>
<div> Nathalie Coupet:Data has to be useful for the query</div>
<div> Nathalie Coupet:efficient</div>
<div> Michael Hammer:not sharing and efficient are orthongonal issues</div>
<div> Nathalie Coupet:What I meant, that only the data needed should be shared.</div>
<div> Lisa Phifer:@Rod, is your goal to provide an overview of existing policy that would support this proposed requirement?</div>
<div> steve metalitz:@Rod how is it handled at ICANN's lookup facility, <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__whois.icann.org_en-3F&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=gu_xEc0jIs-PVSa5yroc8eEfOjJfVo3EC4pHM_zlePM&s=hHc5Z1osunsHeaOeGQ_Nx6_fOhtBGMYY0aIYERi2XgU&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__whois.icann.org_en-3F&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=gu_xEc0jIs-PVSa5yroc8eEfOjJfVo3EC4pHM_zlePM&s=hHc5Z1osunsHeaOeGQ_Nx6_fOhtBGMYY0aIYERi2XgU&e=</a> </div>
<div> Rod Rasmussen:@Lisa - perhaps - it depends on what the "existing policy" actually consists of - you may have seen the write-up I did of relevant secstions of the RAA, RA, and ICANN Compliance reports, but the "ground truth" of what ICANN compliance is
actually testing to/enforcing is murky at best. If there's good documentation that seems to cover this well, great. We may want to tweak something that exists and bring it into the light though to help guide implementations down the road.</div>
<div> Rod Rasmussen:@Steve - great question! I'll add that to my research regime.</div>
<div> Lisa Phifer:@Rod, my point was that we're not yet developing policy or implementation guidance on this requirement, but you're gathering current info to help us understand the proposed requirement, correct?</div>
<div> Rod Rasmussen:Yes, but it ties into the current job of defining "reasonable access" while taking into account that data providers can use measures to protect their systems. It's an open question now, but that "meta principle" probably then has a pointer
to whatever we decide on is guidance in this area.</div>
<div> Lisa Phifer:@Rod, we still need to return to that proposed WG agreement to finalize it, once you deliver your summary - let's be sure to keep this tied to the proposed WG agreement when you email the WG list. Thanks!</div>
<div> Stephanie Perrin:WE could certainly work on better questions and send them to the leadership team. Also happy to comment on which ones we should cull.</div>
<div> Lisa Phifer:If we contract legal analysis on those questions now, we will have a chance at getting responses by fall, prior to trying to answer the foundational question in our first initial report</div>
<div> Lisa Phifer:It does not preclude further legal analysis on additional questions later</div>
<div> Stephanie Perrin:REsponses by fall? that seems awfully slow...</div>
<div> steve metalitz:Have to drop off now, thanks all! </div>
<div> Michele Neylon:I need to drop </div>
<div> Michele Neylon:see you</div>
<div> Lisa Phifer:@Stephanie, 2-3 months to select a legal team, contract with them, set SOW, and complete the work is pretty short actually</div>
<div> Lisa Phifer:Please response to poll on screen now regarding ICANN59 F2F meeting date</div>
<div> Kiran Malancharuvil:Is there a "submit" button? </div>
<div> Lisa Phifer:Yes = changing to Wednesday would affect you negatively</div>
<div> Lisa Phifer:No = keeping F2F on Tuesday would be ok for you</div>
<div> Amr Elsadr:Missing a comma.</div>
<div> Marika Konings:Say no - if you can participate on Wednesday - say yes, if you cannot participate on Wednesday :-)</div>
<div> Amr Elsadr:"Should this change be made, would this affect your ability to participate in the meeting..."</div>
<div> Michael Hammer:Dropping off.</div>
<div> Rod Rasmussen:I'm even more confused now. :-(</div>
<div> Marika Konings:We'll send out a doodle poll after this meeting with a better phrased question. Sorry about the confusion :-(</div>
<div> Rod Rasmussen:Thanks!</div>
<div> Nathalie Coupet:thank you! bye</div>
</div>
<div><br>
</div>
</div>
</div>
</body>
</html>