<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>Maybe we should include a reference to the Consensus and Temporary Policies Specification. Remember, this is not Bylaws language, rather it is instruction to drafting lawyers.</div>
<div><br>
</div>
<div>
<div><br>
</div>
<div>J. Beckwith Burr</div>
<div>Deputy General Counsel & Chief Privacy Officer</div>
<div><br>
</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><Metalitz>, Steven Metalitz <<a href="mailto:met@msk.com">met@msk.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, November 4, 2015 at 4:36 PM<br>
<span style="font-weight:bold">To: </span>Becky Burr <<a href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a>>, "Silver, Bradley" <<a href="mailto:Bradley.Silver@timewarner.com">Bradley.Silver@timewarner.com</a>>, 'Malcolm Hutty' <<a href="mailto:malcolm@linx.net">malcolm@linx.net</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 xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Avenir Book";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1205486138;
mso-list-type:hybrid;
mso-list-template-ids:-819805472 -2129757206 1457916568 -417543508 -1574263620 936421106 -60235356 -440504350 -1960930030 1485750312;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:?;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">The argument is serious because the proposal is to amend the Mission to exclude “regulation of services that use unique identifiers.” This brings
me back to the question whether domain name registration is such a service, and then Bradley’s question whether registrar accreditation is a regulation of that service. There certainly seems to be a serious argument that the answer to each question is “yes,”
and if so, then this change to ICANN’s mission would bring into serious question ICANN’s authority to continue registrar accreditation --- without regard to the fact that, under a Mission statement that always lacked the ban on “regulation of services,” ICANN
has “always accredited.” <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> Burr, Becky [<a href="mailto:Becky.Burr@neustar.biz">mailto:Becky.Burr@neustar.biz</a>]
<br>
<b>Sent:</b> Wednesday, November 04, 2015 4:26 PM<br>
<b>To:</b> Silver, Bradley; Metalitz, Steven; 'Malcolm Hutty'; Alan Greenberg; Accountability Community<br>
<b>Subject:</b> Re: [CCWG-ACCT] WP2 Issues from last night's call<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">This argument doesn’t make a lot of sense to me. ICANN has always accredited – both registries and registrars. Is there a serious argument to be had that
this is outside the Mission?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">J. Beckwith Burr<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Deputy General Counsel & Chief Privacy Officer<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 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;"><Silver>, Bradley <<a href="mailto:Bradley.Silver@timewarner.com">Bradley.Silver@timewarner.com</a>><br>
<b>Date: </b>Wednesday, November 4, 2015 at 4:20 PM<br>
<b>To: </b>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>>, 'Malcolm Hutty' <<a href="mailto:malcolm@linx.net">malcolm@linx.net</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>
<b>Subject: </b>RE: [CCWG-ACCT] WP2 Issues from last night's call<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Thank you for pointing that out, Becky. Do you think it’s clear that the role of “coordinator” of the allocation and assignment of names in the
root zone of the DNS, unequivocally covers the activity of accreditation of services that use the internet’s unique identifiers? Even with the added language covering enforcement of contracts, I think there is significant potential for confusion about how
to reconcile what ICANN is empowered to do on the one hand (coordinate), but forbidden from doing on the other (regulate). The plain meaning of “regulate” seems to clearly cover (and therefore prohibit) the activity of accreditation – even when read alongside
the earlier reference to ICANN’s function as “coordinator”. Some might argue that ICANN can and should fulfill its mission as coordinator without engaging in activities that amount to “regulation”- including accreditation, but possibly other oversight activities
that could be understood as exceeding its powers of coordination. </span><span style="color:black"><o:p></o:p></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"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 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;"> Burr, Becky [<a href="mailto:Becky.Burr@neustar.biz">mailto:Becky.Burr@neustar.biz</a>]
<br>
<b>Sent:</b> Wednesday, November 04, 2015 3:46 PM<br>
<b>To:</b> Silver, Bradley; Metalitz, Steven; 'Malcolm Hutty'; Alan Greenberg; Accountability Community<br>
<b>Subject:</b> Re: [CCWG-ACCT] WP2 Issues from last night's call</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Taking off Andrew and the IAB folks as this is not their issue</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">W As part of this process we have captured and imported the essence of the "picket fence” - the “what” (as opposed to the “how”)
of Consensus Policy (Section 1.2 of the Consensus and Temporary Policies spec) into ICANN's Mission statement for names (ICANN’s Mission for names covers </span><span style="font-family: Cambria, serif; color: black;">issues for which uniform or coordinated
resolution is reasonably necessary to facilitate </span><span style="font-family: 'Avenir Book'; color: black;">openness, interoperability, resilience, security and/or stability of the DNS). That means that issues that fall into the so-called </span><span style="font-size: 11.5pt; font-family: 'Avenir Book'; color: black;">“</span><span style="font-family: 'Avenir Book'; color: black;">picket
fence” are within ICANN’s Mission. That has been functionally true via the registry and registrar agreements since the beginning of ICANN time. We have just made this a bylaw fact. Section 1.3 of the Spec gives examples </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-family: 'Avenir Book'; color: black;">Se</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-family: 'Avenir Book'; color: black;">S</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">J. Beckwith Burr</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Deputy General Counsel & Chief Privacy Officer</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 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;"><Silver>, Bradley <<a href="mailto:Bradley.Silver@timewarner.com">Bradley.Silver@timewarner.com</a>><br>
<b>Date: </b>Wednesday, November 4, 2015 at 12:02 PM<br>
<b>To: </b>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>>, 'Malcolm Hutty' <<a href="mailto:malcolm@linx.net">malcolm@linx.net</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>>, Andrew Sullivan <<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>>, "<a href="mailto:iab@iab.org">iab@iab.org</a>"
<<a href="mailto:iab@iab.org">iab@iab.org</a>><br>
<b>Subject: </b>RE: [CCWG-ACCT] WP2 Issues from last night's call</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Becky and all – I’m new to this thread but have been following this issue for some time. I’m still confused as to how Spec 1 clarifies the “regulation”
language. If spec 1 says ICANN can do something by way of consensus policy making, does that trump what the bylaws say ICANN can do? Bylaws trump, don’t they? </span><span style="color:black"><o:p></o:p></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"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Bradley Silver<br>
Chief Intellectual PropertyCounsel |Time Warner Inc. </span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">One Time Warner Center New York, NY 10019-8016
<b>|</b> P: 212 484 8869 <b>|</b> F: 212 658 9293</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><img border="0" width="283" height="28" id="Picture_x0020_1" src="cid:image001.png@01D1171E.B043DBF0" alt="cid:image004.png@01D11648.738D46F0"></span><span style="color:black"><o:p></o:p></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"><o:p></o:p></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"><o:p></o:p></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"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 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">accountability-cross-community-bounces@icann.org</a>
[<a href="mailto:accountability-cross-community-bounces@icann.org">mailto:accountability-cross-community-bounces@icann.org</a>]
<b>On Behalf Of </b>Burr, Becky<br>
<b>Sent:</b> Wednesday, November 04, 2015 11:33 AM<br>
<b>To:</b> Metalitz, Steven; 'Malcolm Hutty'; Alan Greenberg; Accountability Community; Andrew Sullivan;
<a href="mailto:iab@iab.org">iab@iab.org</a><br>
<b>Subject:</b> Re: [CCWG-ACCT] WP2 Issues from last night's call</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<div>
<div>
<h3 style="margin:0in;margin-bottom:.0001pt;background:white"><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">For some reason the Consensus/Temporary Policy Spec is Spec 4 in the RAA. Note that Section 1.2 outlines the topics that
are fair game for consensus policies, which includes “resolution of disputes regarding the registration of domain names (as opposed to the use of such domain names, but including where such policies take into account use of the domain names) Section 1.3 gives
specific <i>examples (without limitation)</i>, including </span><span style="font-size: 10.5pt; font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">"reservation of registered names in a </span><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">TLD</span><span style="font-size: 10.5pt; font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);"> that
may not be registered initially or that may not be renewed due to reasons reasonably related to (i) avoidance of confusion among or misleading of users, (ii) intellectual property, or (iii) the technical management of the </span><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">DNS</span><span style="font-size: 10.5pt; font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);"> or
the Internet (e.g., establishment of reservations of names from registration)"</span><span style="color:black"><o:p></o:p></span></h3>
<h3 align="center" style="margin:0in;margin-bottom:.0001pt;text-align:center;background:white;box-sizing: border-box;font-size:1.31rem;padding:0.75rem 0px 0.5rem;widows: 1">
<span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);"> </span><span style="color:black"><o:p></o:p></span></h3>
<h3 align="center" style="margin:0in;margin-bottom:.0001pt;text-align:center;background:white;box-sizing: border-box;font-size:1.31rem;padding:0.75rem 0px 0.5rem;widows: 1">
<span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION</span><span style="color:black"><o:p></o:p></span></h3>
<p style="margin-left:51.0pt;text-indent:-.25in;mso-list:l0 level1 lfo2;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1" id="consensus-temporary.1"></a><!--[if !supportLists]--><span style="color: black;"><span style="mso-list:Ignore">?<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';">
</span></span></span><!--[endif]--><strong><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">Consensus Policies.</span></strong><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.1" id="consensus-temporary.1.1"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.1. "<em><b><span style="font-family: Helvetica, sans-serif;">Consensus Policies</span></b></em>" are those policies
established (1) pursuant to the procedure set forth inICANN's Bylaws and due process, and (2) covering those topics listed in Section 1.2 of this document. The Consensus Policy development process and procedure set forth in ICANN's Bylaws may be revised from
time to time in accordance with the process set forth therein.</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.2" id="consensus-temporary.1.2"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.2. Consensus Policies and the procedures by which they are developed shall be designed to produce, to the extent possible,
a consensus of Internet stakeholders, including registrars. Consensus Policies shall relate to one or more of the following:</span><span style="color:black"><o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #EEEEEE 4.5pt;padding:0in 0in 0in 15.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;margin-bottom:15.0pt;box-sizing: border-box">
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.2.1" id="consensus-temporary.1.2.1"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.2.1. issues for which uniform or coordinated resolution is reasonably necessary to facilitate interoperability,
security and/or stability of the Internet, Registrar Services, Registry Services, or the Domain Name System ("DNS");</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.2.2" id="consensus-temporary.1.2.2"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.2.2. functional and performance specifications for the provision of Registrar Services;</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.2.3" id="consensus-temporary.1.2.3"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.2.3. registrar policies reasonably necessary to implement Consensus Policies relating to a gTLD registry;</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.2.4" id="consensus-temporary.1.2.4"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.2.4. resolution of disputes regarding the registration of domain names (as opposed to the use of such domain names,
but including where such policies take into account use of the domain names); or</span><span style="color:black"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:51.0pt;margin-bottom:.0001pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem">
<a name="consensus-temporary.1.2.5" id="consensus-temporary.1.2.5"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.2.5. restrictions on cross-ownership of registry operators and registrars or Resellers and regulations and restrictions
with respect to registrar and registry operations and the use of registry and registrar data in the event that a registry operator and a registrar or Reseller are affiliated.</span><span style="color:black"><o:p></o:p></span></p>
</blockquote>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.3" id="consensus-temporary.1.3"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.3. Such categories of issues referred to in Section 1.2 shall include, without limitation:</span><span style="color:black"><o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #EEEEEE 4.5pt;padding:0in 0in 0in 15.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;margin-bottom:15.0pt;box-sizing: border-box">
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.3.1" id="consensus-temporary.1.3.1"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.3.1. principles for allocation of registered names in a TLD (e.g., first-come/first-served, timely renewal, holding
period after expiration);</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.3.2" id="consensus-temporary.1.3.2"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.3.2. prohibitions on warehousing of or speculation in domain names by registries or registrars;</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.3.3" id="consensus-temporary.1.3.3"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.3.3. reservation of registered names in a TLD that may not be registered initially or that may not be renewed
due to reasons reasonably related to (i) avoidance of confusion among or misleading of users, (ii) intellectual property, or (iii) the technical management of the DNS or the Internet (e.g., establishment of reservations of names from registration);</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.3.4" id="consensus-temporary.1.3.4"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.3.4. maintenance of and access to accurate and up-to-date information concerning Registered Names and name servers;</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.3.5" id="consensus-temporary.1.3.5"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.3.5. procedures to avoid disruptions of domain name registrations due to suspension or termination of operations
by a registry operator or a registrar, including procedures for allocation of responsibility among continuing registrars of the Registered Names sponsored in aTLD by a registrar losing accreditation; and</span><span style="color:black"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:51.0pt;margin-bottom:.0001pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem">
<a name="consensus-temporary.1.3.6" id="consensus-temporary.1.3.6"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.3.6. the transfer of registration data upon a change in registrar sponsoring one or more Registered Names.</span><span style="color:black"><o:p></o:p></span></p>
</blockquote>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.4" id="consensus-temporary.1.4"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.4. In addition to the other limitations on Consensus Policies, they shall not:</span><span style="color:black"><o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #EEEEEE 4.5pt;padding:0in 0in 0in 15.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;margin-bottom:15.0pt;box-sizing: border-box">
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.4.1" id="consensus-temporary.1.4.1"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.4.1. prescribe or limit the price of Registrar Services;</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.4.2" id="consensus-temporary.1.4.2"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.4.2. modify the limitations on Temporary Policies (defined below) or Consensus Policies;</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.1.4.3" id="consensus-temporary.1.4.3"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.4.3. modify the provisions in the Registrar Accreditation Agreement regarding terms or conditions for the renewal,
termination or amendment of the Registrar Accreditation Agreement or fees paid by Registrar to ICANN; or</span><span style="color:black"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:51.0pt;margin-bottom:.0001pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem">
<a name="consensus-temporary.1.4.4" id="consensus-temporary.1.4.4"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">1.4.4. modify ICANN's obligations to not apply standards, policies, procedures or practices arbitrarily, unjustifiably,
or inequitably and to not single out Registrar for disparate treatment unless justified by substantial and reasonable cause, and exercise its responsibilities in an open and transparent manner.</span><span style="color:black"><o:p></o:p></span></p>
</blockquote>
<p style="margin-left:51.0pt;text-indent:-.25in;mso-list:l0 level1 lfo2;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.2" id="consensus-temporary.2"></a><!--[if !supportLists]--><span style="color: black;"><span style="mso-list:Ignore">?<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';">
</span></span></span><!--[endif]--><strong><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">Temporary Policies.</span></strong><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);"> Registrar shall comply with and
implement all specifications or policies established by the ICANN Board of Directors (the "<em><b><span style="font-family: Helvetica, sans-serif;">Board</span></b></em>") on a temporary basis, if adopted by the Board by a vote of at least two-thirds of its
members, so long as the Board reasonably determines that such modifications or amendments are justified and that immediate temporary establishment of a specification or policy on the subject is necessary to maintain the stability or security of Registrar Services,
Registry Services or the DNS or the Internet ("<em><b><span style="font-family: Helvetica, sans-serif;">Temporary Policies</span></b></em>").</span><span style="color:black"><o:p></o:p></span></p>
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.2.1" id="consensus-temporary.2.1"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">2.1. Such proposed specification or policy shall be as narrowly tailored as feasible to achieve those objectives. In
establishing any Temporary Policy, the Board shall state the period of time for which the Temporary Policy is adopted and shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws.</span><span style="color:black"><o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #EEEEEE 4.5pt;padding:0in 0in 0in 15.0pt;margin-left:0in;margin-top:5.0pt;margin-right:0in;margin-bottom:15.0pt;box-sizing: border-box">
<p style="margin-left:51.0pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.2.1.1" id="consensus-temporary.2.1.1"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">2.1.1. ICANN shall also issue an advisory statement containing a detailed explanation of its reasons for adopting
the Temporary Policy and why the Board believes such Temporary Policy should receive the consensus support of Internet stakeholders.</span><span style="color:black"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:51.0pt;margin-bottom:.0001pt;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem">
<a name="consensus-temporary.2.1.2" id="consensus-temporary.2.1.2"></a><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">2.1.2. If the period of time for which the Temporary Policy is adopted exceeds 90 days, the Board shall reaffirm
its temporary adoption every 90 days for a total period not to exceed one year, in order to maintain such Temporary Policy in effect until such time as it becomes aConsensus Policy. If the one year period expires or, if during such one year period, the Temporary
Policy does not become a Consensus Policy and is not reaffirmed by the Board, Registrar shall no longer be required to comply with or implement such Temporary Policy.</span><span style="color:black"><o:p></o:p></span></p>
</blockquote>
<p style="margin-left:51.0pt;text-indent:-.25in;mso-list:l0 level1 lfo2;background:white;box-sizing: border-box;line-height:1.4rem;font-size:1rem;margin:1.25rem">
<a name="consensus-temporary.3" id="consensus-temporary.3"></a><!--[if !supportLists]--><span style="color: black;"><span style="mso-list:Ignore">?<span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman';">
</span></span></span><!--[endif]--><strong><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);">Notice and Conflicts.</span></strong><span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);"> Registrar shall be afforded
a reasonable period of time following notice of the establishment of a Consensus Policy or Temporary Policy in which to comply with such policy or specification, taking into account any urgency involved. In the event of a conflict between Registrar Services
and Consensus Policies or any Temporary Policy, the Consensus Polices or Temporary Policy shall control, but only with respect to subject matter in conflict. For the avoidance of doubt,Consensus Policies that meet the requirements of this Specification may
supplement or supersede provisions of the agreements between Registrar and ICANN, but only to the extent that suchConsensus Policies relate to the matters set forth in Section 1.2 and 1.3 of this Specification.</span><span style="color:black"><o:p></o:p></span></p>
<p style="background:white;box-sizing: border-box;line-height:1.4rem;margin:1.25rem;widows: 1">
<span style="font-family: Helvetica, sans-serif; color: rgb(51, 51, 51);"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">J. Beckwith Burr</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Deputy General Counsel & Chief Privacy Officer</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 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;"><Metalitz>, Steven Metalitz <<a href="mailto:met@msk.com">met@msk.com</a>><br>
<b>Date: </b>Wednesday, November 4, 2015 at 11:03 AM<br>
<b>To: </b>'Malcolm Hutty' <<a href="mailto:malcolm@linx.net">malcolm@linx.net</a>>, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>>, Becky Burr <<a href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a>>, Accountability
Community <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>>, Andrew Sullivan <<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>>, "<a href="mailto:iab@iab.org">iab@iab.org</a>" <<a href="mailto:iab@iab.org">iab@iab.org</a>><br>
<b>Subject: </b>RE: [CCWG-ACCT] WP2 Issues from last night's call</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> </span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Malcolm, can you explain how domain name registration is not a “service that uses the Internet’s unique identifiers”?
</span><span style="color:black"><o:p></o:p></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"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Steve Metalitz </span><span style="color:black"><o:p></o:p></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"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 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">accountability-cross-community-bounces@icann.org</a>
[<a href="mailto:accountability-cross-community-bounces@icann.org">mailto:accountability-cross-community-bounces@icann.org</a>]
<b>On Behalf Of </b>Malcolm Hutty<br>
<b>Sent:</b> Wednesday, November 04, 2015 10:59 AM<br>
<b>To:</b> Alan Greenberg; Burr, Becky; Accountability Community; Andrew Sullivan;
<a href="mailto:iab@iab.org">iab@iab.org</a><br>
<b>Subject:</b> Re: [CCWG-ACCT] WP2 Issues from last night's call</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><br>
<br>
On 04/11/2015 14:17, Alan Greenberg wrote:<br>
> In the regulatory section, I would still like to see language that<br>
> explicitly says that the unique identifiers themselves are deemed to not<br>
> be "content".<br>
<br>
Alan,<br>
<br>
If you read the clause carefully, you will see that it does not say that<br>
ICANN cannot regulate Internet content; that's just a loose paraphrasing<br>
some people have been using in conversation.<br>
<br>
Instead, it says that ICANN "shall not regulate<br>
services that use the Internet's unique identifiers, or the content that<br>
such services carry or provide."<br>
<br>
So the target of that exclusion is not "content" but "services" and "the<br>
content that such services carry or provide". This neatly avoids the<br>
question of whether domain names are content, because even if they are,<br>
they are still outside the reach of that exclusion.<br>
<br>
Malcolm.<br>
-- <br>
Malcolm Hutty | tel: +44 20 7645 3523<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=CwMF-g&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=yv-2vaZRUToupIoctB5N26jR1-FX1R8g20SyyjFmT-8&s=A8DtJCyVMLau-WRON7AQ_czu4FzwQSRY5CwKB3_lfYQ&e=">
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>
_______________________________________________<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://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMF-g&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=yv-2vaZRUToupIoctB5N26jR1-FX1R8g20SyyjFmT-8&s=iCNwcPAMpoUQGaoDRWeh9IT72SUScm3T-i7MFMaS454&e=">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><o:p></o:p></span></p>
</div>
</div>
<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>
=================================================================<o:p></o:p></span></p>
</div>
</div>
<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>
=================================================================<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>