CircleID

> These include TCP/IP, SMTP, HTTP, BIND, BGP, and the DNS (especially the .com registry).

I'd say there's a fundamental flaw in this sentence: a protocol implementation (bind) in the list of protocols. (tcp/ip, smtp, http, bgp)

Also, the Internet is a fancy project, where normal upgrades and refactorings are not possible, or very hard to manage - but dwelling on stuff that was built decades of years and several digital generations ago is not normal. For example, there are several things in dns that was OK back in 1980s (max udp package size, really freaky name packing and bitfields) but really not reasonable now. One can't build a Ferrari from an old Trabant by adding pieces of a new Ferrari to it. Eventually the cartong of the trabant will collapse under the weight of ferrari addons attached to it. The same goes with dns (and other core networking protocols). We live in the world where bandwidth can handle both bytes and kilobytes, processor cycles are cheaper than programmers - so counting bits and programming in assembler for maximum performance is not very wise. Internet is global and unicode is common - although the IDN hack is a smart hackup and it's good to make money from it while it's still possible. The breakthrough has to come sometime soon - when i can send a 'TODO note' (xml) in russian letters(unicode), to my business parnters mobile phone (what i located using dns) over the ipv6 network.