[123962] in North American Network Operators' Group
Re: Using private APNIC range in US
daemon@ATHENA.MIT.EDU (Jonathan Lassoff)
Thu Mar 18 13:18:44 2010
From: Jonathan Lassoff <jof@thejof.com>
To: Jaren Angerbauer <jarenangerbauer@gmail.com>
In-reply-to: <4c6b8c911003180922j426f6e94g37eb772210a249f8@mail.gmail.com>
Date: Thu, 18 Mar 2010 10:16:21 -0700
Cc: nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Excerpts from Jaren Angerbauer's message of Thu Mar 18 09:22:40 -0700 2010:
> Thanks all for the on / off list responses on this. I acknowledge I'm
> playing in territory I'm not familiar with, and was a bad idea to jump
> to the conclusion that this range was private. I made that assumption
> originally because the entire /8 was owned by APNIC, and just figured
> since the registrar owned them, it must have been a private range. :S
>
> It sounds like this range was just recently assigned -- is there any
> document (RFC?) or source I could look through to learn more about
> this, and/or provide evidence to my client?
There's a couple of relevant documents you could refer them to:
IANA's IPv4 Address Space Registry ( http://www.iana.org/assignments/ipv4-address-space/ ),
which will show you a listing of which registries and various entities
are assigned /8 chunks of IPv4 space.
There's some interesting names and historical registrations in there
(including 1.0.0.0/8's recent allocation to APNIC)
There's also an RFC, RFC1918 that sets aside some IPv4 space for
private, ad-hoc use.
http://www.faqs.org/rfcs/rfc1918.html
This is also a good lay reference:
http://en.wikipedia.org/wiki/Private_network
Have fun,
jof
