I have this concern also. That was the #1 item to consider, per the charter before plowing ahead.<br><br><br><br><br><br><br>-------- Original Message --------<br>On May 10, 2016, 1:16 PM, Andrew Sullivan wrote:<blockquote class="protonmail_quote"><br><html>
<head></head>
<body>
Hi,
<br>
<br> I'm slightly concerned that we are forgetting in this discussion why
<br> we _need_ an RDS in the first place.
<br>
<br> On Tue, May 10, 2016 at 10:59:29AM -0400, Sam Lanfranco wrote:
<br> >
<br> > ICANN has business interests in defining what data to collect, accessible by
<br> > whom and under what conditions. It also has business interests, from within
<br> > its remit, in the data relationship with its contracted parties.
<br> > However, ICANN’s contracted parties reside within national jurisdictions,
<br> > and the relevant data is hosted within national jurisdictions, so ICANN
<br> > cannot unilaterally define what constitutes legitimate data policy within
<br> > its business interests.
<br>
<br> All of the above is something I agree with, but there's another
<br> important point. For good, sound, plain old technical reasons, it's
<br> important that operators be able to contact each other outside of the
<br> Internet, so that when stuff breaks it's at least logically possible
<br> that one could try to fix it.
<br>
<br> The key point is that this is not some peculiar business interest of
<br> ICANN, but instead a fundamental interest of anyone who uses the DNS
<br> (i.e. approximately anyone who uses the Internet). It's basic to why
<br> we have ICANN at all.
<br>
<br> None of this is an argument that _all_ the information in any
<br> particular RDS policy is what ought to be in the RDS. But at the same
<br> time, it seems to me that some views about RDS treat every data field
<br> as if it's a simple matter of political negotiation or something like
<br> that. They're not all that way. As an operator of actual technical
<br> infrastructure, I need to be able to contact someone who is causing
<br> problems on my network, and that ability to contact had better not
<br> depend on the Internet since the problem in question is likely to
<br> result from some sort of interoperation failure in the first place.
<br> Therefore,
<br>
<br> > Some will brand this as the “fracturing of the Internet”. It is in fact
<br> > other jurisdictions taking responsibility for Internet governance outside
<br> > ICANN’s remit, but within their remit.
<br>
<br> I don't think that all of this is just about "Internet governance",
<br> any more than (say) port number allocations are a matter for Internet
<br> governance. Some of it is just a fundamental part of having an
<br> Internet at all. Remember, it's an inter-net because of the network
<br> of networks part. Interoperation is a fundamental part, not something
<br> you get to choose or not from a menu of available policy options.
<br>
<br> Best regards,
<br>
<br> A
<br>
<br> --
<br> Andrew Sullivan
<br> ajs@anvilwalrusden.com
<br> _______________________________________________
<br> gnso-rds-pdp-wg mailing list
<br> gnso-rds-pdp-wg@icann.org
<br> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
</body>
</html></div>