Private use of non-RFC1918 IP space
thegameiam at yahoo.com
Mon Feb 2 11:59:05 CST 2009
--- On Mon, 2/2/09, Patrick W. Gilmore <patrick at ianai.net> wrote:
> > Most ISP's, if not all, null route 220.127.116.11/8 therefore
> you shouldn't
> > encounter any problems using it in a private network.
> Until IANA runs out and gives that space to Google or MS or
> Comcast or $WHATEVER_THAT_NETWORK_TALKS_TO.
It all comes down to "what do you mean by 'private network'" doesn't it?
If you operate an IP network which is air-gapped from all other IP networks, which IP address you use is irrelevant. If that network interconnects with (only) a provider/customer using RFC 1918 space, you either have to coordinate with them, NAT, or use non-RFC 1918 space.
If you run a network which should only communicate with others through a proxy/firewall/NAT device, how much does it matter what's on the inside?
Of course, the risk of using IP addresses which are not uniquely assigned to you is that there will be an overlap somewhere. Whether the risk is greater inside or outside of RFC 1918, I leave for others to puzzle out (although it should be noted that organizational M&A activity makes hash of the best-laid IP address schema).
Need Geek Rock? Try The Franchise:
More information about the NANOG