They are not bogus, hence the sub-deligation, and hence a good reason to have a more detailed source of information.
I would suspect that this block should be "chopped" a bit to reflect the IANA/ICANN usage. This block was first routed on the internet via AS 226 around late summer early fall 1999. On Wed, Sep 04, 2002 at 10:08:00AM -0400, David Charlap wrote: > > John M. Brown wrote: > > > > In the last 72 hours I've seen over 3GB of data hit a network > > I play with with source IP's of IANA-RESERVED space. > > Just out of curiosity, do you know that these are bogus source > addresses? Some of the IANA-RESERVED block is actually valid and is > used by IANA's computers. > > My company was blocking all of the IANA-RESERVED space for a while, > until we discovered that the IANA web server is using an address in that > space. > > Note: > $dig www.iana.org a > > ; <<>> DiG 2.0 <<>> www.iana.org a > ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6 > ;; flags: qr rd ra ; Ques: 1, Ans: 1, Auth: 6, Addit: 6 > ;; QUESTIONS: > ;; www.iana.org, type = A, class = IN > > ;; ANSWERS: > www.iana.org. 68055 A 192.0.34.69 > ... > > and: > $whois -h whois.arin.net 192.0.34.69 > IANA RESERVED-192 (NET-192-0-0-0-1) > 192.0.0.0 - 192.0.127.255 > ICANN > c/o Internet Assigned Numbers Authority ICANN (NET-192-0-32-0-1) > 192.0.32.0 - 192.0.47.255 > > > Various people have reported seeing IANA-RSERVED get announced > > via BGP at different parts of the net. > > Again, bogus addresses or legitimate IANA servers? Not everything in > IANA-RESERVED is bogus. > > -- David >
