<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Becky,<br>
<br>
"shall not regulate services that use the Internet's unique
identifiers" -- had this language been in place a decade ago how
could the corporation have addressed the wildcard problem? Who
would be the regulator(s) of monitized synthetic returns? These
are things that actually broke the net, and an appeal to Vixie's
patch seems ... well ... to court risk of repetition.<br>
<br>
Where do we go in the future when VGRS initiates another
disruptive service unforeseen in contract? When the Egyptian
government next withdraws all prefixes can we keep the last
authoritative nameserver for Egypt running after its data expires?<br>
<br>
Also, assuming for the moment that ICANN currently exercises
delegated rule making authority, if ICANN explicitly abandons this
authority, does that authority revert to the delegating agency?<br>
<br>
If I may, to regulate, or not regulate, stub-, recursive- and
authoritative-resolvers and their resolutions via port 53 of
delegated name spaces to allocated address spaces, is more
on-point, and vastly narrower, than "services that use ..."<br>
<br>
Eric<br>
<br>
On 10/30/15 6:19 AM, Burr, Becky wrote:<br>
</div>
<blockquote cite="mid:D258E681.C0D0%25becky.burr@neustar.biz"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">In Dublin we discussed, both in
our working meetings and over two brown bag lunches, an approach
to addressing concerns about the Mission Statement prohibition
on regulation of services that use the Internet’s unique
identifiers, or the content that such services carry or provide.
The following language (in blue) is proposed to address this
concern: </div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div><span style="font-style: italic;">ICANN shall have no power
to act other than in accordance with, and as reasonably
appropriate to achieve its Mission. Without in any way
limiting the foregoing absolute prohibition, ICANN shall not
regulate services that use the Internet's unique identifiers,
or the content that such services carry or provide. I<font
color="#0000ff">n service of its Mission, ICANN shall have
the ability to enforce agreements with contracted parties,
subject to established means of community input on those
agreements and reasonable checks and balances on its ability
to impose obligations exceeding ICANN’s Mission on
registries and registrars.</font></span></div>
<div style="color: rgb(0, 0, 0);"><span style="font-style:
italic;"><br>
</span></div>
<div style="color: rgb(0, 0, 0);">What we discussed (over the
lunches) as a reasonable check and balance (in addition to
existing mechanisms such as public comment, etc.) is a new
mechanism whereby registries and registrars are permitted to
sign RAs and RAAs subject to a public reservation that they
intend to challenge one or more specified provisions of such
agreements on the grounds that the provision(s) would exceed the
scope of ICANN’s Mission. This mechanism will need to be
developed. </div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">
<div>J. Beckwith Burr</div>
<div>Deputy General Counsel & Chief Privacy Officer</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
</body>
</html>