[111228] in North American Network Operators' Group
RE: Private use of non-RFC1918 IP space
daemon@ATHENA.MIT.EDU (Skywing)
Mon Feb 2 11:15:20 2009
From: Skywing <Skywing@valhallalegends.com>
To: "trey@kingfisherops.com" <trey@kingfisherops.com>, "nanog@nanog.org"
<nanog@nanog.org>
Date: Mon, 2 Feb 2009 10:14:54 -0600
Errors-To: nanog-bounces@nanog.org
If you get an address reservation from a registry, then you could certainly=
use that space in a way that doesn't entail globally-reachable routing. I=
n fact, IIRC one of the RFCs explicitly mentions this possibility in the ev=
ent that overlapping private use address space usage makes interconnection =
between two networks otherwise unworkable.
However, as everyone else had assumed you might be doing, "borrowing" unass=
igned or assigned-to-someone-else (for which all "unassigned" can eventuall=
y be expected to devolve into) is unwise.
=96 S
-----Original Message-----
From: Trey Darley <trey@kingfisherops.com>
Sent: Monday, February 02, 2009 07:48
To: nanog@nanog.org <nanog@nanog.org>
Subject: Private use of non-RFC1918 IP space
Hi, y'all -
Some colleagues and I are running into a bit of a problem. We've been
using RFC 1918 Class A space but due to the way subnets have been
allocated we are pondering the use of public IP space. As the network in
question is strictly closed I don't anticipate any problems with this as
the addresses would be unambiguous within our environment. I'm curious if
anyone else is doing this.
I'd be very interested in corresponding off-list with anyone who's in a
similar position.
Cheers,
--Trey
++-------------------------------------------------------------------------=
---++
Kingfisher Operations
Trey Darley - Principal
