<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>I am good with Malcolm’s language</div>
<div><br>
</div>
<div>
<div>J. Beckwith Burr</div>
<div>Deputy General Counsel & Chief Privacy Officer</div>
<div><br>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, November 4, 2015 at 5:47 PM<br>
<span style="font-weight:bold">To: </span>Malcolm Hutty <<a href="mailto:malcolm@linx.net">malcolm@linx.net</a>><br>
<span style="font-weight:bold">Cc: </span>Becky Burr <<a href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a>>, Steven Metalitz <<a href="mailto:met@msk.com">met@msk.com</a>>, "Silver, Bradley" <<a href="mailto:Bradley.Silver@timewarner.com">Bradley.Silver@timewarner.com</a>>,
Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>>, Accountability Community <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CCWG-ACCT] WP2 Issues from last night's call<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div class="gmail_default" style="font-family:verdana,sans-serif">Malcolm,</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">Thank you for this. I think it is a leap forward. I appreciate the effort and the spirit in which it is offered I still have to take more than a moment with it, but I think we are moving in
the right direction, at least as regards our concerns. </div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">
<div class="gmail_default">I still have an issue with the phrase "service that uses the Internet's unique identifiers." I've looked at this phrase a hundred times, and I would not have come up with the idea that it is limited to <b><u>hardware</u> </b>(which
are things, not services...). I think I'm far from alone in that. Also, the way you look at the clause "using the Internet's unique identifiers" is also not one that I would have taken away from this language. Registries and registrars clearly are services
that use the Internet's unique identifiers; so does every other service business that uses the internet.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">Maybe as an IXP this has the meaning you think it has. But we need language that is agnostic of such distinctions, especially in a corporate bylaw. I spend much of my day looking at language at the intersection of law and technology,
so I should be a good audience for something like this. As such I think the "misreading" is inherent in the language and not in the reader.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">To capture the meaning you attribute to the phrase in question, I would suggest the following:</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">"[microprocessor controlled] technologies that use the Internet's unique identifiers to access the Internet"</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">In this way, we have more explicitly limited the "service" as you suggest, and also limited the "use" as you suggest. And we avoid the ambiguity of the word "services," which clearly means very different things to different people.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">I look forward to your thoughts and those of others persevering on this thread.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">Greg</div>
<div><br>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Nov 4, 2015 at 5:29 PM, Malcolm Hutty <span dir="ltr">
<<a href="mailto:malcolm@linx.net" target="_blank">malcolm@linx.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
<br>
On 04/11/2015 22:06, Greg Shatan wrote:<br>
> Becky and all,<br>
><br>
> I have attached a revision to the proposed Bylaw under discussion,<br>
> taking the comments from various quarters into account and trying to<br>
> balance various concerns.<br>
><br>
> Greg<br>
<br>
</span>Thank you Greg. I think "strictly" should remain; the intent is indeed<br>
to ensure that ICANN remains within the Mission, and who is to say what<br>
kind of mission creep is "harmless".<br>
<br>
Your text also helpfully points out the unhelpfully vague nature of the<br>
phrase "as reasonably appropriate" in the first sentence. Let's delete it.<br>
<br>
I can agree with the inclusion of "negotiate and enter into", provided<br>
that this is also within the Mission.<br>
<br>
Attached is my suggestion for how we incorporate that phrase.<br>
<br>
The attached text is much simpler and more clear than anything we have<br>
had so far. If it is used, I think you will agree that there can be no<br>
suggestion nor any reasonable fear that ICANN's legitimate contracting<br>
authority is being brought into question.<br>
<br>
Can we settle on this?<br>
<div class="HOEnZb">
<div class="h5"><br>
Malcolm.<br>
<br>
--<br>
Malcolm Hutty | tel: <a href="tel:%2B44%2020%207645%203523" value="+442076453523">
+44 20 7645 3523</a><br>
Head of Public Affairs | Read the LINX Public Affairs blog<br>
London Internet Exchange | <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__publicaffairs.linx.net_&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=NYdcU7h7Yqe0Ei3DaPlgBGmq30kwdQEwySnogN1V-HQ&s=f_sjwRhW76BY1TN4m5cdxATV_IO0pZ5QWOiyQKMrYeI&e=" rel="noreferrer" target="_blank">
http://publicaffairs.linx.net/</a><br>
<br>
London Internet Exchange Ltd<br>
Monument Place, 24 Monument Street, London EC3R 8AJ<br>
<br>
Company Registered in England No. 3137929<br>
Trinity Court, Trinity Street, Peterborough PE1 1DA<br>
<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>