IPv4 Markets |
Sponsored by |
There's a great fight going on right now in Philadelphia...The case is about a Pennsylvania statute [PDF] that mandates that Pennsylvania ISPs remove access to sites that the AG believes contain child pornography. Now, child pornography is abhorrent and any ISP will cooperate in taking down such sites that it is hosting. But the problem is that in complying with the statute with respect to sites the ISPs don't themselves host, ISPs are (rationally) using either IP blocking ("null routing") or "domain poisoning" techniques, both of which (particularly the IP number blocking) result in rendering inaccessible millions of perfectly legal sites.
RFID tags, UPC codes, International characters in email addresses and host names, and a variety of other identifiers could all go into DNS, and folks have occasionally proposed doing just that. Its really just a question of figuring out how to use the DNS -- its ready to carry arbitrary identifiers. And by the way, this isn't a new idea, see RFC 1101 for proof, although even earlier I designed the DNS in the early 1980s to allow it to be so, but it seemed too far fetched to document for a while. ...I was in Geneva for a WSIS meeting of CTOs, and was surprised that the various organizations (ITU, ICANN, ISOC) haven't figured out that they need each other to make this technology work, rather than asserting ownership.
I've been following the recent news on the World Summit on the Information Society, and it's getting really bizarre. The Wired article is one example of out of the out-of-this-world coverage on the World Summit; I heard a similar spin yesterday on a radio show that often shares material with the BBC. What king or dictator or bureaucrat has signed the document giving power over the Internet to one organization or another? Did I miss the ceremony? One laughable aspect of news reportage is that the founders and leaders of ICANN always avowed, with the utmost unction, that they were not trying to make policy decisions and were simply tinkering with technical functions on the Internet.
If you analyze the relay of spam- and malware-containing email circulating on the Internet purely through your mail server logs (running the Unix command "tail"), a large proportion seem to come from Asia Pacific hosts, especially those from mainland China. Therefore, many less-experienced systems administrators have simply blocked the access from subnets of Chinese or Asian origin, effectively destroying the fabric of the Internet -- messaging. If administrators took pains to analyze these supposedly Asian spam messages by analyzing the full Internet headers, they would have realized that the Asian servers were merely used by the real spammers as open relays, or perhaps as zombie hosts previously infected with the mass mailing worms through the exploitation of operating system vulnerabilities.
Here's a good way to frighten yourself: Learn about something, and then read what the press writes about it. It's astonishing how often flatly untrue things get reported as facts. I first observed this back in 1997 when I was a Democratic lawyer in the U.S. House of Representatives working on the (rather ridiculous) campaign finance investigation. (The investigating committee's conspiracy-minded chairman was famous for shotgunning pumpkins in his backyard in order to figure out exactly how Hillary snuffed Vince Foster)...More recently, I've seen the same discouraging phenomenon in reporting on technology and, in particular, the Internet.
Fueled by the lack of public IP addresses, 70% of Fortune 1000 companies have been forced to deploy NATs (Source: Center for Next Generation Internet). NATs are also found in hundreds of thousands of small business and home networks where several hosts must share a single IP address. It has been so successful in slowing the depletion of IPv4 addresses that many have questioned the need for IPv6 in the near future. However, such conclusions ignore the fact that a strategy based on avoiding a crisis can never provide the long-term benefits that solving the underlying problems that precipitated the crisis offers.
An article based on the most recent study for the European Commission on the Policy Implications of Convergence in the Field of Naming, Numbering and Addressing written by Joe McNamee and Tiina Satuli of Political Intelligence.
"With relation to the Internet and also IP addresses, the "scarcity" is more complicated: there are not only intellectual property issues with regards to domain names, but there is also an issue of managing the integrity of the system. For any naming or numbering system to work, it is essential that the names and addresses used cannot be confused with any other -- in other words, no one system can have two end-points with the same fully qualified number or name..."
This is a special two-part series article providing a distinct and critical perspective on Internet Protocol Version 6 (IPv6) and the underlying realities of its deployment. The first part gives a closer look at how IPv6 came about and the second part exposes the myths.
In January 1983, the Advanced Research Projects Agency Network (ARPANET) experienced a "flag day," and the Network Control Protocol, NCP, was turned off, and TCP/IP was turned on. Although there are, no doubt, some who would like to see a similar flag day where the world turns off its use of IPv4 and switches over to IPv6, such a scenario is a wild-eyed fantasy. Obviously, the Internet is now way too big for coordinated flag days. The transition of IPv6 into a mainstream deployed technology for the global Internet will take some years, and for many there is still a lingering doubt that it will happen at all.
There are indications that the Internet, at least the Internet as we know it today, is dying. I am always amazed, and appalled, when I fire up a packet monitor and watch the continuous flow of useless junk that arrives at my demarcation routers' interfaces. That background traffic has increased to the point where it makes noticeable lines on my MRTG graphs. And I have little reason for optimism that this increase will cease. Quite the contrary, I find more reason to be pessimistic and believe that this background noise will become a Niagara-like roar that drowns the usability of the Internet. And the net has very long memory...
The IPv6 Forum, the North American IPv6 Task Force, and Charmed Technology, Inc. today announced that the U.S. IPv6 Summit 2003 will be held December 8 - 11, 2003 in Arlington, VA, at the Doubletree Crystal City. The U.S. IPv6 Summit 2003 will focus on deployment, technical depth of key IPv6 features, and applications or services of Internet Protocol version 6 (IPv6).