<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I agree with Eric's closing statement: "<span style="font-size:12.8px;font-family:arial,sans-serif">If I may, I suggest replacing sweeping language with specific language, or less non-specific language."</span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-size:12.8px;font-family:arial,sans-serif"><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-size:12.8px;font-family:arial,sans-serif">The "nits" that Eric picks show the problem with using the term "regulation," since much of what ICANN does can be deemed "regulation," depending on how you (reasonably) define it.</span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-size:12.8px;font-family:arial,sans-serif"><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-size:12.8px;font-family:arial,sans-serif">I have no problem with trying to "appease" ISPs, as long as it doesn't have negative consequences to ICANN's mission.</span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-size:12.8px;font-family:arial,sans-serif"><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-size:12.8px;font-family:arial,sans-serif">(I do have big problems with calling any of what we're trying to do "appeasement." This is multistakeholder give-and-take, and in a sense everyone's looking for "appeasement," which is just a nasty way of saying that an outcome has been achieved that meets the concerns of stakeholder group(s).)</span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-size:12.8px;font-family:arial,sans-serif"><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-size:12.8px;font-family:arial,sans-serif">Greg</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 6, 2015 at 5:09 PM, Eric Brunner-Williams <span dir="ltr"><<a href="mailto:ebw@abenaki.wabanaki.net" target="_blank">ebw@abenaki.wabanaki.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Becky,<br>
<br>
As a preamble, I want to mention that content, whatever sluices
between edge nodes (users at their computers, or watches) and
clusters of ad revenue sharing content delivery engines, is not
our policing problem. The resolutions of names to addresses, is
however. <br>
<br>
If I may, I'd like to pick a nit. You wrote: "no authority to
regulate ISPs, or to use its authority over registries and
registrars to do so indirectly."<br>
<br>
First, could we narrow what it is we're not regulating, ISPs do a
lot of things, but one thing they can do is operate recursive
resolvers, so in particular, the "no authority to regulate" means
no means to ensure continuous correct resolution of domain names
by ISPs.<br>
<br>
More generally, it means that any protocol designed to provide
end-to-end semantics, such as digital signature or cookie policy
(something I worked on in the W3C's P3P work early this century)
guarantees of continuous, correctness can be exploited as a
business model, and those business models that falsify DNS lookups
have no liabilities, no costs, for doing so. Another means of
describing such a system is one with "a man or woman in the
middle", generally not a helpful man or woman. More of a
pickpocket or cutpurse.<br>
<br>
Next, still nit picking, I want to point out that currently the
provisioning of third-parties with registry and registrar data is
not unconditional. When I ask for access to VGRS's bulk data I
have to fill out more then just a pro forma, when I ask for access
to GoDaddy's bulk data again there are questions to answer and
promises to make. I think just about everyone (contracted parties)
has a TERMS OF USE paragraph in their WHOIS boilerplate.<br>
<br>
So, we currently have ICANN using "its authority over registries
and registrars to do" something limiting third-party access to and
republication of data held by contracted parties, and we have at
least a history, in SSAC032 and its prior work product on
synthetic return.<br>
<br>
Both are obsoleted by the sweeping prohibition language.<br>
<br>
If I may, I suggest replacing sweeping language with specific
language, or less non-specific language.<span class="HOEnZb"><font color="#888888"><br>
<br>
Eric Brunner-Williams<br>
Eugene, Oregon</font></span><div><div class="h5"><br>
<br>
<br>
On 11/6/15 9:30 AM, Burr, Becky wrote:<br>
</div></div></div>
<blockquote type="cite"><div><div class="h5">
<div>
<div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
All: At the risk of causing a riot, I confess that am
getting increasingly concerned that we are confusing
ourselves (and possibly the bylaws) by trying to include and
explain the prohibition on regulation of services that use
the Internet’s unique identifiers or the content that such
services carry or provide. Perhaps we would be better off
relying on a clear Mission statement and enhanced
accountability mechanisms to prevent mission creep? I could
certainly make the argument, based on the proposed mission
statement, that ICANN has no authority to regulate ISPs, or
to use its authority over registries and registrars to do so
indirectly. (Please note, ICANN’s Bylaws currently
authorize ICANN to enter into contracts. See Article XV,
Section 1). </div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
Should we discuss this approach? The report language on
ICANN’s Mission Statement, reflecting the recent changes to
address IAB/IETF concerns, would then read:</div>
<div>
<div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">The Mission of The
Internet Corporation for Assigned Names and Numbers
("ICANN") is to ensure the stable and secure operation
of the Internet's unique identifier systems in the
ways described below. Specifically, ICANN:</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">1. Coordinates the
allocation and assignment of names in the root zone of
the Domain Name System ("DNS"). In this role, ICANN’s
Mission is to coordinate the development and
implementation of policies:</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">•<span style="white-space:pre-wrap">
</span>For which uniform or coordinated resolution is reasonably
necessary to facilitate the openness,
interoperability, resilience, security and/or
stability of the DNS; and</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">•<span style="white-space:pre-wrap">
</span>That are developed through a bottom-up, consensus-based multi-
stakeholder process and designed to ensure the stable
and secure operation of the Internet’s unique names
systems.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">2. Coordinates the
operation and evolution of the DNS root name server
system. In this role, ICANN’s Mission is to [to be
provided by root server operators].</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">3. Coordinates the
allocation and assignment at the top-most</font></div>
<div><font face="Calibri,sans-serif">level of Internet
Protocol ("IP") and Autonomous System ("AS") numbers.
ICANN’s Mission is described in the ASO MoU between
ICANN and RIRs.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">4. Collaborates with
other bodies as appropriate to publish core registries
needed for the functioning of the Internet. In this
role, with respect to protocol ports and parameters,
ICANN's Mission is to provide registration services
and open access for registries in the public domain
requested by Internet protocol development
organizations, such as the Internet Engineering Task
Force.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">ICANN shall act
strictly in accordance with, and only as reasonably
appropriate to achieve its Mission.
<strike><font color="#ff0000">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. 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></strike> </font></div>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<p class="MsoNormal" style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px;margin-top:12pt">
</p>
<p class="MsoNormal" style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px;margin-top:12pt">
<b><span style="font-size:9pt;line-height:115%">J.
Beckwith Burr</span></b><b><span style="font-size:10.0pt;line-height:115%;color:#262626">
</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#3366ff"><br>
</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#008656">Neustar, Inc.</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#068658">
</span></b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d">/</span><b><span style="font-size:9.0pt;line-height:115%;color:#068658">
</span></b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d">Deputy
General Counsel & Chief Privacy Officer<br>
1775 Pennsylvania Avenue NW, Washington D.C. 20006</span><span style="font-size:9.0pt;line-height:115%;color:gray"><br>
</span><b><span style="font-size:9.0pt;line-height:115%;color:#008656">Office:</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d">
</span></b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d"><a href="tel:%2B1.202.533.2932" value="+12025332932" target="_blank">+1.202.533.2932</a>
</span><b><span style="font-size:9.0pt;line-height:115%;color:#008656">Mobile:</span></b><b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d">
</span></b><span style="font-size:9.0pt;line-height:115%;color:#7d7d7d"><a href="tel:%2B1.202.352.6367" value="+12023526367" target="_blank">+1.202.352.6367</a>
<strong><span style="font-family:Arial">/</span></strong></span><span style="font-size:9.0pt;line-height:115%;color:#068658">
</span><a href="http://www.neustar.biz" target="_blank"><b><span style="font-size:9.0pt;line-height:115%;color:#008656">neustar.biz</span></b></a><span style="font-size:9.0pt;line-height:115%;color:gray"><u></u><u></u></span></p>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><span class=""><pre>_______________________________________________
Accountability-Cross-Community mailing list
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</span></blockquote>
<br>
</div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>