As part of the ongoing measurement of traffic in 1.0.0.0/8 three /24s from the range are shortly going to be announced by AARNet, via AS7575:
1.0.0.0/24
1.1.1.0/24
1.2.3.0/24
This will be happening over the next week or so.
cheers
-George
Hey George,
If AARNet or someone has the bandwidth, would it not be of value to announce the entire 1/8 and see what areas are targeted by traffic - clearly analysing it and removing DoS or scan traffic.
I'm just wondering if there are any /24's or space that is unsuitable to allocate inside 1/8.
...Skeeve
If only there was someone who pushed a whole lot of outbound data and had not really that much inbound - advertising 1/8 wouldn't really impact them that much. Some kind of, video sharing site, maybe?
route-views>sh ip bgp 1.0.0.0/8
BGP routing table entry for 1.0.0.0/8, version 600951180
Paths: (24 available, no best path)
Flag: 0x820
Not advertised to any peer
1239 174 36561
144.228.241.130 (inaccessible) from 144.228.241.130 (144.228.241.130)
Origin IGP, localpref 100, valid, external
% whois -a AS36561 | grep -i name
OrgName: YouTube, Inc.
http://www.merit.edu/mail.archives/nanog/msg06402.html
"Accordingly, APNIC authorizes AS36351 to periodically advertise a
route for 1.0.0.0/8 from now until 21 March 2010, and
requests that AS36351's peers and upstreams accept this as a
legitimate routing advertisement."
1.0.0.0/8 has been fun. I wont steal George/Geoff's show by telling
all... but I will state that about 18% of the internet is still bogon
filtering (or using internally) 1.x... I wouldn't want to be a poor
schlub getting assigned something from this space, personally.
We're going to announce 27.128.0.0/12 in the next 24 hours as well...
To see what backscatter is like in an uninteresting range. I'll send
a separate clear message to the list about this too.
,N