<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">This topic was just discussed extensively on the call yesterday and there was considerable progress. The recordings, notes, chat and call transcripts are all available now at <a href="https://community.icann.org/pages/viewpage.action?pageId=56145283">https://community.icann.org/pages/viewpage.action?pageId=56145283</a>. I've attached the call transcript; the relevant discussion is on pp. 4-19. It's important to read the whole section, but the concluding remarks from that discussion are helpful for us to build on:</div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline"></div></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><span style="line-height:normal">Becky
Burr:</span><span style="line-height:normal"> </span><span style="line-height:normal">Well, no, I mean, I
think that the point is - and Greg has just echoed me in this - what we are
talking about is services, not service providers. So the question is what is
the underlying service, not what is the nature of the business. So I guess I
agree with - I agree with the way it is set up in this language here.<br></span> <br>Thomas
Rickert: Yes, and I guess that what
you’ve just refined is a better description of what Greg I think meant by saying
differing classes of services - class of businesses. So I guess that’s helpful.
So I think we can confirm and please let me know if you do not agree with this,
that that we are looking for a technology-neutral description of
this.<br> <br> But
still if we’re using the technique that Kavouss has suggested, for example, we
could have examples of technology to illustrate what we mean by the definition
that should then go - or by the language that should then go into the bylaws.
Alan, you’ve raised your hand.<br> <br>Alan
Greenberg: Yeah, thank you. It [dawns]
on me that when we're looking at the two classes of service, someone may be
offering a graphics design service over the web. Clearly, we are never saying
we are going to be regulating the graphics design service. So at some level we
could not - we don’t have to differentiate because we’re - the higher level
service is always carved out. But since the word has two different very
distinct meanings it’s probably better to be clear. Thank you.<br> <br><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline"><span style="font-family:arial,sans-serif;line-height:normal">Thomas
Rickert:</span><span style="font-family:arial,sans-serif;line-height:normal"> </span><span style="font-family:arial,sans-serif;line-height:normal">Thanks very much, Alan.
And I think that these are excellent final words on this conversation. So I
think this is as far as we can get during this call. And with that I’d like to
thank you all for your contributions and for bearing with us for those who are
not calling this their favorite item. And let’s now move to the next agenda
item which is going to be chaired by Mathieu.</span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div></blockquote><div class="gmail_extra"><span style="font-family:verdana,sans-serif"><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">Andrew Sullivan had two suggested revisions to the first part of the provision</div><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">, both of which are consistent with this direction:</div></span></div><div class="gmail_extra"><ul><li><span style="font-size:12.8px"><b><font color="#0000ff"><font face="arial, helvetica, sans-serif"><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline"></div><div class="gmail_default" style="display:inline">ICANN</div><div class="gmail_default" style="display:inline"> shall not impose regulations on </div><div class="gmail_default" style="display:inline"></div>services (i.e., any software process that accepts<div class="gmail_default" style="display:inline"> </div></font></font></b></span><b><font color="#0000ff" face="arial, helvetica, sans-serif"><span style="font-size:12.8px">connections from the Internet) that use the Internet’s unique<div class="gmail_default" style="display:inline"> </div></span><span class="im" style="font-size:12.8px"><font color="#0000ff">identifiers, or<div class="gmail_default" style="display:inline"> the content that such services carry or provide</div></font></span></font></b><br></li></ul></div><div class="gmail_extra"><span style="font-family:verdana,sans-serif;color:rgb(80,0,80);font-size:12.8px"></span><span style="font-family:verdana,sans-serif;font-size:12.8px"><font color="#000000">or, alternatively</font></span><br></div><div class="gmail_extra"><ul><li><b><font face="arial, helvetica, sans-serif"><span style="font-size:12.8px"><font color="#0000ff"><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline"><b style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px"><font color="#0000ff"><font face="arial, helvetica, sans-serif"><div class="gmail_default" style="display:inline">ICANN</div><div class="gmail_default" style="display:inline"> shall not impose regulations on </div><div class="gmail_default" style="display:inline"></div></font></font></b></div>services (i.e., any software process that accepts datagrams from </font></span><font color="#0000ff"><span style="font-size:12.8px">the Internet, when those datagrams are not themselves necessarily </span><span style="font-size:12.8px">the consequence of a datagram previously sent by the software </span><span style="font-size:12.8px">process itself) that use the Internet’s unique identifiers</span><span style="font-size:12.8px">, or</span><div class="gmail_default" style="font-size:12.8px;display:inline"> the content that such services carry or provide</div></font></font></b><br></li></ul></div><div class="gmail_extra"><span class="im" style="font-size:12.8px"><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline"></div></span><font face="verdana, sans-serif">These parentheticals are both more "technically neutral" than the parenthetical I circulated ("(i.e., the software processes by which commands received via the Internet are processed and a response is generated and transmitted via the Internet, to be viewed in a web browser, email client, or the like")). I tend to prefer the first one, which has the virtue of brevity. That said, we should see if there are tweaks consistent with Thomas's summary of the call "</font>we’re not talking about the service providers or the class of business that they're in but that we're talking about the technical processes, the technical services.<span style="font-family:verdana,sans-serif">"</span></div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_default" style="font-family:verdana,sans-serif">Another suggestion came from Milton Mueller:</div><div class="gmail_default"><ul><li><b style="color:rgb(0,0,255);font-family:arial,helvetica,sans-serif"><b style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px"><font color="#0000ff"><font face="arial, helvetica, sans-serif"><div class="gmail_default" style="display:inline">ICANN</div><div class="gmail_default" style="display:inline"> shall not impose regulations on </div><div class="gmail_default" style="display:inline"></div></font></font></b>Information services which use the Internet’s unique identifiers but are not registries or registrars, or<div class="gmail_default" style="display:inline"> </div><div class="gmail_default" style="display:inline">t</div>he content that such services carry or provide</b><br></li></ul></div><div class="gmail_default" style="font-family:verdana,sans-serif">In response to James Bladel, Milton suggests "<span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6667px">Instead of saying “registries or registrars” we could simply say “under the Registrar Accreditation Agreement (RAA) or the Registry Agreement (RA).”</span></div></div><div class="gmail_extra"><div class="gmail_default"><ul><li><font face="arial, helvetica, sans-serif"><b><font color="#0000ff"><b style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px"><font color="#0000ff"><font face="arial, helvetica, sans-serif"><div class="gmail_default" style="display:inline">ICANN</div><div class="gmail_default" style="display:inline"> shall not impose regulations on </div><div class="gmail_default" style="display:inline"></div></font></font></b>Information services which use the Internet’s unique identifiers but are not under</font><font color="#0000ff"> the Registrar Accreditation Agreement (RAA) or the Registry Agreement (RA)</font><font color="#0000ff">, or</font><div class="gmail_default" style="color:rgb(0,0,255);display:inline"> </div><div class="gmail_default" style="color:rgb(0,0,255);display:inline">t</div><font color="#0000ff">he content that such services carry or provide</font></b></font><br></li></ul></div><div class="gmail_default" style="font-family:verdana,sans-serif">Although "information services" could be preferable to "services," the first suggestion clearly takes us away from describing "technical processes" and instead describes "service providers" since it refers to "registries or registrars" as the kind of thing that would be included as "information services" (unless carved out). The second suggestion is not as clearly about "service providers" but it's also not clearly about "technical services" either (there's not enough information to read it clearly). </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Perhaps there's a way to combine these various thoughts in a manner consistent with the overall direction, for instance in the following synthesis:</div><div class="gmail_default"><ul><li><font face="verdana, sans-serif"></font><font face="arial, helvetica, sans-serif" color="#0b5394"><b><b style="font-size:12.8px"><font><div class="gmail_default" style="display:inline">ICANN</div><div class="gmail_default" style="display:inline"> shall not impose regulations on:</div></font></b></b></font></li><ul><li><font face="arial, helvetica, sans-serif" color="#0b5394"><b><b style="font-size:12.8px"><font><div class="gmail_default" style="display:inline"></div></font></b>Information services <span style="font-weight:normal;font-size:12.8px"><b>(i.e., any software process that accepts<div class="gmail_default" style="display:inline"> </div></b></span><b><span style="font-size:12.8px">connections from the Internet) that</span></b> use the Internet’s unique identifiers, other than those covered by the Registrar Accreditation Agreement (RAA) or </b></font><b style="color:rgb(11,83,148);font-family:arial,helvetica,sans-serif">the Registry Agreement (RA), or<div class="gmail_default" style="display:inline"> </div></b></li><li><b style="color:rgb(11,83,148);font-family:arial,helvetica,sans-serif"><div class="gmail_default" style="display:inline"></div><div class="gmail_default" style="display:inline">t</div>he content that such information services carry or provide</b><span style="color:rgb(11,83,148);font-family:arial,helvetica,sans-serif"></span></li></ul></ul></div><div class="gmail_default" style="font-family:verdana,sans-serif">or, alternatively (if the carve-out for the RAA/RA seems confusing, unnecessary or overbroad) </div></div><div class="gmail_default"><ul><li><font face="verdana, sans-serif"></font><font face="arial, helvetica, sans-serif" color="#0b5394"><b><b style="font-size:12.8px"><div class="gmail_default" style="display:inline">ICANN</div><div class="gmail_default" style="display:inline"> shall not impose regulations on:</div></b></b></font></li><ul><li><font face="arial, helvetica, sans-serif" color="#0b5394"><b><b style="font-size:12.8px"><div class="gmail_default" style="display:inline"></div></b>Information services <span style="font-weight:normal;font-size:12.8px"><b>(i.e., any software process that accepts<div class="gmail_default" style="display:inline"> </div></b></span><b><span style="font-size:12.8px">connections from the Internet) that</span></b> use the Internet’s unique identifiers, </b></font><b style="color:rgb(11,83,148);font-family:arial,helvetica,sans-serif"> or<div class="gmail_default" style="display:inline"> </div></b></li><li><b style="color:rgb(11,83,148);font-family:arial,helvetica,sans-serif"><div class="gmail_default" style="display:inline"></div><div class="gmail_default" style="display:inline">t</div>he content that such information services carry or provide</b><span style="color:rgb(11,83,148);font-family:arial,helvetica,sans-serif"></span></li></ul></ul></div><div class="gmail_extra"><span style="font-family:verdana,sans-serif"><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">In order to focus this email, I haven't touched on the second sentence, which we should finalize as well.</div></span></div><div class="gmail_extra"><span style="font-family:verdana,sans-serif"><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline"><br></div></span></div><div class="gmail_extra"><span style="font-family:verdana,sans-serif"><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">I look forward to your thoughts.</div></span></div><div class="gmail_extra"><span style="font-family:verdana,sans-serif"><br></span></div><div class="gmail_extra"><span style="font-family:verdana,sans-serif"><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">Greg</div><br></span></div><div class="gmail_extra"><span style="font-family:verdana,sans-serif"> </span><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">On Fri, Nov 13, 2015 at 11:44 AM, Mueller, Milton L <span dir="ltr"><<a href="mailto:milton@gatech.edu" target="_blank">milton@gatech.edu</a>></span> wrote:<br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">James:
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Understand your concern. I think we can easily fix this.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Instead of saying “registries or registrars” we could simply say “under the Registrar Accreditation Agreement (RAA) or the Registry Agreement (RA).”
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Vertical integration between registries and registrars does not alter the fact that they are still contracted parties under either RAA or RA or both, and by specifying
the RAA and RA we make it very clear which aspects of the business are “regulated” and which are not.<u></u><u></u></span></p>
<p class="MsoNormal"><a name="151080d3e2b38378_151070cfb002ad27_15106e19427de347_1510333a3000e0fd_1510300e9af95771_15101bd67b28395b__MailEndCompose"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></a></p>
<div style="border-style:none none none solid;border-left-color:blue;border-left-width:1.5pt;padding:0in 0in 0in 4pt">
<div>
<div style="border-style:solid none none;border-top-color:rgb(225,225,225);border-top-width:1pt;padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> James M. Bladel [mailto:<a href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a>]
<br>
<b>Sent:</b> Friday, November 13, 2015 11:22 AM<br>
<b>To:</b> Silver, Bradley <<a href="mailto:Bradley.Silver@timewarner.com" target="_blank">Bradley.Silver@timewarner.com</a>>; Edward Morris <<a href="mailto:egmorris1@toast.net" target="_blank">egmorris1@toast.net</a>>; Mueller, Milton L <<a href="mailto:milton@gatech.edu" target="_blank">milton@gatech.edu</a>></span></p><div><div><br>
<b>Cc:</b> Accountability Cross Community <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><br>
<b>Subject:</b> Re: [CCWG-ACCT] Attempt to summarize discussion regarding Mission and Contract<u></u><u></u></div></div><p></p>
</div>
</div><div><div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black">Like many, I have completely lost track of this thread, particularly since many messages are arriving out-of-sequence. Not sure if this this the best place to
jump in, but here goes: I do not support the inclusion of the terms “Registries” or “Registrars” in to ICANN’s mission or bylaws.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black">We are entering a new era of vertical integration between & among a wide variety of service providers. Some of these commercial activities are subject to ICANN
governance, others are not. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black">We have a hard enough time defining these terms in our own Stakeholder Group Charter(s), so I don’t recommend transplanting that mess here.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black">Thanks—<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black">J.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div style="border-style:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black">From:
</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:black"><<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>> on behalf of "Silver, Bradley" <<a href="mailto:Bradley.Silver@timewarner.com" target="_blank">Bradley.Silver@timewarner.com</a>><br>
<b>Date: </b>Friday, November 13, 2015 at 7:46 <br>
<b>To: </b>Edward Morris <<a href="mailto:egmorris1@toast.net" target="_blank">egmorris1@toast.net</a>>, "Mueller, Milton L" <<a href="mailto:milton@gatech.edu" target="_blank">milton@gatech.edu</a>><br>
<b>Cc: </b>Accountability Cross Community <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><br>
<b>Subject: </b>Re: [CCWG-ACCT] Attempt to summarize discussion regarding Mission and Contract<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black"><u></u> <u></u></span></p>
</div>
</div></div><div>
<div><div><div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Thanks Milton and Ed -
</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Doesn’t calling our registries and registrars get us back into the problem area of whether activities such as the accreditation of Privacy & Proxy services is
in breach of the no-regulation clause? I had thought the goal of the draft Greg circulated was to describe the specific processes that ICANN would stay clear of imposing regulation on (the distinction being that “services” is not meant to describe entities,
but rather a certain type of activity). </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Also, the change the second bullet does not provide the clarity that is needed – it essentially makes it a narrower way saying what the first sentence says.
The point of the contractual language was to clarify that the first bullet would not impede ICANN’s furtherance of its mission via contractual agreements. I think flipping it around doesn’t give the necessary guidance and clarity.
</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">These are important distinctions, but I think a good step towards finding agreement on language that could satisfy broad interests.
</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Bradley
</span></b><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
<div>
<div style="border-style:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif;color:black">
<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a> [<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">mailto:accountability-cross-community-bounces@icann.org</a>]
<b>On Behalf Of </b>Edward Morris<br>
<b>Sent:</b> Friday, November 13, 2015 6:24 AM<br>
<b>To:</b> Mueller, Milton L<br>
<b>Cc:</b> Accountability Cross Community<br>
<b>Subject:</b> Re: [CCWG-ACCT] Attempt to summarize discussion regarding Mission and Contract</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="color:black">+1<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">The revised language is a bit clearer and based more on general principle than on specific technology. We're building a governing construct for the future ICANN regardless of where technology takes us. Milton's
proposed language better allows us to carry these general principles forward regardless of any changes to base technology that ICANN might encounter or need to adapt to. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><span style="color:black">Ed<br>
<br>
<br>
<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><span style="color:black"><br>
On Nov 13, 2015, at 2:45 AM, Mueller, Milton L <<a href="mailto:milton@gatech.edu" target="_blank">milton@gatech.edu</a>> wrote:<u></u><u></u></span></p>
</div>
</div></div><blockquote style="margin-top:5pt;margin-bottom:5pt">
<div><div><div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Greg:</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I think with some modifications to your proposed text we can find widespread agreement. Here is how I would modify your proposal:</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span style="color:black"><u></u><u></u></span></p>
</div></div><div style="border-style:none none none solid;border-left-color:blue;border-left-width:1.5pt;padding:0in 0in 0in 4pt">
<div>
<div><div><div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:black">ICANN shall act strictly in accordance with, and only as reasonably appropriate to</span><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:rgb(31,73,125)">,</span><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:black">
achieve its Mission. Without limiting the foregoing:</span><span style="color:black"><u></u><u></u></span></p>
</div></div><p class="MsoNormal" style="margin-left:0.5in">
<u></u><span style="font-size:10pt;font-family:Symbol;color:black"><span>?<span style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span></span><u></u><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:black">ICANN shall not impose regulations on:</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:1in">
<u></u><span style="font-size:10pt;font-family:'Courier New';color:black"><span>o<span style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span></span><u></u><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:rgb(31,73,125)">Information
</span><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:black">services which use the Internet’s unique identifiers</span><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:rgb(31,73,125)"> but are not registries or registrars</span><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:black">,
or</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:1in">
<u></u><span style="font-size:10pt;font-family:'Courier New';color:black"><span>o<span style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span></span><u></u><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:rgb(31,73,125)">T</span><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:black">he content that such services carry or provide</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><span style="font-size:10pt;font-family:Symbol;color:black"><span>?<span style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:'Times New Roman'">
</span></span></span><u></u><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:black">ICANN shall have the ability to enter into and enforce agreements with contracted parties,
</span><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:rgb(31,73,125)">insofar as those agreements are consistent with
</span><span style="font-size:13.5pt;font-family:Tahoma,sans-serif;color:black">its Mission. </span><span style="color:black"><u></u><u></u></span></p><span>
<p class="MsoNormal" style="background-image:initial;background-repeat:initial">
<span style="font-family:Calibri,sans-serif;color:rgb(31,73,125)">Explanation:</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Calibri,sans-serif;color:rgb(31,73,125)">“information services” is a simpler and more generic way to describe what we you are referring to and has a long regulatory history. As others
noted before, it is dangerous to try to get too technologically specific. What we need to do here is carve out an exception to the regulation band for registries and registrars, which ICANN can and does regulate in accord with its mission.</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Calibri,sans-serif;color:rgb(31,73,125)">The second point, pertaining to enforcing contracts, puts in clearer and more restrictive language. Rather than “in furtherance of’ its mission
I proposed “consistent with” its mission. One might claim that many ancillary activities might “further” ICANN’s mission in some way; it is more precise to ask that ICANN’s activities be “consistent” with its mission.
</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">--MM</span><span style="color:black"><u></u><u></u></span></p>
</span></div>
</div><span>
<div>
<p class="MsoNormal" style="background-image:initial;background-repeat:initial"><span style="color:black"> <u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="color:black">On Thu, Nov 12, 2015 at 3:24 PM, Burr, Becky <<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>> wrote:<u></u><u></u></span></p>
<blockquote style="border-style:none none none solid;border-left-color:rgb(204,204,204);border-left-width:1pt;padding:0in 0in 0in 6pt;margin:5pt 0in 5pt 4.8pt">
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black">I share Keith’s confusion. Just where are we?</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</span></div>
</div>
</blockquote><span>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div>
<p class="MsoNormal"><span style="color:black">_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><u></u><u></u></span></p>
</div>
</blockquote>
<p><span style="color:black">=================================================================<br>
</span><b><i><span style="color:red">Reminder: Any email that requests your login credentials or that asks you to click on a link could be a phishing attack. If you have any questions regarding the authenticity of this email or its sender, please contact the
IT Service Desk at <a href="tel:212.484.6000" value="+12124846000" target="_blank">212.484.6000</a> or via email at <a href="mailto:ITServices@timewarner.com" target="_blank">
ITServices@timewarner.com</a> </span></i></b><span style="color:black"><u></u><u></u></span></p>
<p><span style="color:black"><br>
=================================================================<u></u><u></u></span></p>
<p><span style="color:black">=================================================================<br>
This message is the property of Time Warner Inc. and is intended only for the use of the<br>
addressee(s) and may be legally privileged and/or confidential. If the reader of this message<br>
is not the intended recipient, or the employee or agent responsible to deliver it to the intended<br>
recipient, he or she is hereby notified that any dissemination, distribution, printing, forwarding,<br>
or any method of copying of this information, and/or the taking of any action in reliance on<br>
the information herein is strictly prohibited except by the intended recipient or those to whom<br>
he or she intentionally distributes this message. If you have received this communication in<br>
error, please immediately notify the sender, and delete the original message and any copies<br>
from your computer or storage system. Thank you.<br>
=================================================================<u></u><u></u></span></p>
</span></div>
</div>
</div>
</div>
</div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">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></div>