* Joe Baptista wrote:
The point of my letter is very clear. What happened? Who was affected? And what are the security repercussions to users world wide. So far ICANN has remained silent.
The problem is discussed in detail on dns-operators: https://lists.dns-oarc.net/pipermail/dns-operations/2010-March/thread.html#5... To summarize: a) An network (connected to the Internet) installed a blocking technology by intercepting DNS queries. The technical method used is local route injection. b) Due to an operational error, the injected route leaked to the Internet and caused to redirect parts of the Internet world to participate in the blocking project. Let's focus on ICANNs part and PLEASE move to technical-issues-WG. -> technical-issues@atlarge-lists.icann.org My understanding is, that a) is not within ICANNs remit because it's internal to the participating autonomous systems. Autonomous systems occur as plain points (without any internal structure) in the visible Internet. OTOH b) is a well known problem. Hijacking foreign IP space is unfortunely common and causes heavy headache by all involved operators. The SIDR-WG at IETF is working on a solution to prevent the negative impact of such operational errors. Hijacking of foreign ressources is clearly a topic on ICANNs agenda. So please come to the technical-issues-WG. BTW: I'm biased on SIDR: My personal impression is, that their solution is much to complex and hardly handled by current routers. So I put my own proposal into this group (which was immediately ignored).