<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; "><br><div><div>On Feb 24, 2014, at 10:53 AM, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Feb 24, 2014 at 4:38 PM, Steve Crocker <span dir="ltr"><<a href="mailto:steve@shinkuro.com" target="_blank">steve@shinkuro.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Marilyn, et al,<br>
<br>
Thanks. Two comments about root servers�<br>
<br>
1. A list of which countries have root servers and which do not is the beginning but not the end of the discussion. The technical question is whether a locale is being served well enough. "Well enough" is usually measured in terms of delay to get an answer to a look up, e.g. 89 milliseconds, and reliability, e.g. answers are received 99.923% of the time. (Both of the numbers in the previous sentence are illustrative and not related to any actual measurement. I made them up as I typed.) On the other hand, many people seem concerned with political questions, e.g. which countries are important enough to have root servers. It would help the discussion to know what questions are being asked. The list of root server locations may or may not be relevant.<br>
</blockquote><div><br></div><div>For me, i am not really about the political aspect, just as you indicated the more local the root is the better for us.<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2. The root zone is just the top level of the DNS hierarchy. After receiving an answer from a root zone server, the resolver then has to make another query to the TLD's name server. If the TLD's name server is far away, slow or not responding, having a local copy of the root zone isn't much help. As a practical matter, it maybe *much* better to have a local copy of the .com zone than the root zone.<br>
</blockquote><div><br></div><div>Yeah you are right, but it takes lesser process to have TLD name servers. The closer the root servers, will definitely create an even 'more' closer TLDs<br></div></div></div></div></blockquote><div><br></div>I don't understand what you mean about "lesser process to have TLD name servers." It's pretty easy to have a root server.</div><div><br></div><div>Steve</div><div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Cheers! <br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Steve<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
On Feb 24, 2014, at 10:26 AM, Marilyn Cade <<a href="mailto:marilynscade@hotmail.com">marilynscade@hotmail.com</a>> wrote:<br>
<br>
> David is right, but this was probably an unintended change in 'terminology'.<br>
> So, we still should call a root server, as it is a root server. :-)<br>
><br>
> I will just make a comment about definitions and terminology.<br>
> While not alone in this challenge, within the Business Constituency @ICANN, we found that we had to devote time to creating an "acronym buster" [sorry for the slang terminology], in order to decode the vast number of terms, and abbreviations.<br>
><br>
> Others have undertaken similar challenging tasks, but creating new labels for existing<br>
> functions/things which are well entrenched in a lot of materials and working activities will to me delay our ability to focus on challenging work.<br>
><br>
> Pasted here from David Conrad's response:<br>
> "It might also be useful to observe that a common technique at larger ISPs and other resolver operators is to mirror the root zone into their resolvers, thereby removing the need of those resolvers to actually query the root servers. As such, those resolvers could be considered to be a form of root name servers as well. Of course, it is a bit challenging to identify which resolvers actually do this mirroring... "<br>
><br>
> I support David's comment about the function of the larger ISPs and web hosting companies, and actually even very large corporations that are NOT ISPs or networking companies, but who operate huge networks that may serve business functions -- for instance, many banks, in many part of the world, operate secure networks, and so they may also be mirroring the root zone in their resolvers.<br>
><br>
> However, while the resolver performs that function, I wouldn't call them a root server, but would agree with David's statement overall.<br>
><br>
> It is interesting to me that we are talking about this, and I feel lucky that really informed and experienced contributors are contributing.<br>
><br>
> Marilyn Cade<br>
><br>
> Sent from my iPad<br>
><br>
>> On Feb 24, 2014, at 11:44 AM, "David Conrad" <<a href="mailto:drc@virtualized.org">drc@virtualized.org</a>> wrote:<br>
>><br>
>> Elisabeth,<br>
>><br>
>>> On Feb 24, 2014, at 12:10 PM, Elisabeth Blanconil <<a href="mailto:info@vgnic.org">info@vgnic.org</a>> wrote:<br>
>>> Here is the distribution of the 365 top zone name servers (root servers)<br>
>><br>
>> I suspect creating a new term for the root name servers is unlikely to be helpful to anyone.<br>
>><br>
>>> made available by the two VGNICs I know of (ICANN/IANA and ORSN).<br>
>><br>
>> What's a "VGNIC"? I presume it is not the Network Information Center for the British Virgin Island (a la JPNIC, CNNIC, KRNIC, TWNIC, etc).<br>
>><br>
>>> They are broken down per countries as follows:<br>
>><br>
>> A graphical representation of root name server instance distribution can be found at:<br>
>><br>
>> <a href="http://www.root-servers.org/" target="_blank">http://www.root-servers.org</a><br>
>><br>
>> (Note that the location of the "B" root name server instance is not in the South Atlantic just off the coast of western Africa (Lat: 0, Lon: 0), but in Los Angeles, US).<br>
>><br>
>> Regards,<br>
>> -drc<br>
>><br>
>><br>
>> _______________________________________________<br>
>> discuss mailing list<br>
>> <a href="mailto:discuss@1net.org">discuss@1net.org</a><br>
>> <a href="http://1net-mail.1net.org/mailman/listinfo/discuss" target="_blank">http://1net-mail.1net.org/mailman/listinfo/discuss</a><br>
><br>
> _______________________________________________<br>
> discuss mailing list<br>
> <a href="mailto:discuss@1net.org">discuss@1net.org</a><br>
> <a href="http://1net-mail.1net.org/mailman/listinfo/discuss" target="_blank">http://1net-mail.1net.org/mailman/listinfo/discuss</a><br>
<br>
<br>
_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@1net.org">discuss@1net.org</a><br>
<a href="http://1net-mail.1net.org/mailman/listinfo/discuss" target="_blank">http://1net-mail.1net.org/mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>------------------------------------------------------------------------<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>
</blockquote></font><br>
</div></div>
</blockquote></div><br></body></html>