<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office">
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<!--[if gte mso 9]>
<xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
<o:PixelsPerInch>96</o:PixelsPerInch>
</o:OfficeDocumentSettings>
</xml>
<![endif]-->
<style type="text/css">* a:hover{cursor:pointer;}</style>
<style>body {-webkit-animation:bugfix infinite 1s;}@-webkit-keyframes bugfix {from {position:relative;}to {position:relative;}}</style>
</head>
<body style="word-wrap:normal; word-break:break-word;">
<style>a {word-wrap:normal;word-break:break-word;}.background-contain {background-size:contain;}@media only screen and (max-width:600px) {.container {-webkit-text-size-adjust:none !important;}.container,.palm-one-whole {width:100% !important;min-width:100% !important;}.palm-one-half {width:50% !important;min-width:50% !important;box-sizing:border-box;}blockquote .container,blockquote .container div,blockquote .container table {width:auto !important;min-width:0 !important;position:relative !important;}img {max-width:100%;}.border-outer,.border-middle,.border-inner,.inner,[title="separator"] {width:100% !important;}.innercell {padding:8px !important;}.palm-block {display:block !important;}td.palm-one-whole {display:inline-block !important;padding:0;}td.palm-one-whole:first-child:not(:only-child) {margin-bottom:16px;}td.hostname {padding-top:3px !important;}}@media only screen and (min-width:601px) {.preview-card {max-width:600px !important;}}@media only screen and (min-device-width :320px) and (max-device-width :568px),only screen and (min-device-width :768px) and (max-device-width :1024px),only screen and (max-device-width:640px),only screen and (max-device-width:667px),only screen and (max-width:480px){.container {width:100% !important;min-width:100% !important;}.p,.small,li,font[size="2"],font[size="3"] {font-size:1em !important;}}@media only screen and (min-device-width :320px) and (max-device-width :568px),only screen and (min-device-width :768px) and (max-device-width :1024px),only screen and (min-device-width :1224px) {.message-wrapper {padding-top:6px;}.apple-only[style] {display:block !important;max-height:none !important;line-height:normal !important;overflow:visible !important;height:auto !important;width:100% !important;position:relative !important;}.no-apple {display:none !important;}form {font-size:inherit;}input[type="text"] {height:43px;padding-left:4px !important;}button:hover {cursor:pointer;}}@media only screen and (min-device-width :1224px) {.apple-mail-form {display:block !important;background-color:white !important;}}* [office365] .outlook-com-hidden {display:none !important;}* [office365] .outlook-com-button {display:block;}* [office365] .outlook-com-only {display:block !important;max-height:none !important;line-height:normal !important;overflow:visible !important;height:auto !important;width:100% !important;position:relative !important;}</style>
<!--[if (gte mso 9)|(IE)]>
<style>a,body {font-family:'Calibri',Arial,sans-serif;}img {border:none !important;-ms-interpolation-mode:bicubic;}td {mso-line-height-rule:exactly !important;}.mso-card-inner table {border-collapse:collapse !important;mso-table-lspace:0pt;mso-table-rspace:0pt;vertical-align:top;}.outlook-com-only {display:none !important;font-size:0 !important;}#mso-one-whole {width:100% !important;}.border-outer,.border-middle,.border-inner {border:none !important;}.border-middle,.border-inner {width:100% !important;}.mso-border-outer,.mso-border-middle,.mso-border-inner {padding:1px;}.mso-border-outer {background-color:rgb(245,255,255);}.mso-border-middle {background-color:rgb(223,246,255);}.mso-border-inner {background-color:rgb(153,176,225);}</style>
<![endif]-->
<table class="container" lang="container" border="0" cellpadding="0" cellspacing="0" valign="top" style="width:100%; margin-top:6px;">
<tr>
<td valign="top" class="message-wrapper" style="line-height: 1.31; color: #222; font-family: arial, sans-serif;">
<!--[if mso]><table border="0" cellpadding="0" cellspacing="0" valign="top" style="border-collapse:separate;"><tr><td valign="top"><![endif]-->
<div><span lang="EN-GB">Thank you
for taking the time to outline the architecture of the existing WHOIS service
and how it has evolved over time, Andrew. With this background and your extremely
useful diagrams I now have a much clearer understanding of to what extent
different parties wield control (or not) over the data of registrants. I am not going to be able to enter into any
conversation where we are debating the finer technical points of how a protocol
functions, but I can comment on more focused policy applications. Certainly I
do not want to contribute to any degradation of what has made the Internet what
it is today – a place for limitless innovation and where users trust it as safe
and secure environment for commerce and communication.</span></div><div><font><br></font></div><div>I have
tried my best not to approach this working group with any pre-conceived ideas
as to what I would like the final outcome to be (partially because I do not have the institutional knowledge to even formulate these ideas in the first place <span class="js-command-span"><img class="emoji" src="https://dv4jgpe7xb4ws.cloudfront.net/v1/unicode/1f609.png" alt="😉" style="vertical-align: text-top; max-height: 1.1em; height: 1.1em; min-height: 1.1em; width: 1.1em;"></span>), but I lay my cards out on the
table and say it is very important to me that the Internet’s growth is not
impeded in any way. I worry, looking at Model V in particular, that we could
end up in a situation where we all end up wishing a different approach could
have been taken. We could very well end up with an outcome where the reasons behind
establishing this working group are not addressed, where ICANN or another party
is stuck with huge costs, and where the Internet’s growth and evolution is permanently
stifled.</div><div><font><br></font></div><div>There are six
issues that I see with Model V, four of which Mark has already outlined: questions
around jurisdiction, privacy, cost, and service level agreements/overall
accountability. I would also like us to consider potential liability for the
manager of the federated store for data breaches (and liability for those who
have retrieved data from the RDS and have lost it once it was in their
possession), along with the potential anti-trust implications of there being
one, privately-owned database which all gTLD registries must use.</div><div><font><br></font></div><div>What I like
about the Internet, as we know it today, is that it is for everyone. There is
no central authority that permits different classes of Internet activities, which
means it is possible for anyone to connect to the network and to build new
parts of it. This innovation (which happens organically, without requiring
permission) has come about because the Internet’s technologies are based on
interoperability and reusable building blocks that might have been built for
one purpose but have come to support some other important function at a later
date. This is what I want to continue happening. A distributed RDS which anyone
can improve through cooperation and collaboration, because its success depends
on its continued relevance and utility, and not on some arbitrary clause in a
contract that prioritises 'incumbation' (for lack of a better word) over innovation.</div><div><font><br></font></div><div>I
understand that we are not yet at a stage where we should be deliberating on
what the RDS should look like (if we even conclude one is required), so before
I continue to outline my strong opposition to Model V, may I please clarify:
where did the idea for this federated RDS originate from? Is it just because in
the wish list of possible requirements we have to consider, a few suggested
a federated system? Or is there something more concrete in the works? (And if
so, can you please link me to any IETF discussions on this?) Thank you.</div><div><font><br></font></div><div>Thank you again, Andrew, for taking the time to go back to basics. The diagrams you have produced of how WHOIS-related protocols and services have evolved over time have left me much more informed of the differences between 'thick' and 'thin' registries than I was a few days ago. </div><div><font><br></font></div><div>Best wishes,</div><div><font><br></font></div><div>Ayden</div><img align="left" width="0" height="0" style="border:0; width:0px; height:0px;" src="https://app.mixmax.com/api/track/v2/hzbgKWNfBGf5urBIl/i02bj5SZulGblRmclZGQu5WYjlmI/icmcv5ibuF2YpB0Z31CckBXLzRmct82cudmI/?sc=false" alt="">
<!--[if mso]></td></tr></table><![endif]-->
</td>
</tr>
</table>
<div>
<div>
<p data-m-apply-default-font="true"><br></p>
<div class="gmail_extra">
<p data-m-apply-default-font="true"><br></p>
<div class="gmail_quote">
On Fri, Jul 1, 2016 5:52 AM, Mark Svancarek via gnso-rds-pdp-wg <span dir="ltr"> <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div>
<div>
<div style="font-family:Calibri,sans-serif; font-size:11pt">That's why I'd be concerned 😃<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir="ltr">
<hr>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">From:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:rrasmussen@infoblox.com">Rod Rasmussen</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Sent:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt">7/1/2016 6:27 AM</span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">To:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:marksv@microsoft.com">Mark Svancarek</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Cc:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:ajs@anvilwalrusden.com">Andrew Sullivan</a>;
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Subject:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt">Re: [gnso-rds-pdp-wg] Five models of RDS (was Re: Apologies, and some reflections on requirements)</span><br>
<br>
</div>
</div>
<font size="2" style="font-size: 1em;"><span style="font-size:10pt;">
<div>ICANN doend’t “run” most of the things coming under it’s remit or in the ecosystem it’s policies guide. Any sort of RDS system regardless of model would likely fall into this category as well. I thinks a few of the large registries
run 5 9 operations for example…<br>
<br>
> On Jun 30, 2016, at 11:15 PM, Mark Svancarek via gnso-rds-pdp-wg <gnso-rds-pdp-wg@icann.org> wrote:<br>
> <br>
> <br>
> That's why I mentioned my concern about ICANN SLA. I don't think they are ready to run a 99.999% online service.<br>
> <br>
> Sorry for the confusion.<br>
<br>
</div>
</span></font>
</blockquote>
</div>
</div>
</div>
</div>
<br><br><div>Ayden Férdeline</div><div><a href="https://community.icann.org/display/gnsosoi/Ayden+Férdeline+SOI" style="background-color: white;">Statement of Interest</a></div>
</body>
</html>