<p dir="ltr">Okay I see the point, so it's really not about asking why role 2 (as I listed) is not covered in policy implementation because they are 2 distinct roles. It's more about asking why the dependencies are not evident in the current wording of the 2 roles.</p>
<p dir="ltr">Regards</p>
<div class="gmail_quot<blockquote class=" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
<div>
<div>My question, Seun, is why that is not already covered by implementation of policy. I surely do not have an objection to ICANN allocating and assigning names in the root zone consistent with applicable policy (e.g., New gTLD PDP, RFC 1591 in the case of
ccTLDs), but absent that caveat, the addition seems potentially broad.</div>
<div>
<div><br>
</div>
<p class="MsoNormal" style="margin-top:12.0pt"></p>
<p class="MsoNormal" style="margin-top:12.0pt"><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>
<div><br>
</div>
<span>
<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>Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, December 16, 2015 at 11:26 AM<br>
<span style="font-weight:bold">To: </span>Becky Burr <<a href="mailto:becky.burr@neustar.biz" target="_blank">becky.burr@neustar.biz</a>><br>
<span style="font-weight:bold">Cc: </span>Accountability Community <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CCWG-ACCT] The Board's take on the Mission Statement<br>
</div>
<div><br>
</div>
<div>
<div>
<p dir="ltr">On Dec 16, 2015 17:00, "Burr, Becky" <<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>> wrote:<br>
><br>
><br>
> I have asked Bruce to explain what is encompassed by "the allocation and assignment of names in the root zone” that is not covered by “coordination of the development and implantation of policies.” <br>
><br>
SO(Not Bruce): The former is an action item in relation to RZ, the later is means to the former. We may be concerned if just the former is preferred but from your pasted table, I see that both was accommodated.</p>
<p dir="ltr">I hope no one would argue that ICANN performs 2 main roles in relation to names;
<br>
1. Coordinate development and implementation of policies<br>
2. Allocate names to the root zone</p>
<p dir="ltr">So I don't see anything wrong in trying to reflect its actual role if indeed the goal is to ensure clarity on role.</p>
<p dir="ltr">Regards</p>
<p dir="ltr">> I encourage each of you to study the side-by-side comparison attached to determine for yourself whether the Board’s approach is consistent with the goals of clarifying ICANN’s limited Mission.<br>
><br>
><br>
> J. Beckwith Burr <br>
> Neustar, Inc. / Deputy General Counsel & Chief Privacy Officer<br>
> 1775 Pennsylvania Avenue NW, Washington D.C. 20006<br>
> Office: <a href="tel:%2B1.202.533.2932" value="+12025332932" target="_blank">+1.202.533.2932</a> Mobile: <a href="tel:%2B1.202.352.6367" value="+12023526367" target="_blank">+1.202.352.6367</a> / <a href="http://neustar.biz" target="_blank">
neustar.biz</a><br>
><br>
><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://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=I_lsQXHH-_-YpVvnJPiJR-So7R07mgx9CAvYeXCUPlg&s=Ghv7wcAWeQryJQcT-w63p2pW38WmDtFSBwUET-1SVg4&e=" target="_blank">
https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
><br>
</p>
</div>
</div>
</span>
</div>
</div>