132.0.0.0/10 is floating around:
route-views.oregon-ix.net>show ip bgp 132.0.0.0/10
BGP routing table entry for 132.0.0.0/10, version 12484641
Paths: (43 available, best #41)
Advertised to non peer-group peers:
64.166.72.140
4513 13646 5696 568, (aggregated by 568 198.26.128.1)
195.66.224.82 from 195.66.224.82 (209.10.12.222)
Origin IGP, metric 7602, localpref 100, valid, external, atomic-aggregate
[snip, route-views has more than a page of entries for it]
However, it doesn't apprar to be registered:
% whois -h whois.arin.net 132.0.0.0
No match for "132.0.0.0".
568 regisitered to disa.mil, and a number of longer prefixes
inside the /10 are registered to .mil addresses:
% whois -h whois.arin.net 132.15.0.0
Kadena Air Base (NET-KADENA-NET)
Bldg 792, Kadena AB JA
APO, AP 96368-5149
US
The question is, do they legitimately own the whole /10? If
so, why isn't it marked in the databases?
Says who ? - maybe you didn't check the right one ?
whois -h whois.radb.net 132.0.0.0
route: 132.0.0.0/10
descr: DISA, DSAC
P. O. Box 1605
Columbus
OH 43216-5002, USA
origin: AS568
member-of: RS-COMM_US_FED
mnt-by: MAINT-AS568
changed: nsfnet-admin@merit.edu 19940819
source: RADB
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
radb is a routing database, has nothing to do with ownership of ip
space.
- --
Matt Levine
@Home: matt@deliver3.com
@Work: matt@eldosales.com
ICQ : 17080004
PGP : http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0D04CF
"The Trouble with doing anything right the first time is that nobody
appreciates how difficult it was."
Perhaps I should restate my complaint a bit. I think all three
of these stand on their own.
* If sub-bits of an allocation are in the ARIN database,
I think the supernet should be in the ARIN database.
* ARIN seems to have a good many, if not all of the .MIL
supernets, but doesn't have this one.
* Having .MIL say they have address space is not proof
that they own the whole block, anymore than www.ufp.org saying
I now own 20 class A's is proof that they are mine.
In any event, I'd just like network lookups to work in some sane
way, so when operators need to check something they can get accurate
results.
My theory is that DISO-UNRRA were originally allocated 132.1.0.0/16 through 132.15.0.0/16 in the classful world - these are all in the ARIN DB under various military guises. When CIDR came along, it seems that someone must have decided that because 132.0.0.0/16 was now available and part of a bigger block, it could be added to the announcement, etc...?
There are a total of four like this:
Network Origin AS Description
132.0.0.0/10 568 DISO-UNRRA
135.0.0.0/13 10455 Lucent Technologies
137.0.0.0/13 568 DISO-UNRRA
158.0.0.0/13 568 DISO-UNRRA
Just a theory - but the above 4 could do with the x.0.0.0/16 being put in ARIN's db, if the allocation can be proven...
philip