DoC will put IANA functions up for competitive bid

Private Address Space from ARIN, etc. Public Address Space from the FCC and U.S. Telcos Many ISPs only have Private Address Space and that is not Guaranteed to be Routable. Ask ARIN. > The registries (including IANA as their root) should provide just > that, a place to register the use of number resources to avoid collisions. > I'm thinking that "private" number spaces should probably be used > advisedly if not deprecated outright. RIR's are taking heat (or some finger pointing atleast) for allocations that don't appear in the public route table. There are many reasons why the allocation might not appear in the table, I'm not convinced that measuring the public table is any real way to measure 'in use' status for ip space, though it's one gauge people seem to be using. If there is a legittimate need to use some ip space NOT in a public manner, one for which 1918 might not be appropriate, perhaps having a registration method 'in region' (with the RIR's who already have the machinations to do ip number registrations and delegations) would make some sense? I recall, I believe, a policy proposal 1 or 2 ARIN's ago that would have included some form of 'private' or 'public' stamp/category on ip registration data? Perhaps reviving that, or making a new one, would be in order? How do the currently allocated folks feel about sending in registration info now? Assume no payment, or minimum payment for registration 'work' in included? Would we be able to get all of the relevant parties to sign up/register/keep-up-to-date ? Example registered but not 'routed': 7.0.0.0/8 Would we want to change whois output to include the 'pub/priv' flag?

[ Reply to This | Parent ]

Re:On U.S. Telcos and FCC Draining the IANA Swamp by Anonymous

Re:On U.S. Telcos and FCC Draining the IANA Swamp
by Anonymous on Monday November 14 2005, @04:13AM (#16498)

This particular /8 allocation is described by IANA as "007/8 Apr 95 IANA - Reserved" in http://www.iana.org/assignments/ipv4-address-space while a whois query to the ARIN database reveals:

$ whois 7.0.0.0

OrgName: DoD Network Information Center
OrgID: DNIC
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US

NetRange: 7.0.0.0 - 7.255.255.255
CIDR: 7.0.0.0/8
NetName: DISANET7
NetHandle: NET-7-0-0-0-1
Parent:
NetType: Direct Allocation
Comment: Defense Information Systems Agency
Comment: DISA /D3
Comment: 11440 Isaac Newton Square
Comment: Reston, VA 22090-5087 US
RegDate: 1997-11-24
Updated: 1998-09-26

RTechHandle: MIL-HSTMST-ARIN
RTechName: Network DoD
RTechPhone: +1-800-365-3642
RTechEmail: HOSTMASTER@nic.mil

OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: +1-800-365-3642
OrgTechEmail: HOSTMASTER@nic.mil

# ARIN WHOIS database, last updated 2005-11-12 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.

So in this case who is telling the truth? IANA or ARIN? Is this, as ARIN data is claiming, an address block that is currently allocated to the US Dept of Defense via a "direct allocation" (by IANA presumably, but unspecified in any case), or is this, as IANA data is claiming, an address block that is currently in the IANA reserved pool and can be allocated to an RIR in the future. Go figure.

[ Reply to This | Parent ]

who is telling the truth? IANA or ARIN? by Anonymous Monday November 14 2005, @04:18AM

Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com