<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Greg Aaron, Jim Galvin, and I were all members of this SSAC work party and would be happy to elaborate further on any questions folks in this group have on this report. Note that we were looking at the issues we raised on this report as much more a comment on the implementation of the original policy work and where things were falling short rather than as something with any “new” policy implications. <div class=""><br class=""></div><div class="">As one of the co-chairs of the GNSO WP that proposed the CZDS (and actually probably the guy you can blame for kicking off the whole thing to begin with, for good or ill) it was very gratifying to see totally newly crafted policy based on scaling existing practices to the new realities of the gTLD expansion embodied in a well-defined and operational system that made existing practices and policy a lot more understandable, scalable, and efficient come into being. We have had some growing pains, but all-in-all, the system that was implemented reflects most of the ideas we put forward and does a pretty darn good job. Yes, there are areas for improvement which this advisory gets into, but the core system itself is delivering exactly what was intended. </div><div class=""><br class=""></div><div class="">The fact that we got this done remains one of my core inspirations in the entire ICANN process. I find it invigorating that ICANN provides a forum where someone in the community with a "good idea” on policy can bring it forward, explain it to others to get them on board, and then with work with those folks to create a movement, a PDP, and eventually an actual policy to see that idea come to fruition for the global Internet. Without a dime spent on lobbying or other “traditional” policy movers to boot mind you. Where else in the world can you find that? Pretty darn cool, I say! That’s why I keep coming to these meetings, spending countless hours on calls, and volunteering in many forums to try to get thing “done right” despite what seems like intractable odds at times.</div><div class=""><br class=""></div><div class="">I can only hope that at the end of the day, we end up putting forward a policy proposal along similar lines that we can all be proud of pointing to in the future saying, “yeah, I helped put that together” where all parties are served well in the end. I share these thoughts in the hopes of getting our work party a bit more aligned on the end goal here that we’ve been chartered with. Seems we have been having discussions of “camps”, “sides”, and far too many posts where folks are taking shots at each others' ideas or working towards a specifically narrow agenda. I would like us all to remember that we’re charged with creating a system for providing registration information that protects the interests of ALL stakeholders in making the Internet work, from those who actually register domains to those who provide the services to make that happen, to those who ensure the system isn’t abused to the detriment of all which will, in the end, seriously jeopardize the future of that system if it isn’t held to account properly.</div><div class=""><br class=""></div><div class="">Best wishes to all this week - I look forward to seeing many of you in JNB next week!</div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class="">Rod<div class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 18, 2017, at 5:24 PM, John Bambenek via gnso-rds-pdp-wg <<a href="mailto:gnso-rds-pdp-wg@icann.org" class="">gnso-rds-pdp-wg@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">I would agree bulk access (i.e. Entire zone file) should be treated different than ad hoc queries. <br class=""><br class="">--<div class="">John Bambenek</div></div><div class=""><br class="">On Jun 18, 2017, at 19:12, Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca" class="">stephanie.perrin@mail.utoronto.ca</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><p class=""><font size="+1" class=""><font face="Lucida Grande" class="">It is an interesting
report. I note that access can be denied if an applicant
fails to meet credential requirements. I did not see a sample
request/agreement/credential, but that would be interesting
for our purposes...later on in our process.</font></font></p><p class=""><font size="+1" class=""><font face="Lucida Grande" class="">Stephanie Perrin</font></font><br class="">
</p>
<br class="">
<div class="moz-cite-prefix">On 2017-06-18 19:27, Carlton Samuels
wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:CAOZQb9SFWnqye3cmF1bcTEOe799BO6nnebyFKJcDRTAQK2qGfQ@mail.gmail.com" class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small">You might find this SSAC
Advisory of interest, if only as a lesson demonstrqtingto an
arrangement where users are admitted to accessing of [zone]
file data.</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small">Coming now on 18 years,
ICANN has obliged gTLD registries to provide for free, copies
of their zone files to interested parties. This posture is
predicated on the acceptance that "<i class="">...<span style="font-family:arial,sans-serif" class="">the DNS is public
infrastructure, ICANN accredits gTLD registry </span><span style="font-family:arial,sans-serif" class="">operators, and zone
files are essential for a variety of legitimate purposes
that are in the </span><span class="gmail-fontstyle0" style="font-family:arial,sans-serif">public interest." </span></i><span style="font-family:arial,sans-serif" class=""></span></div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small"><i class=""><span class="gmail-fontstyle0" style="font-family:arial,sans-serif"><br class="">
</span></i></div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small">Referencing recent
discussions on the list, you might also wish to check out the
zone file dataset.</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small">In the SSAC's view, <i class="">'<span style="font-family:arial,sans-serif" class="">Policy and process
difficulties prevent subscribers from gaining and </span></i><span style="font-family:arial,sans-serif" class=""><i class="">then maintaining
reliable access to zone files.'</i> T</span>hey then
handily outlined these policy and process differences as well
as clearly state their recommendations for remediation.</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-family:"comic sans
ms",sans-serif;font-size:small">-Carlton</div>
<div class="">
<div class="gmail_signature">
<div dir="ltr" class="">
<div class=""><br class="">
==============================<br class="">
<i class=""><font face="comic sans ms, sans-serif" class="">Carlton A
Samuels</font></i><br class="">
<font face="comic sans ms, sans-serif" class=""><i class="">Mobile:
876-818-1799<br class="">
<font color="#33CC00" class="">Strategy, Planning,
Governance, Assessment & Turnaround</font></i></font><br class="">
=============================</div>
</div>
</div>
</div>
<div class="gmail_quote">
<div style="word-wrap:break-word" class="">
<div class=""><br class="">
</div>
<div class="">This Report is attached and can also be found on the <a href="https://www.icann.org/groups/ssac/documents" target="_blank" moz-do-not-send="true" class="">SSAC Reports</a> webpage.<br class="">
</div>
<div class="gmail-m_-8775278938200022505page" title="Page 1">
<div class="gmail-m_-8775278938200022505layoutArea">
<div class="gmail-m_-8775278938200022505column">
<div class=""><br class="">
</div>
</div>
</div>
</div>
</div>
</div>
<br class="">
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br class="">
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">gnso-rds-pdp-wg mailing list</span><br class=""><span class=""><a href="mailto:gnso-rds-pdp-wg@icann.org" class="">gnso-rds-pdp-wg@icann.org</a></span><br class=""><span class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" class="">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div></blockquote></div>_______________________________________________<br class="">gnso-rds-pdp-wg mailing list<br class=""><a href="mailto:gnso-rds-pdp-wg@icann.org" class="">gnso-rds-pdp-wg@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</div></blockquote></div><br class=""></div></div></div></body></html>