February 2010 - At-Large - lists.icann.org

Offlist : Google Code Blog : A proposal to extend the DNS protocol
by Sivasubramanian Muthusamy Feb. 6, 2010

Feb. 6, 2010

Hello Patrick Vande Walle On Fri, Feb 5, 2010 at 11:22 PM, Patrick Vande Walle <patrick(a)vande-walle.eu> wrote: > > On 05 Feb 2010, at 17:47, Michele Neylon :: Blacknight wrote: > The fact most of them are paid full time by a company for doing exactly that, and submit documents that closely follow the company's strategy is a pure coincidence. :-) Which company? I am a little curious. Shiva. > > -- > Patrick Vande Walle

1 0

Google Code Blog : A proposal to extend the DNS protocol
by Dev Anand Teelucksingh Feb. 5, 2010

Feb. 5, 2010

A proposal to extend the DNS protocol Wednesday, January 27, 2010 Today a group of DNS and content providers, including Neustar/UltraDNS and Google are publishing a proposal to extend the DNS protocol (http://www.ietf.org/id/draft-vandergaast-edns-client-ip-00.txt) DNS is the system that translates an easy-to-remember name like www.google.com to a numeric address like 74.125.45.104. These are the IP addresses that computers use to communicate with one another on the Internet. By returning different addresses to requests coming from different places, DNS can be used to load balance traffic and send users to a nearby server. For example, if you look up www.google.com from a computer in New York, it may resolve to an IP address pointing to a server in New York City. If you look up www.google.com from the Netherlands, the result could be an IP address pointing to a server in the Netherlands. Sending you to a nearby server improves speed, latency, and network utilization. Currently, to determine your location, authoritative nameservers look at the source IP address of the incoming request, which is the IP address of your DNS resolver, rather than your IP address. This DNS resolver is often managed by your ISP or alternately is a third-party resolver like Google Public DNS. In most cases the resolver is close to its users, in which case the authoritative nameservers will be able to find the nearest server. However, some DNS resolvers serve many users over a wider area. In these cases, your lookup for www.google.com may return the IP address of a server several countries away from you. If the authoritative nameserver could detect where you were, a closer server might have been available. Our proposed DNS protocol extension lets recursive DNS resolvers include part of your IP address in the request sent to authoritative nameservers. Only the first three octets, or top 24 bits, are sent providing enough information to the authoritative nameserver to determine your network location, without affecting your privacy. Read full article : http://googlecode.blogspot.com/2010/01/proposal-to-extend-dns-protocol.html

2 1

Weekly posting summary for alac@atlarge-lists.icann.org
by Thomas Narten Feb. 5, 2010

Feb. 5, 2010

Total of 11 messages in the last 7 days. script run at: Fri Feb 5 00:53:05 EST 2010 Messages | Bytes | Who --------+------+--------+----------+------------------------ 18.18% | 2 | 19.21% | 14946 | baptista at publicroot.org 18.18% | 2 | 12.46% | 9695 | johnl at iecc.com 9.09% | 1 | 14.93% | 11616 | tropology at gmail.com 9.09% | 1 | 11.49% | 8937 | namecritic at blogs.pn 9.09% | 1 | 10.50% | 8170 | franck.martin at gmail.com 9.09% | 1 | 8.59% | 6680 | devtee at gmail.com 9.09% | 1 | 8.58% | 6675 | sebastien at bachollet.com 9.09% | 1 | 8.03% | 6249 | narten at us.ibm.com 9.09% | 1 | 6.21% | 4830 | carlton.samuels at gmail.com --------+------+--------+----------+------------------------ 100.00% | 11 |100.00% | 77798 | Total

1 0