There are sizable chunks that are fairly quiet (un-interesting numbers, luck of the draw, etc). Given that its mostly mis-configurations, laziness, ignorance, or poor planning... I suspect the worst ranges will need to be sacrificed, and the remaining 80-90% of the space used for legitimate allocations. Unfortunately, anyone who accepts allocations in 1.x will need to be aware that they will have a slightly lower quality address-space. Accepting 1.1.1.0/24, for example, will land you with a continuous 50mbps of junk... seemingly forever... and a respectable chance that some percentage of the net will never reach you, due to their own misconfigurations. ,N On Fri, Mar 12, 2010 at 1:34 PM, Kevin Loch <kloch@kl.net> wrote:
Axel Morawietz wrote:
Am 12.03.2010 17:03, schrieb Nathan:
[...] Its amazing how prolific 1.x traffic is.
one reason might also be, that at least T-Mobile Germany uses 1.2.3.* for their proxies that deliver the content to mobile phones. And I'm not sure what they are doing when they are going to receive this route from external. ;)
If 1.0.0.0/8 has been widely used as de-facto rfc1918 for many years, perhaps it is time to update rfc1918 to reflect this?
- Kevin