<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Oct 29, 2014 at 6:39 PM, Burr, Becky <span dir="ltr"><<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>></span> wrote:<br><blockquote class="gmail_quote" 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-family:Calibri,sans-serif">
<div>
<div style="font-size:14px">Sorry, formatting was odd, so resending</div>
<div style="font-size:14px"><br>
</div>
<div>
<p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri">Olivier,</span><span style="font-family:Calibri"><u></u><u></u></span></span></p>
<p class="MsoNormal"><span style="font-family:Calibri;font-size:16px"> </span></p>
<p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri">Thanks for this input. I’d like to take a step back so that we are all on the same page. I hope everyone with take the time to review this post. I think we are making
this work unnecessarily complicated.</span><span style="font-family:Calibri"><u></u><u></u></span></span></p>
<p class="MsoNormal"><span style="font-family:Calibri;font-size:16px"> </span></p>
<p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri">Under the straw man I’ve suggested the “Council” or “Body” or whatever it is called is responsible for negotiating and interacting with IANA on technical issues.</span></span></p></div></div></div></blockquote><div><br></div><div>Hmm...technical issue? so its assumed that the members of the council will be technical folks right? or the council members will further employ people to do their review? (Because i am positive that Larry of NTIA may not necessarily be technical enough to follow-up with the terms of the contract. However their oversight has been smooth because NTIA has access to resources to get as much personnel as required)<br></div><div> </div><blockquote class="gmail_quote" 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-family:Calibri,sans-serif"><div><div><p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri"> As defined
by the IANA functions contract, IANA’s naming-related tasks include the following:</span></span></p></div></div></div></blockquote><div><snipped the functions><br><br></div><div>And you don't think the community within ICANN can also perform those functions?....isn't what we are doing right now a sample? wouldn't setting up a cwg for this purpose achieve the same goal <br></div><blockquote class="gmail_quote" 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-family:Calibri,sans-serif"><div><div><p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri"><u></u><u></u></span></span></p><span style="font-family:Calibri;font-size:16px"> </span>
<p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri">I would agree with you that a conflict of interest could emerge if IANA was developing policies for the registries, but that is not what’s being proposed. </span></span></p></div></div></div></blockquote><blockquote class="gmail_quote" 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-family:Calibri,sans-serif"><div><div><p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri"> <b><span style="color:#fb0007">Rather,
all policy work would remain with ICANN subject to multi-stakeholder processes – just as it is now</span></b><span style="color:#fb0007">.</span></span></span> <span style="font-size:16px"><span style="font-family:Calibri"> <span style="letter-spacing:-.1pt">What conflict of interest arises in this situation?</span></span></span></p></div></div></div></blockquote><div><br></div><div>Multi-stakeholder group that also consist of the registries right. Proposing a council consisting registries alone already create another layer of decision making which generally means that the registries can wake-up one day and decide that ICANN is not doing fine (since they are presumably the contractor). How does the community's view get to influence such decision making? Also recall that the transition by NTIA requirement indicated that the role be transferred to multi-stakeholder and i don't think the registry alone will fit such description.<br></div><div> </div><blockquote class="gmail_quote" 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-family:Calibri,sans-serif"><div><div><p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri"><span style="letter-spacing:-.1pt"> Registries will be in
the best position to know whether or not IANA is processing name server changes in a timely fashion. Registries are harmed if it takes forever to do that.</span></span></span></p></div></div></div></blockquote><div><br></div><div>Well if they are then, they should raise it as a member of the community, again performing this role should not make the registries the contractor; they don't have to be a contractor to know/do this. <br></div><div> <br></div><blockquote class="gmail_quote" 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-family:Calibri,sans-serif"><div><div><p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri"><span style="letter-spacing:-.1pt"> </span></span></span><span style="font-family:Calibri;font-size:16px"></span><span style="font-size:16px"><span style="font-family:Calibri">I don’t see a conflict of interest in registries performing an oversight role with respect to IANA’s purely technical and operational functions.</span></span></p></div></div></div></blockquote><div><br></div><div>Again i have no problem with them doing this, but i have a problem when i don't have the opportunity to be part of the decision making (as an end-user for instance). <br></div><div> </div><blockquote class="gmail_quote" 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-family:Calibri,sans-serif"><div><div><p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri"> Remember, the IANA function
contract specifies that IANA’s role is<span style="letter-spacing:-.1pt"> technical and operational,
<b><i>not policy development. </i></b>If IANA does something that is inconsistent with ICANN policy, </span>I<span style="letter-spacing:-.1pt"> want the ICANN Board to be accountable. </span></span></span></p></div></div></div></blockquote><div><br></div><div>I think even an end-user who is involved in the process will detect this, its not overly technical to know when something is going wrong. <br></div><blockquote class="gmail_quote" 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-family:Calibri,sans-serif"><div><div><p class="MsoNormal"><span style="font-family:Calibri;letter-spacing:-0.1pt;font-size:16px"> </span></p>
<p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri;letter-spacing:-0.1pt">Again, to be clear, </span><span style="font-family:Calibri">I<span style="letter-spacing:-.1pt"> am not unalterably opposed to having other
parts of the community participate, but </span>I<span style="letter-spacing:-.1pt"> don</span>’<span style="letter-spacing:-.1pt">t understand why they would want to.</span></span></span></p></div></div></div></blockquote><div><br></div><div>They want to because they utilise the names resources. Perhaps i should refer to the numbers world where the oversight rest on community as much as possible(does not mean there is no room for improvement). I think such would be desired for the names world. Getting the registries to become the contractor and then the same registries participate in the policy process (with others) already is an indication of probable conflict in near future.<br><br></div><div>There is also the aspect of who determines the members of the council. Registries are not fairly distribute accross regions, so how will that be resolved to ensure there is fairness of representation. Who funds the council to perform its operations? these are all questions that could help us appreciate that we may be heading to creating a political council and not necessarily a technical council<br><br></div><div>Regards<br></div><blockquote class="gmail_quote" 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-family:Calibri,sans-serif"><div><div><p class="MsoNormal"><span style="font-size:16px"><span style="font-family:Calibri"><span style="letter-spacing:-.1pt"><u></u><u></u></span></span></span></p>
<p class="MsoNormal"><span style="font-family:Calibri;letter-spacing:-0.1pt;font-size:16px"> </span></p>
<p class="MsoNormal"><span style="font-family:Calibri;letter-spacing:-0.1pt;font-size:16px">Becky</span><font size="3"><u></u><u></u></font></p>
</div>
<div style="font-size:14px">
<p class="MsoNormal"><span style="font-size:9pt;font-family:Arial,sans-serif">J. Beckwith Burr<u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Neustar, Inc. /</span></b><span style="font-size:9pt;font-family:Arial,sans-serif"> Deputy General Counsel and Chief Privacy Officer<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:Arial,sans-serif">1775 Pennsylvania Avenue NW, Washington, DC 20006<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Office</span><span style="font-size:9pt;font-family:Arial,sans-serif">: <a href="tel:%2B%201.202.533.2932" value="+12025332932" target="_blank">+ 1.202.533.2932</a> <span style="color:rgb(6,134,88)"> Mobile</span>:
<a href="tel:%2B1.202.352.6367" value="+12023526367" target="_blank">+1.202.352.6367</a> <span style="color:rgb(6,134,88)">/ <a href="mailto:becky.burr@neustar.biz" style="color:purple" target="_blank">becky.burr@neustar.biz</a> / <a href="http://www.neustar.biz" target="_blank">www.neustar.biz</a></span></span></p>
</div>
</div>
<div style="font-size:14px"><br>
</div>
<span style="font-size:14px">
<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><Burr>, Becky Burr <<a href="mailto:becky.burr@neustar.biz" target="_blank">becky.burr@neustar.biz</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, October 29, 2014 at 1:16 PM<br>
<span style="font-weight:bold">To: </span>Olivier MJ Crepin-Leblond <<a href="mailto:ocl@gih.com" target="_blank">ocl@gih.com</a>>, "<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>" <<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap:break-word">
<div>
<div style="color:rgb(0,0,0)"><span style="font-size:16px">Olivier,</span></div>
<div style="color:rgb(0,0,0)"><span style="font-size:16px"><br>
</span></div>
<div><span style="font-size:16px">Thanks for this input. I’d like to take a step back so that we are all on the same page. I hope everyone with take the time to review this post. I think we are making this work unnecessarily complicated.</span></div>
<div style="color:rgb(0,0,0)"><span style="font-size:16px"><br>
</span></div>
<div style="color:rgb(0,0,0)"><span style="font-size:16px">Under the straw man I’ve suggested the “Council” or “Body” or whatever it is called is responsible for negotiating and interacting with IANA on technical issues. As defined by the IANA functions
contract, IANA’s naming-related tasks include the following:</span></div>
<div style="color:rgb(0,0,0)"><span style="font-size:16px"><br>
</span></div>
<div>
<ol>
<li><span style="color:rgb(0,0,0);font-style:normal;font-weight:normal;text-decoration:none;font-size:16px"><b><span style="letter-spacing:-.05pt">Root</span><span style="letter-spacing:-.25pt"></span>Zone<span style="letter-spacing:-.35pt">
</span><span style="letter-spacing:-.05pt">File</span><span style="letter-spacing:-.2pt"></span><span style="letter-spacing:-.05pt">Change</span><span style="letter-spacing:-.25pt"></span><span style="letter-spacing:-.05pt">Request</span><span style="letter-spacing:-.15pt"></span><span style="letter-spacing:-.05pt">Management</span><span style="letter-spacing:.1pt"></span>--<span style="letter-spacing:-.15pt">
</span></b><span style="letter-spacing:-.05pt">The</span><span style="letter-spacing:-.1pt"></span><span style="letter-spacing:-.05pt">Contractor</span><span style="letter-spacing:-.15pt"></span><span style="letter-spacing:-.05pt">shall</span><span style="letter-spacing:-.25pt"></span><span style="letter-spacing:-.05pt">receive</span><span style="letter-spacing:-.2pt"></span><span style="letter-spacing:-.05pt">and</span><span style="letter-spacing:2.95pt"></span><span style="letter-spacing:-.05pt">process</span><span style="letter-spacing:-.15pt"></span><span style="letter-spacing:-.05pt">root</span><span style="letter-spacing:-.15pt"></span><span style="letter-spacing:-.05pt">zone</span><span style="letter-spacing:-.2pt"></span>file<span style="letter-spacing:-.2pt">
</span><span style="letter-spacing:-.05pt">change</span><span style="letter-spacing:-.1pt"></span><span style="letter-spacing:-.05pt">requests
</span>for<span style="letter-spacing:-.15pt"></span><span style="letter-spacing:-.05pt">TLD</span>s<span style="letter-spacing:-.2pt"></span>as<span style="letter-spacing:2.65pt">
</span><span style="letter-spacing:-.05pt">expeditiously</span><span style="letter-spacing:-.25pt"></span>as<span style="letter-spacing:-.1pt">
</span><span style="letter-spacing:-.05pt">possible. This does not include a policy role at all. A new TLD is entered into the root only after the ICANN Board directs IANA to do that. Policy remains in ICANN, not the IANA function.</span></span></li><li><span style="font-size:16px"><b>Root</b><b><span style="letter-spacing:-.3pt"></span></b><b>Zone<span style="letter-spacing:-.3pt"></span><span style="letter-spacing:-.05pt">“WHOIS”</span><span style="letter-spacing:-.25pt"></span><span style="letter-spacing:-.05pt">Change</span><span style="letter-spacing:-.3pt"></span><span style="letter-spacing:-.05pt">Request</span><span style="letter-spacing:-.15pt"></span><span style="letter-spacing:-.05pt">and</span><span style="letter-spacing:-.2pt"></span><span style="letter-spacing:-.05pt">Database</span><span style="letter-spacing:-.25pt"></span><span style="letter-spacing:-.05pt">Management</span>
--<span style="letter-spacing:-.2pt"></span></b><font>The</font><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">Contractor</span><span style="letter-spacing:3.05pt"></span><span style="letter-spacing:-0.05pt">shall</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">maintain,</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">update,</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">and
make publicly</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">accessible
</span><font>a</font><span style="letter-spacing:-0.2pt"></span><font>Root</font><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">Zone</span><span style="letter-spacing:0.25pt"></span><span style="letter-spacing:-0.05pt">“</span><span style="letter-spacing:-0.05pt">WHOIS</span><span style="letter-spacing:-0.05pt">”</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">database</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">with</span><span style="letter-spacing:3.45pt"></span><span style="letter-spacing:-0.05pt">current</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">and
verified</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">contact information</span><span style="letter-spacing:0.15pt"></span><span style="letter-spacing:-0.05pt">for</span><span style="letter-spacing:-0.1pt"></span><font>all</font><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">TLD
r</span><span style="letter-spacing:-0.05pt">egistry</span><span style="letter-spacing:-0.15pt"></span><font><span style="letter-spacing:-0.05pt">operators. Again, this involves
no policy role. ICANN makes policy on WHOIS, not IANA. IANA just follows ICANN</span></font><span>’</span><font><span style="letter-spacing:-0.05pt">s orders.</span></font></span></li><li><span style="font-size:16px"><b><span style="letter-spacing:-0.05pt">Delegation</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.1pt">and</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">Redelegation</span><span style="letter-spacing:-0.25pt"></span></b><span><b>of<span style="letter-spacing:-.15pt"></span>a<span style="letter-spacing:-.3pt"> Generic
TLDs and </span><span style="letter-spacing:-.05pt">Country</span><span style="letter-spacing:-.35pt"></span><span style="letter-spacing:-.05pt">Code</span></b><span style="letter-spacing:-0.35pt"><b> TLDs</b>. Again, the role is administrative and not
policy making. IANA adds or removes a TLD from the root only at the direction of the ICANN Board. It is responsible for documenting that the action was consistent with established ICANN policy, but has no role in formulating that policy.</span></span></span></li><li><span style="color:rgb(0,0,0);font-style:normal;font-weight:normal;text-decoration:none;font-size:16px"><b><span style="letter-spacing:-0.05pt">Root</span><span style="letter-spacing:-0.2pt"></span>Zone<span style="letter-spacing:-.3pt">
</span><span style="letter-spacing:-.05pt">Automation</span><span style="letter-spacing:.05pt"></span><span style="letter-spacing:-.05pt">--</span><span style="letter-spacing:-.1pt"></span></b><span style="letter-spacing:-0.05pt">The</span><span style="letter-spacing:-0.1pt">
Contractor</span><span style="letter-spacing:-0.05pt"> shall</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">work</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">with</span><span style="letter-spacing:-0.2pt"></span>NTIA<span style="letter-spacing:-0.2pt">
</span>and<span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">the</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">Root</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">Zone</span><span style="letter-spacing:2.85pt"></span><span style="letter-spacing:-0.05pt">Maintainer,</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">and
collaborate</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">with</span><span style="letter-spacing:-0.1pt"></span>all<span style="letter-spacing:-0.25pt">
</span><span style="letter-spacing:-0.05pt">interested</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">and</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">affected</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">parties</span><span style="letter-spacing:-0.1pt"> </span>to<span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">deploy</span><span style="letter-spacing:-0.15pt"></span>a<span style="letter-spacing:-0.2pt">
</span><span style="letter-spacing:-0.05pt">fully</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">automated root</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">zone</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">management</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">system.
This is an administrative/operations task, not a policy task.</span><span style="letter-spacing:-0.15pt"></span></span></li><li><span style="color:rgb(0,0,0);font-style:normal;font-weight:normal;text-decoration:none;font-size:16px"><b><span style="letter-spacing:-0.05pt">Root</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">Domain</span><span style="letter-spacing:-0.3pt"></span><span style="letter-spacing:-0.05pt">Name</span><span style="letter-spacing:-0.35pt"></span><span style="letter-spacing:-0.05pt">System</span><span style="letter-spacing:-0.3pt"></span><span style="letter-spacing:-0.05pt">Security</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">Extensions</span><span style="letter-spacing:-0.3pt"></span><span style="letter-spacing:-0.05pt">(DNSSEC)</span><span style="letter-spacing:-0.3pt"></span>Key<span style="letter-spacing:-.4pt">
</span><span style="letter-spacing:-.05pt">Management</span><span style="letter-spacing:.05pt"></span><span style="letter-spacing:-.05pt">--</span></b><span style="letter-spacing:-0.05pt">The</span><span style="letter-spacing:3.25pt"></span><span style="letter-spacing:-0.05pt">Contractor</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">shall</span><span style="letter-spacing:-0.2pt"></span>be<span style="letter-spacing:-0.1pt">
</span><span style="letter-spacing:-0.05pt">responsible</span><span style="letter-spacing:-0.25pt"></span>for<span style="letter-spacing:-0.2pt">
</span><span style="letter-spacing:-0.05pt">the</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">management</span><span style="letter-spacing:-0.2pt"></span>of<span style="letter-spacing:-0.2pt">
</span><span style="letter-spacing:-0.05pt">the root</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">zone</span><span style="letter-spacing:-0.2pt"></span>Key<span style="letter-spacing:-0.15pt">
</span><span style="letter-spacing:-0.05pt">Signing</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">Key</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">(KSK),</span><span style="letter-spacing:3.15pt"></span><span style="letter-spacing:-0.05pt">including</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">generation,</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">publication,</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">and</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">use</span><span style="letter-spacing:-0.2pt"></span>for<span style="letter-spacing:-0.25pt">
</span><span style="letter-spacing:-0.05pt">signing</span><span style="letter-spacing:-0.2pt"></span>the<span style="letter-spacing:-0.25pt">
</span>Root<span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">Keyset. Again, DNSSEC policy is set by ICANN, informed by all stakeholders, the SSAC, etc. IANA simply administers the ICANN policy.</span></span></li><li><span style="font-size:16px"><b><span style="letter-spacing:-0.05pt">Customer</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">Service</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">Complaint</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">Resolution</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">Process</span><span style="letter-spacing:0.1pt"></span><span style="letter-spacing:-0.1pt">(CSCRP)</span><span style="letter-spacing:-0.25pt"></span>--</b><span>The</span><span style="letter-spacing:-0.3pt"></span><span style="letter-spacing:-0.05pt">Contractor</span><span style="letter-spacing:-0.4pt"></span><span style="letter-spacing:-0.05pt">shall</span><span style="letter-spacing:3.65pt"></span><span style="letter-spacing:-0.05pt">work</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">with</span><span style="letter-spacing:-0.1pt"></span><span>NTIA</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">and
collaborate</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">with</span><span style="letter-spacing:-0.1pt"></span><span>all</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">interested</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">and</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">affected</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">parties</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">to</span><span></span><span style="letter-spacing:-0.05pt">establish</span><span style="letter-spacing:-0.1pt"></span><span>and</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">implement</span><span style="letter-spacing:0.05pt"></span><span>a</span><span style="letter-spacing:4.05pt"></span><span style="letter-spacing:-0.05pt">process</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">for</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">IANA</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">function</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">customers</span><span style="letter-spacing:-0.25pt"></span><span>to</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">submit</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">complaints</span><span style="letter-spacing:-0.25pt"></span><span>for</span><span style="letter-spacing:-0.25pt"></span><span>timely</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">resolution</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">that</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">follows </span><span style="letter-spacing:-0.05pt">industry</span><span style="letter-spacing:-0.3pt"></span><span>best</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">practice</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">and</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">includes</span><span style="letter-spacing:-0.25pt"></span><span>a</span><span style="letter-spacing:0.05pt"></span><span style="letter-spacing:-0.05pt">reasonable</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">timeframe</span><span style="letter-spacing:-0.25pt"></span><span style="letter-spacing:-0.05pt">for</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">resolution.
This relates to complaints about IANA doing its technical job in a timely and competent fashion, not policy, which remains with ICANN.</span></span></li><li><span style="font-size:16px"><b><span style="letter-spacing:-.05pt">Perform</span><span style="letter-spacing:-.35pt"></span><span style="letter-spacing:-.05pt">Administrative</span><span style="letter-spacing:-.3pt"></span><span style="letter-spacing:-.05pt">Functions</span><span style="letter-spacing:-.35pt"></span><span style="letter-spacing:-.05pt">Associated</span><span style="letter-spacing:-.3pt"></span>With<span style="letter-spacing:-.3pt">
</span><span style="letter-spacing:-.05pt">Root</span><span style="letter-spacing:-.3pt"></span><span style="letter-spacing:-.05pt">Zone</span><span style="letter-spacing:-.3pt"></span><span style="letter-spacing:-.05pt">Management. F</span></b><span style="letter-spacing:-0.05pt">acilitate</span><span style="letter-spacing:-0.1pt"></span>and<span style="letter-spacing:-0.2pt">
</span><span style="letter-spacing:-0.05pt">coordinate</span><span style="letter-spacing:-0.15pt"></span><span style="letter-spacing:-0.05pt">the</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">root</span><span style="letter-spacing:-0.15pt"></span>zone<span style="letter-spacing:-0.2pt">
</span><span style="letter-spacing:-0.05pt">of</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">the</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">domain</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">name</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">system,</span><span style="letter-spacing:-0.2pt"></span>and<span style="letter-spacing:3.75pt">
</span><span style="letter-spacing:-0.05pt">maintain</span><span style="letter-spacing:-0.25pt"></span>24<span style="letter-spacing:-0.2pt">
</span><span style="letter-spacing:-0.05pt">hour-a-day/7</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">days-a-week</span><span style="letter-spacing:-0.2pt"></span><span style="letter-spacing:-0.05pt">operational</span><span style="letter-spacing:-0.1pt"></span><span style="letter-spacing:-0.05pt">coverage.</span></span></li></ol>
<div><span style="color:rgb(0,0,0);font-style:normal;font-weight:normal;text-decoration:none;font-size:16px"><br>
</span></div>
<div><span style="font-size:16px">I would agree with you that a conflict of interest could emerge if IANA was developing policies for the registries, but that is not what’s being proposed. </span><font color="#ff0000"><b><span style="font-size:16px">Rather,
all policy work would remain with ICANN subject to multi-stakeholder processes – just as it is now</span></b><span style="font-size:16px">.</span></font><span style="font-size:16px"> </span><span><span style="font-size:16px;letter-spacing:-0.05pt">What
conflict of interest arises in this situation? Registries will be in the best position to know whether or not IANA is processing name server changes in a timely fashion. Registries are harmed if it takes forever to do that. To the limited extent this kind
of thing might impact end users, registries have all of the necessary incentives to get it fixed. In the early years of ICANN, when IANA was performing very poorly, registries were unhappy, but most of the rest of the ICANN community was not impacted in any
way. Today, the ICANN board - NOT IANA - promises stakeholders that IANA will do its work in accordance with ICANN policy. If it doesn't, </span><span style="font-size:16px">I</span><span style="font-size:16px;letter-spacing:-0.05pt"> am going to
look to the ICANN Board and not the IANA staff for redress. </span></span></div>
<div><span style="font-size:16px"><br>
</span></div>
<div><span style="font-size:16px">I don’t see a conflict of interest in registries performing an oversight role with respect to IANA’s purely technical and operational functions. Remember, the IANA function contract specifies that IANA’s role is</span><span><span style="font-size:16px;letter-spacing:-0.05pt"> technical
and operational, </span><i style="font-size:16px;letter-spacing:-0.05pt;font-weight:bold">not policy development. </i><span style="font-size:16px;letter-spacing:-0.05pt">If IANA does something that is inconsistent with ICANN policy, </span><span style="font-size:16px">I</span><span style="font-size:16px;letter-spacing:-0.05pt"> want
the ICANN Board to be accountable. </span></span></div>
<div><span style="font-size:16px"><span style="letter-spacing:-0.05pt"><br>
</span></span></div>
<div><span><span style="font-size:16px;letter-spacing:-0.05pt">Again, to be clear, </span><span style="font-size:16px">I</span><span style="font-size:16px;letter-spacing:-0.05pt"> am not unalterably opposed to having
other parts of the community participate, but </span><span style="font-size:16px">I</span><span style="font-size:16px;letter-spacing:-0.05pt"> don</span><span style="font-size:16px">’</span><span style="font-size:16px;letter-spacing:-0.05pt">t
understand why they would want to. </span></span><span style="font-size:16px"> </span></div>
<p style="margin-top:0.1pt;margin-right:5.15pt;margin-left:41pt">
<u></u><u></u></p>
<p style="margin-top:0.1pt;margin-right:5.15pt;margin-left:41pt">
<br>
</p>
<p style="margin-right:7.75pt;margin-left:40.5pt">
<font face="Calibri,sans-serif" size="3"><span style="letter-spacing:-0.05pt"><br>
</span></font></p>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<p class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt"><span style="font-size:9pt;font-family:Arial,sans-serif">J. Beckwith Burr<u></u><u></u></span></p>
<p class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt"><b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Neustar, Inc. /</span></b><span style="font-size:9pt;font-family:Arial,sans-serif"> Deputy
General Counsel and Chief Privacy Officer<u></u><u></u></span></p>
<p class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt"><span style="font-size:9pt;font-family:Arial,sans-serif">1775 Pennsylvania Avenue NW, Washington, DC 20006<u></u><u></u></span></p>
<p class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt"><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Office</span><span style="font-size:9pt;font-family:Arial,sans-serif">: <a href="tel:%2B%201.202.533.2932" value="+12025332932" target="_blank">+ 1.202.533.2932</a> <span style="color:rgb(6,134,88)"> Mobile</span>:
<a href="tel:%2B1.202.352.6367" value="+12023526367" target="_blank">+1.202.352.6367</a> <span style="color:rgb(6,134,88)">/ <a href="mailto:becky.burr@neustar.biz" style="color:purple" target="_blank">becky.burr@neustar.biz</a> / <a href="http://www.neustar.biz" target="_blank">www.neustar.biz</a></span></span></p>
</div>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<span style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<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>Olivier MJ Crepin-Leblond <<a href="mailto:ocl@gih.com" target="_blank">ocl@gih.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, October 29, 2014 at 11:50 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>" <<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000">Hello all,<br>
<br>
irrespective of whether an "Oversight Council" is a desirable thing or not (I have not yet made up my mind about this, only having very basic information about it), I see a serious conflict of Interest where only the directly affected parties oversee operations
that concern them directly. <br>
There was much discussion about the GAC having seats. Although I have not asked them, I am pretty much sure that end users, as affected parties, would need a number of seats too.<br>
<br>
Kind regards,<br>
<br>
Olivier<br>
<br>
<div>On 29/10/2014 14:33, Burr, Becky wrote:<br>
</div>
<blockquote type="cite">
<div>
<div>I’d envisioned the “Oversight Council” to be elected by registries (ccs and gs) organized in some fashion outside of the ICANN umbrella – so the IANA Oversight Inc. or other association we were talking about the other day. It seems to me that the duties
and authority of the Council would be determined by the membership of the organization (I.e., the registries) – so these questions would be resolved as part of structuring Oversight, Inc. Let’s not create yet another separate mechanism. Instead, figure out
a way for the views of all stakeholders with respect to major decisions can be collected by Oversight, Inc. and taken into account in the process of developing major proposals. </div>
<div><br>
</div>
<div><br>
</div>
<div>
<p class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt">
<span style="font-size:9pt;font-family:Arial,sans-serif">J. Beckwith Burr<u></u><u></u></span></p>
<p class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt">
<b><span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Neustar, Inc. /</span></b><span style="font-size:9pt;font-family:Arial,sans-serif"> Deputy General Counsel and Chief Privacy Officer<u></u><u></u></span></p>
<p class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt">
<span style="font-size:9pt;font-family:Arial,sans-serif">1775 Pennsylvania Avenue NW, Washington, DC 20006<u></u><u></u></span></p>
<p class="MsoNormal" style="margin:0in 0in 0.0001pt;font-size:11pt">
<span style="font-size:9pt;font-family:Arial,sans-serif;color:rgb(6,134,88)">Office</span><span style="font-size:9pt;font-family:Arial,sans-serif">: <a href="tel:%2B%201.202.533.2932" value="+12025332932" target="_blank">+ 1.202.533.2932</a> <span style="color:rgb(6,134,88)"> Mobile</span>: <a href="tel:%2B1.202.352.6367" value="+12023526367" target="_blank">+1.202.352.6367</a> <span style="color:rgb(6,134,88)">/ <a href="mailto:becky.burr@neustar.biz" style="color:purple" target="_blank">becky.burr@neustar.biz</a> /
<a href="http://www.neustar.biz" target="_blank">www.neustar.biz</a></span></span></p>
</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>Guru Acharya <<a href="mailto:gurcharya@gmail.com" target="_blank">gurcharya@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, October 29, 2014 at 9:35 AM<br>
<span style="font-weight:bold">To: </span>Allan MacGillivray <<a href="mailto:allan.macgillivray@cira.ca" target="_blank">allan.macgillivray@cira.ca</a>><br>
<span style="font-weight:bold">Cc: </span>Becky Burr <<a href="mailto:becky.burr@neustar.biz" target="_blank">becky.burr@neustar.biz</a>>, "<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>" <<a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a>>,
"Lindeberg, Elise" <<a href="mailto:elise.lindeberg@npt.no" target="_blank">elise.lindeberg@npt.no</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div>Postulates emerging from Allan's remarks:</div>
<div><br>
</div>
<div>The Oversight Council will monitor compliance with day to day technical SLA type requirements.<br>
</div>
<div><br>
</div>
<div>Even though the final contracting authority of changing the IANA operator will rest with the Oversight Council:<br>
</div>
<div><br>
</div>
<div>1) There will be a "separate mechanism" for recommending any major decision to the Oversight Council, including change of IANA operator</div>
<div><br>
</div>
<div>2) The Oversight Council will be bound to accept/implement the decision of the "separate mechanism". </div>
<div><br>
</div>
<div>3) That "separate mechanism" will necessarily involve the views of the GAC.</div>
<div><br>
</div>
<div>4) That "separate mechanism" will be at an arms length from ICANN so that the ICANN board can not interfere since ICANN is the present IANA operator.</div>
<div><br>
</div>
<div>How do we intend to codify these characteristics of the "separate mechanism" so that the GAC can be assured that they will be consulted in case of change of the IANA operator? Maybe as part of a MOU between the Oversight Council and GAC+ALAC+GNSO+CCSNO?</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 29, 2014 at 6:32 PM, Allan MacGillivray <span dir="ltr">
<<a href="mailto:allan.macgillivray@cira.ca" target="_blank">allan.macgillivray@cira.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-CA">
<div>
<p class="MsoNormal">I see the “oversight council” as being a body that deals with IANA compliance with day-to-day SLA-type responsibilities e.g. the current performance metric that 80% of root zone file and WHOIS database change requests be completed within
21 days. I would not expect that governments (other than those that are ccTLD operators) would have much interest in this. However, were there to be major review of these functions, such as that which the NTIA initiated in 2011 with its NOI, or to change
the operator, then I would expect that the responsibility for conducting such a review would not fall on the ‘oversight council’ alone and that in whatever mechanism that would be established, there could be a role for governments.</p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif" lang="EN-US">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif" lang="EN-US"><a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a>
[mailto:<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Guru Acharya<br>
<b>Sent:</b> October-29-14 8:32 AM<br>
<b>To:</b> Becky Burr<br>
<b>Cc:</b> <a href="mailto:cwg-stewardship@icann.org" target="_blank">
cwg-stewardship@icann.org</a>; Lindeberg, Elise<br>
<b>Subject:</b> Re: [CWG-Stewardship] [IANA-issues] Fwd: Names Community vs the other two communities</span></p>
<div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Becky. I agree with your initial assessment that the "oversight council" would focus on "technical and operational issues" (as opposed to policy issues); and therefore GAC participation in the council will not be required even though GAC
participation at an equal footing will not be inconsistent with the multi-stakeholder model. </p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">However, I think GAC participation in the council might be essential in the scenario where the oversight council decides to change the IANA operator in the future. If the council decides to contract a different operator (different from
ICANN) in the future, would it not lead to various policy issues such as jurisdiction of the new IANA operator, financing of the new IANA operator etc - where the insight of the GAC may be beneficial?</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Therefore I think GAC should be a part of the oversight council.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Regards,</p>
</div>
<div>
<p class="MsoNormal">Guru</p>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On Tue, Oct 28, 2014 at 8:47 PM, Burr, Becky <<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>> wrote:</p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black">Thanks Elise, very helpful. I was thinking that the “oversight counsel” would focus on technical and operational issues as opposed to policy issues ... But
policy for IANA would remain in existing ICANN processes. Could you help me understand which technical/operational IANA services might raise “public interest” concerns? I agree with you that having some GAC reps on a Oversight Counsel would not be inconsistent
with the Strickling view, but I am curious about why GAC might want to participate in that kind of counsel. </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri,sans-serif;color:black"> </span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span><br>
<fieldset></fieldset> <br>
<pre>_______________________________________________
CWG-Stewardship mailing list
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_cwg-2Dstewardship&d=AAMF-g&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=TdVuaup5FYNO7Kbzw-WeiPL40WR6uQHvHCZH8wY06S4&s=yoOCQp_8bldp5dAaRtsRf1G1SnLtkZg7UeOAZjWdPj8&e=" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a></pre>
</blockquote>
<br>
</div>
</div>
</span></div>
</div>
</span>
</div>
<br>_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">------------------------------------------------------------------------<br><font color="#888888"><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:garamond,serif">
<i><span style="color:rgb(0,102,0)">Seun Ojedeji,<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Federal University Oye-Ekiti<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">web: </span><a href="http://www.fuoye.edu.ng" target="_blank">http://www.fuoye.edu.ng</a><br>
<span style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Mobile: <a value="+2348035233535">+2348035233535</a></span><span style="color:rgb(0,102,0)"></span><br></i><i><span style="color:rgb(0,102,0)">alt email:<a href="http://goog_1872880453" target="_blank"> </a><a href="mailto:seun.ojedeji@fuoye.edu.ng" target="_blank">seun.ojedeji@fuoye.edu.ng</a></span></i><br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The key to understanding is humility - my view !<br></blockquote></blockquote></font><br></div>
</div></div>