<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,</span><o:p></o:p></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><o:p></o:p></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, 11 April 2017 at 16:00 UTC.</span><o:p></o:p></p>
<p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; line-height: 15.6pt;">
<span style="font-size: 11pt; font-family: Calibri;"><b>MP3:</b></span><span style="font-family: Calibri;"><b> </b><o:p></o:p></span><a href="http://audio.icann.org/gnso/gnso-nextgen-rds-pdp-11apr17-en.mp3
" style="font-family: -webkit-standard; font-size: 14px;">http://audio.icann.org/gnso/gnso-nextgen-rds-pdp-11apr17-en.mp3</a></p>
<a href="http://audio.icann.org/gnso/gnso-nextgen-rds-pdp-11apr17-en.mp3
"><br>
</a>
<p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman'; line-height: 15.6pt;">
<span style="font-size: 11pt; font-family: Calibri;"><b>AC recording:</b></span> <a href="https://participate.icann.org/p6086e50408/" style="font-family: -webkit-standard; font-size: 14px;">https://participate.icann.org/p6086e50408/</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:</span><o:p></o:p></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></span><o:p></o:p></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;"> </span><o:p></o:p></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;"> </span><o:p></o:p></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 **</span><o:p></o:p></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;"> </span><o:p></o:p></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></span><o:p></o:p></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;"> </span><o:p></o:p></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;"><b>Wiki page: </b></span><o:p></o:p><a href="https://community.icann.org/x/CcPRAw" style="font-family: -webkit-standard; font-size: 14px;">https://community.icann.org/x/CcPRAw</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;"> </span><o:p></o:p></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.</span><o:p></o:p></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,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-family: Calibri;">Michelle </span><span style="font-family: -webkit-standard, serif;"><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;"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<span style="font-size: 11.5pt; font-family: Calibri;">———————————————</span><o:p></o:p></p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<o:p> </o:p></p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman';">
<b><u><span style="font-family: Calibri;">AC Chat Next-Gen RDS PDP WG Tuesday</span></u></b><b><u><span style="font-family: Calibri;">, 11 April 2017</span></u></b></p>
<div> Michelle DeSmyter:Welcome to the GNSO Next-Gen RDS PDP Working Group teleconference on Tuesday, 11 April 2017 at 16:00 UTC for 90 minutes. </div>
<div> Michelle DeSmyter:Agenda wiki page: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_CcPRAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=zg2LSish7IuO0wOlnrPN25a01S-CgxZ4Ijdyh7-bJVs&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_CcPRAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=zg2LSish7IuO0wOlnrPN25a01S-CgxZ4Ijdyh7-bJVs&e=</a></div>
<div> Michael Hammer:I'll need to drop off at 60 minutes - apologies.</div>
<div> Chuck Gomes:Hello all</div>
<div> Chris Pelling:Good afternoon all</div>
<div> Nathalie Coupet:Hello all</div>
<div> Maxim Alzoba (FAITID):Hello All</div>
<div> Theo Geurts:'lo</div>
<div> Maxim Alzoba (FAITID):be back in 2 min, reloading</div>
<div> Greg Aaron:Hi.</div>
<div> David Cake:hello all</div>
<div> andrew sullivan:Hi all</div>
<div> Alan Greenberg:I am getting no audio on AC.</div>
<div> Carlton Samuels:Howdy do all</div>
<div> andrew sullivan:Am I correct in believing that the silence is just pre-meeting silence, or is there a problem for me/</div>
<div> andrew sullivan:?</div>
<div> Lisa Phifer:there is audio now Andrew</div>
<div> Scott Hollenbeck (Verisign):Im not hearing anything, either</div>
<div> Alan Greenberg:No on AC.</div>
<div> Susan Prosser:I'm not getting it either</div>
<div> Carlton Samuels:I'm hearing people</div>
<div> David Cake:I also can't hear any audio</div>
<div> David Cake:Now I can</div>
<div> Chris Pelling:I hear Chuck talking now</div>
<div> andrew sullivan:audio now</div>
<div> Carlton Samuels:Chuck is speaking</div>
<div> Alan Greenberg:Carlton, sound on adobe connect?</div>
<div> Michelle DeSmyter:I will check into the issue</div>
<div> Chris Pelling:I can hear you Chuck :)</div>
<div> Susan Prosser:now I can </div>
<div> Theo Geurts:audio bridge fine</div>
<div> andrew sullivan:just started. Sounded like it buffered for approxmately forever and then started up</div>
<div> Carlton Samuels:@Alan, yes. Sound on the a/c room</div>
<div> Scott Hollenbeck (Verisign):Still no sound on AC for me</div>
<div> Maxim Alzoba(FAITID):Could anyone test adobe audio, I do not hear anything</div>
<div> Michele Neylon:AC audio isn't working, but I'm dialled in</div>
<div> Michele Neylon:now it is working</div>
<div> Scott Hollenbeck (Verisign):Now it's there!</div>
<div> Maxim Alzoba(FAITID):I do hear aduio</div>
<div> Alan Greenberg:Just started!</div>
<div> Kal Feher:oh. audio just arrived</div>
<div> Maxim Alzoba(FAITID):UPDATE: my SOI has SSC now in .12.</div>
<div> Scott Hollenbeck (Verisign):silence again...</div>
<div> Alex Deacon:I heard Andrew but nothing else. I'll dial in....</div>
<div> Scott Hollenbeck (Verisign):I heard maxim</div>
<div> Benny Samuelsen / Nordreg AB:same here else complety silence</div>
<div> Kal Feher:I heard a bit of Andrew sullivan and maxim, but not hearing others. AC audio is not receiving all speakers atm</div>
<div> Alex Deacon:same for me. </div>
<div> Sara Bockey:seems to be working for me</div>
<div> Alan Greenberg:I am dialed in but on AC, I am hearing everyone I think.</div>
<div> Benny Samuelsen / Nordreg AB:People are not been let into the meeting</div>
<div> Sara Bockey:Stephanie is waiting to get in....can staff assist?</div>
<div> andrew sullivan:yes :)</div>
<div> Chris Pelling:Can someone let Stewphanie Perrin in</div>
<div> Greg Shatan:Both times I've logged into AC today, it has apparently knocked my Internet connection offline. It could be an instance of correlation not equaling causation, but my Internet connection is usually solid (if unspectacular).</div>
<div> Michelle DeSmyter 2:If anyone does need a dialout, please private chat and and we can have an operator dial out to you as well</div>
<div> Kal Feher:audio just started to pick up chuck in AC.</div>
<div> Michelle DeSmyter 2:IT is addressing the issue right now as well</div>
<div> Carlton Samuels:Except for Jamaica! I gotta call the US Toll free via Skype!</div>
<div> Lisa Phifer:link to 2a is <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078601_ICANN58-2DPrivacy-2DPanel-2DResponses-2DDraft-2D7April2017.docx&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=jmGrgFi2F0Q5OgaSwqXmJKgRT5OyvwI521pY-i7Nvug&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078601_ICANN58-2DPrivacy-2DPanel-2DResponses-2DDraft-2D7April2017.docx&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=jmGrgFi2F0Q5OgaSwqXmJKgRT5OyvwI521pY-i7Nvug&e=</a></div>
<div> andrew sullivan:The nice thing about that Internet (it might catch on yet!) is that it can route around the damage of the traditional POTS system :)</div>
<div> Michelle DeSmyter 2:I will send the invite out to everyone now as a reminder with phone numbers</div>
<div> Volker Greimann:is there no sound today</div>
<div> Lisa Phifer:@Volker, there is a tech issue being resolved now</div>
<div> Volker Greimann:ah ok. I now got to hear chuck for 2 secs</div>
<div> Lisa Phifer:@Volker, if you can dial-in please do</div>
<div> Volker Greimann:sorry</div>
<div> Benny Samuelsen / Nordreg AB:sound finally</div>
<div> Marina Lewis:Hi everyone</div>
<div> Lisa Phifer:We will be using the answers given to inform our deliberation on questions in our charter. Recall that this WG's goal in asking the questions was to inform our work. but we have many ohther sources of input to consider as well</div>
<div> Michael Hammer:My suggestion is to change the approach for private registration. Let the organization providing the private registration be the registrant of record and responsible for the activities and use of the domain.</div>
<div> Volker Greimann:law enforcement documents are usually very one-sided</div>
<div> Volker Greimann:after all, they represent the state of how they see the law.</div>
<div> Michael Hammer:the relationship between the individual and the private registration organization be contractual.</div>
<div> Michelle DeSmyter 2:Is everyone able to hear the audio through your Adobe Connect?</div>
<div> Lisa Phifer:@Michael, that would be a potential solution to raise during deliberation on our privacy charter questions</div>
<div> Volker Greimann:if the law is X, that is how it has to be, ultimately</div>
<div> Michael Hammer:Law enforcement or legal entities can serve search warrents or subpeonas if they need to know the actual registrant.</div>
<div> Greg Shatan:We should make sure that the panelist are all aware of this document and have an opportunity to respond and/or contribute.</div>
<div> Nathalie Coupet:I think Greg would like the input of privacy lawyers who can defend IPC interests</div>
<div> Nathalie Coupet:Consultants?</div>
<div> Michael Hammer:My concern is the actual stopping of abusive/malicious activity that is happening (malware, etc).</div>
<div> Greg Shatan:I would like the input of privacy lawyers who can dieal with this in commercially pragmatic manner.</div>
<div> Nathalie Coupet:Does the GNSO have a budget for this?</div>
<div> Greg Shatan:Not merely for intellectual property owners, but for consumers, anti-abuse investigators of all types, consumers and other end-users. My concerns are not merely parochial.</div>
<div> Nathalie Coupet:I didn't think they were. </div>
<div> Lisa Phifer:@Susan, do you need any staff support (to arrange call, assemble survey, etc) - if so, let us know</div>
<div> andrew sullivan:My suggestion to the team is that we just pick a different term. I wonder whether that would be acceptable to people?</div>
<div> andrew sullivan:(re: authoritative)</div>
<div> Lisa Phifer:@David, same question, let us know if you need a call scheduled, etc</div>
<div> andrew sullivan:I think that Nathalie Coupet has also volunteered to the team, BW</div>
<div> andrew sullivan:BTW</div>
<div> Jim Galvin (Afilias):we could have our own glossary of course, and add the nuance we need to the technical definition to serve our purpose. But I also support a different term.</div>
<div> Nathalie Coupet:Thanks, Andrew</div>
<div> David Cake:Yes, Nathalie has also volunteered. </div>
<div> Volker Greimann:IIRC, this discussion was also a part of the Thick Whois PDP deliberations.</div>
<div> David Cake:And yes, we may pick a different term if we can find one.</div>
<div> Volker Greimann:maybe we can draw on that work regarding the definition of authoritativeness?</div>
<div> Scott Hollenbeck (Verisign):@Volker, I think their definition is part of what people are disagreeing with. I know I don't agree with it.</div>
<div> David Cake:Thick whois is relevant, yes. </div>
<div> Carlton Samuels:The sound is totally gone now!</div>
<div> Carlton Samuels:Reloaded and back!</div>
<div> Volker Greimann:@Scott: Disagreement is good, but we then need to ensure we properly define the term going forward. I think it is problematic if one particular term means one thing during one PDP that is still on its way to implementation and another
thing during another. </div>
<div> Scott Hollenbeck (Verisign):Agreed, and so maybe Andrew's suggestion is a good one.</div>
<div> Michele Neylon:The IRT vs the PDP ... .. </div>
<div> Volker Greimann:once a certain definition has been agreed, that should have some weight going forward, and any changes should be well argued and documented.</div>
<div> Volker Greimann:and ideally also be applied retroactively to already completed work</div>
<div> Alan Greenberg:That is 6 hours or a full 1/4 of the meeting devoted to this PDP. A big commitment for those of us that have other AC/SO work as well!</div>
<div> Volker Greimann:@Greg: I prefer to be legally compliant-pragmatic</div>
<div> Carlton Samuels:@Chuck: Would it be useful to load the EWG's work on this and see if we can get some minds concentrated?</div>
<div> Lisa Phifer:See <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078512_Merged-2DThinDataPurposes-2Dv1.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=x9E4oDJF8UAW8cXBbxUBQ1xwU978WJFqvlVz8ZKrvx4&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64078512_Merged-2DThinDataPurposes-2Dv1.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=x9E4oDJF8UAW8cXBbxUBQ1xwU978WJFqvlVz8ZKrvx4&e=</a></div>
<div> Volker Greimann:as in: best be on the safe side - pragmatic</div>
<div> Lisa Phifer:@Carlton, the EWG's Annex D has been merged with Andew's proposed approach in this document being displayed now</div>
<div> Amr Elsadr:All documents relevant to today's call are posted on the meeting wiki page here: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_CcPRAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=zg2LSish7IuO0wOlnrPN25a01S-CgxZ4Ijdyh7-bJVs&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_CcPRAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=zg2LSish7IuO0wOlnrPN25a01S-CgxZ4Ijdyh7-bJVs&e=</a></div>
<div> Carlton Samuels:@Lisa. Thanks.t noticed</div>
<div> Greg Shatan:@Volker, I'm also suggesting being legally compliant and pragmatic. Our goal should be to accomplish our objectives to the greatest extent within the bounds of the law, reasonably and pragmatically applied.</div>
<div> Volker Greimann:@greg: maybe the term "pragmatic application of the law" worries me more than it should then? I rather apply the law with some safe space than pragmatically</div>
<div> Michele Neylon:We might have very different objectives though :)</div>
<div> Lisa Phifer:Note that this WG already looked at EWG's permissible purposes when we deliberated on charter subquestion 3.2. See our working document for purposes for collection of thin data.</div>
<div> Nathalie Coupet:@Michele: We could apply the legal principle that what is not forbidden is allowed. </div>
<div> andrew sullivan:@Nathalie: I'm not a lawyer: is that actually a univeral legal principle?</div>
<div> andrew sullivan:I know it's a legal principle in some systems, but I don't know about all</div>
<div> Nathalie Coupet:It's a general legal principle in French law, would need to research for other legal systems</div>
<div> Volker Greimann:@nathalie: when it comes to data protection, the principle is turned around. what is not allowed is prohibited</div>
<div> Volker Greimann:as in: if there is not a legitimate reason to collect, store, etc the data, you should not be doing it</div>
<div> Lisa Phifer:secure protected credentials, Rod</div>
<div> Greg Shatan:Pragmatic application does not imply a lack of "safety." We should mitigate risk, not attract it. On the other hand, if one wanted to be absolutely safe, one would stay in bed.</div>
<div> Michael Hammer:Lots of people die in bed.</div>
<div> Greg Shatan:The bathroom is the most dangerous room in the house. That doesn't keep me out of it....</div>
<div> Greg Shatan:The kitchen is number two and I definitely don't avoid that. But I do take pragmatic precautions.</div>
<div> andrew sullivan:@Michael: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.goodreads.com_book_show_25506781-2Dwe-2Dll-2Dall-2Dbe-2Dburnt-2Din-2Dour-2Dbeds-2Dsome-2Dnight&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=h7WbvtL0-Z1h3gCXrs4AgTxzGVm3MujKLL-J9EYF_J0&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.goodreads.com_book_show_25506781-2Dwe-2Dll-2Dall-2Dbe-2Dburnt-2Din-2Dour-2Dbeds-2Dsome-2Dnight&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=h7WbvtL0-Z1h3gCXrs4AgTxzGVm3MujKLL-J9EYF_J0&e=</a> ?</div>
<div> Greg Shatan:@Michele, I was thinking more about the objectives of the RDS, but I suppose there might be some difference of opinion on that as well....</div>
<div> Michael Hammer:Rod is definitely and old hand. <G></div>
<div> Michele Neylon:lol</div>
<div> Greg Shatan:@Andrew, @MIchael, <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__youtu.be_jpkGvk1rQBI&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=WDNPkUT5zFinHOf1e8IecaBYYIUUiO9A8cURUQv_yoA&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__youtu.be_jpkGvk1rQBI&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=WDNPkUT5zFinHOf1e8IecaBYYIUUiO9A8cURUQv_yoA&e=</a> ("How
Can We Sleep When Our Beds are Burning?", Midnight Oil)</div>
<div> Lisa Phifer:Correction: it is section 2.2.2 of our working document that enumerates our rough consensus agreements on purposes for collection so far</div>
<div> Lisa Phifer:Working Document: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_56986791_KeyConceptsDeliberation-2DWorkingDraft-2D4April2017.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=jyj3QbF_ooqZ9hERQgM2mCkkCbFgjdhdoSDMDhpqhX4&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_56986791_KeyConceptsDeliberation-2DWorkingDraft-2D4April2017.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=jyj3QbF_ooqZ9hERQgM2mCkkCbFgjdhdoSDMDhpqhX4&e=</a></div>
<div> Volker Greimann:@stephanie: In many cases the reseller will not be known by the registrar or registry</div>
<div> Michael Hammer:Stephanie does raise an interesting point.</div>
<div> Michele Neylon:reseller is in thick</div>
<div> Michele Neylon:in .com and .net anyway</div>
<div> Stephanie Perrin:great thanks!</div>
<div> Volker Greimann:@Michele: Only the reseller of the registrar, but not the reseller of the reseller, or their reseller, or theirs....</div>
<div> Michele Neylon:Volker - no of course not</div>
<div> Michele Neylon:that would make the record stupidly long :)</div>
<div> Michael Hammer:Weknow that some resellers are more problematic than others from an abuse perspective.</div>
<div> Volker Greimann:so the reseller field does not necessarily inform anyone about where they should go to manage their domain</div>
<div> Michele Neylon:Volker - true</div>
<div> Maxim Alzoba(FAITID):also resellers can create a chain ...</div>
<div> Maxim Alzoba(FAITID):of resellers</div>
<div> Lisa Phifer:See references in table to group (i) - that's the group Andrew is referring to at the moment</div>
<div> Lisa Phifer:Group (i) includes Sponsoring Registrar IANA ID and Registrar Name</div>
<div> Sara Bockey:I can't hear anything</div>
<div> Sara Bockey:audio back but I missed the last 3 mins of convo</div>
<div> Amr Elsadr:@Sara: Would you like a dial-out?</div>
<div> andrew sullivan:In case it helps, the mail that I sent about this where I laid out the details has Subject: a suggestion for "purpose in detail"</div>
<div> Sara Bockey:Thanks, Amr... I think I'm good for the moment</div>
<div> andrew sullivan:hang on, I'll find the link in the archives</div>
<div> Amr Elsadr:@Sara: Great.</div>
<div> andrew sullivan:The thread starts at <a href="http://mm.icann.org/pipermail/gnso-rds-pdp-wg/2017-March/002575.html">http://mm.icann.org/pipermail/gnso-rds-pdp-wg/2017-March/002575.html</a></div>
<div> andrew sullivan:I think the table is really helpful, however</div>
<div> andrew sullivan:"authoritative" is the right name, IMO :)</div>
<div> andrew sullivan:but anyway, the IANA registry is the Real Source for the name</div>
<div> Lisa Phifer:Andrew's document is in the meeting materials as well, in printable form. See <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64076964_Sullivan-2DSuggestionForPurposeInDetail.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=HF3J0ttMiuEKP4JzEGZhzpiLoj84rILXqW4PlnIIxW0&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_64076964_Sullivan-2DSuggestionForPurposeInDetail.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=8_WhWIPqsLT6TmF1Zmyci866vcPSFO4VShFqESGe_5iHWGlBLwwwehFBfjrsjWv9&m=8TMv3EprOWXPDmVpMx3a4yxWaxUiyxrkheAFaSQlzQc&s=HF3J0ttMiuEKP4JzEGZhzpiLoj84rILXqW4PlnIIxW0&e=</a></div>
<div> Lisa Phifer:All of Andrew's text is captured in the merged document, with the exception of the concept of "maximal use"</div>
<div> andrew sullivan:At the moment, the relevant IANA registry is listed as a protocol parameters registry. Those are not normally queried online, but are instead imbedded in other systems</div>
<div> Chris Pelling:there is also a registered name server lookup to find registered IPs via whois </div>
<div> andrew sullivan:I agree with Lisa that everything is captured in this merged document & I don't want to minimise that or suggest it's not excellent work</div>
<div> Lisa Phifer:@Andrew, possibly it would help to group the rows to reflect your data groups?</div>
<div> andrew sullivan:I just don't want people to focus exclusively tablewise, since it's important to realise that some rows go together</div>
<div> Lisa Phifer:The related rows are adjacent but perhaps with color-coding and a summary of why the rows are grouped?</div>
<div> andrew sullivan:In respect of the remit issues: this is why not everything I discussed in the mail I sent reflected EWG purposes, because once I had a single reason why everyone needed the data, other purposes didn't matter I think</div>
<div> andrew sullivan:@Lisa: no, I think this is good enough. We're all clever enough to keep it in mind as long as we commit to doing so :)</div>
<div> Rod Rasmussen:For data collection, one "legitimate" purpose is probably sufficient (ignoring retention and other ancilliary issues). Full debate on the legitimacy of all purposes becomes much more important for discussions around what data is provided
to data requestors and under what conditions (e.g. gated vs. open)</div>
<div> Roger Carney:@andrew, I sort of agree, except that multiple purposes are also useful "in the future" as at some point a single purpose may no longer be valid</div>
<div> Jim Galvin (Afilias):@rod +1</div>
<div> Jim Galvin (Afilias):I wish we would carefully separate collection from publication</div>
<div> Rod Rasmussen:@Roger - I kinda ignored that for my answer, but yes, you are dead-on correct - we discussed that in the EWG as well, which is one reason we gave the full matrix. Such an event is unlikely, but possible.</div>
<div> Jim Galvin (Afilias):as far as I know there is nothing extra that folks are looking to be collected than what has already been collected. so why do we need more than one purpose?</div>
<div> Marc Anderson:@Jim what about language tag?</div>
<div> Michele Neylon:woohoo my senility must be improving :)</div>
<div> andrew sullivan:I approached this only from collection. I thought we weren't talking about pub yet</div>
<div> Jim Galvin (Afilias):@marc - language tag is only relevant if it's present on data you're publishing. seems to me it would have the "rule" applied as the data itself, since it's an integral part of the data.</div>
<div> Rod Rasmussen:The "academic" question is actually quite nuanced and layered given ICANN's commitments to transparency and other resposibilities around competition, access, etc. One of the ways you *can* do that is by providing data to researchers working
under well-defined (and it is in the world today) academic guidelines and oversight to do studies on these various topics. For example, can people in developing countries get access to domain registration services or are they priced out of the market, or
do they not have local registrars available that provide local language services? This kind of important question needs RDS-style data at scale to answer. So one or our jobs may well be to answer that question.</div>
<div> Maxim Alzoba(FAITID):not all knids of research are good for community .. like research on methods to instantly collapse DNS all over the planet :) - pretty much legal </div>
<div> Rod Rasmussen:@Maxim - yeah, though that example is probably doable via DNS queries and zone files without any RDS involvment at all. :-(</div>
<div> Roger Carney:@Rod, I would say that is not "academic" you are defining a more specific ICANN competition/chose evaluation</div>
<div> Michele Neylon:eh? the IANA ID is unique to each registrar</div>
<div> Chris Pelling:I was about to say that too Michele</div>
<div> Michele Neylon:Unless I've misunderstood him</div>
<div> Maxim Alzoba(FAITID):not all .. 9998 and 9999 are not :)</div>
<div> Michele Neylon:but what I'm hearing is incorrect</div>
<div> Roger Carney:@andrew, good point, some data is actively captured, passively "captured" and some generated</div>
<div> Michele Neylon:That's a "trading name"</div>
<div> Michele Neylon:totally different</div>
<div> Michele Neylon:Enom had over 250 IANA IDs</div>
<div> Michele Neylon:and quite a few companies are called one thing officially and trade as something totally different</div>
<div> Abdeldjalil Bachar Bong:IANA ID IS THE NAME OF REGISTRAR in Whois ?</div>
<div> Maxim Alzoba(FAITID):formally they are different legal bodies </div>
<div> Michele Neylon:No</div>
<div> Michele Neylon:the IANA ID is a number</div>
<div> Rod Rasmussen:But to my point - one of the questions we wrestled with as the EWG is how to provide large-scale access to academic researchers in a gated-access RDS world, as there are an unknowable amount of potential community-wide beneficial studies
that could be performed, but only with broad access that may not be available otherwise. That's one of the ways this particular use-case was raised in awareness and priority in the EWG work. Anyways, this discussion is much more relevant for the publication
portion of our deliberations - there is likely no "academic only" data element on the collection docket.</div>
<div> Michele Neylon:which has a name with it</div>
<div> Lisa Phifer:Should Registrar Name be a registration data element?</div>
<div> andrew sullivan:It certainly is</div>
<div> Michele Neylon:it is</div>
<div> Chris Pelling:It is showed and is a requirement of the RAA</div>
<div> Lisa Phifer:It is currently a data element specified in the RAA</div>
<div> Maxim Alzoba(FAITID):9998 9999 are registries acting as registrars ...so it is not very unique</div>
<div> Lisa Phifer:I think the question to this WG is: Should Registrar Name be a registration data element? It is - should it be, in order to meet requirements for registration data?</div>
<div> andrew sullivan:I withdrew my hand because of time, but I mentioned this upthread</div>
<div> Alan Greenberg:So if a registrar changes its legal name, and the next week I do a WHOIS query, does it reflect the old name or new name?</div>
<div> Chris Pelling:depends how quick they change it</div>
<div> andrew sullivan:The way the names for IANA ids get bound in is usually static</div>
<div> andrew sullivan:this is because the IANA registry is a protocol parameters reg</div>
<div> Alan Greenberg:What I am asking is does the registry need to go through its entire WHOIS database and make that change?</div>
<div> Theo Geurts:the RAA is perhaps not the best example when it comes to guiding us through this</div>
<div> Chris Pelling:ICANN gets updated, then it trickles down to the registries</div>
<div> andrew sullivan:so it gets included in programs rather than queried real time</div>
<div> andrew sullivan:it's like the protocol number for TCP</div>
<div> andrew sullivan:@Alan: that's a question of how the registry has implemented</div>
<div> andrew sullivan:if the have a clue, they used a table and update it once</div>
<div> andrew sullivan:some people don't have such a clue and need to update many rows :)</div>
<div> Alan Greenberg:I guess I would have expected the id to be in the actual record and the ID:Name registry contents periodically cached.</div>
<div> Maxim Alzoba(FAITID):cross control over registrars might be out of scope of this group </div>
<div> Greg Shatan:Google is now a subsidiary of Alphabet; it remains a discrete company, though wholly-owned by Alphabet....</div>
<div> andrew sullivan:@Alan: how someone implements stuff is often surprisng</div>
<div> Alan Greenberg:@Andrew Ain't that the truth!</div>
<div> Marina Lewis:@Chuck - only if we give equal air time to a "maximalist" approach.</div>
<div> Fabricio Vayra:+Marina</div>
<div> Fabricio Vayra:@Jim -- Will we link from the ID to the record?</div>
<div> andrew sullivan:What this question really boils down to is, "Should the RDS incorporate the IANA registry of registrars?" or maybe "Should IANA's collection of registrar names be considered part of the RDS"? If we frame it that way, I think the answer
is yes</div>
<div> Marina Lewis:I would like to hear reasons why having the registar listed as a registration data element has NOT been working. In other words, what is the rationale for removing this element from public view now?</div>
<div> Michele Neylon:it's a data managment issue</div>
<div> andrew sullivan:@Marina: there is no rationale, but we're only talking about collection :)</div>
<div> Fabricio Vayra:+1 Marina</div>
<div> Michele Neylon:1448 = Blacknight</div>
<div> Michele Neylon:You don't need to collect "Blacknight"</div>
<div> Michele Neylon:it's already mapped to it</div>
<div> Fabricio Vayra:@Michale, will thre be a link to = Blacknight?</div>
<div> Chris Pelling:@Jim, you cannot say "Ip" its the registrar login</div>
<div> Michele Neylon:So I tend to agree with Jim</div>
<div> andrew sullivan:I think the point I made above is the way to frame it, though</div>
<div> Theo Geurts:+1 Jim</div>
<div> Michele Neylon:Fabricio - you can display the name in the output</div>
<div> andrew sullivan:But we're out of time :)</div>
<div> Marina Lewis:I ask because the approach we are being asked to take (to achive consensus) is not to throw the baby out with the proverbial bathwater, but rather to identify specific reasons why an existing practice is not working. So far, I have heard
nothing.</div>
<div> Michele Neylon:you just don't need to collect it</div>
<div> Chris Pelling:a few platform providers might use the same IP for a few registrars, but, on EPP connection the login would be unique</div>
<div> andrew sullivan:@Michele: someone needs to collect it</div>
<div> Lisa Phifer:Note that we are running over call end time, hang in there a minute if you can</div>
<div> Fabricio Vayra:QUESTION: So will the ID link to the registrar details?</div>
<div> andrew sullivan:you're saying the registry doesn't need to. That's true</div>
<div> Chris Pelling:but agree with Jim regarding Minimal, its not needed </div>
<div> Michele Neylon:Andrew - IANA has it - so does ICANN</div>
<div> andrew sullivan:But the IANA registry _does_ need to</div>
<div> andrew sullivan:and so the question is only whether that's part of the RDS. I say yes.</div>
<div> Michele Neylon:Andrew - of course</div>
<div> Michele Neylon:Or displayed </div>
<div> Michele Neylon:personally I don't care </div>
<div> Stephanie Perrin:Does not adding it introduce risk/inaccuracy? IN which case we discuss it much later when we discuss risk/accuracy.</div>
<div> andrew sullivan:The IANA registry is not today looked up in real tie</div>
<div> andrew sullivan:time</div>
<div> andrew sullivan:and that's important to keep in mind</div>
<div> Michele Neylon:exactly it's static</div>
<div> Greg Shatan:Maybe that should be solved.</div>
<div> Stephanie Perrin:Have to get on next call, by all!</div>
<div> Chris Pelling:have fun all and happy Easter to those that have it :)</div>
<div> Maxim Alzoba(FAITID):bye all</div>
<div> Greg Shatan:Make the database opaque and difficult to understand is not a great plan.</div>
<div> Fabricio Vayra:+1 Greg S</div>
<div> andrew sullivan:@Greg: the RDAP approach makes this easier, actually</div>
<div> Maxim Alzoba(FAITID):it is not simple already </div>
<div> Greg Shatan:Chag Sameach and Good Passover to those celebrating that, as well.</div>
<div> Theo Geurts:ciao</div>
<div> Chris Pelling:a whois query is very simple</div>
<div> andrew sullivan:Regrets for next week -- I'll be at a meeting in China</div>
<div> Fabricio Vayra:Thanks, all. Bye.</div>
<div> andrew sullivan:so the time would be good, but it'll probably interfere with having to be at the other meetings</div>
<div> Abdeldjalil Bachar Bong:au revoir </div>
<div> Marina Lewis:+1 Greg</div>
<div> andrew sullivan:thanks and bye</div>
<div> Amr Elsadr:Thanks all. Bye.</div>
<div> Nathalie Coupet:Bye all! Very interesting!</div>
<div> Marina Lewis:Bye all</div>
<div> Greg Aaron:"The domain name will be necessary for every legitimate purpose."? Is ther ea word missing in there?</div>
</div>
<div><br>
</div>
</div>
</div>
</body>
</html>