[111225] in North American Network Operators' Group
Re: Private use of non-RFC1918 IP space
daemon@ATHENA.MIT.EDU (Jeroen Massar)
Mon Feb 2 11:08:40 2009
Date: Mon, 02 Feb 2009 17:07:50 +0100
From: Jeroen Massar <jeroen@unfix.org>
To: trey@kingfisherops.com
In-Reply-To: <55945.192.101.252.156.1233589709.squirrel@kingfisherops.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigFB70323F0FE6FC952F632F46
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Trey Darley wrote:
> Hi, y'all -
>=20
> 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 i=
n
> question is strictly closed I don't anticipate any problems with this a=
s
> the addresses would be unambiguous within our environment. I'm curious =
if
> anyone else is doing this.
Of course you can use public address space, and actually you should have
been doing that already for years.
The catch is of course that you just get it from your local RIR or LIR,
thus making sure it is globally unique, as that is where the problem of
RFC1918 lies for most people.
Another trick is of course to start moving to IPv6: get a /48 or more
from your local LIR/RIR and you have all the IPs you will ever need
(unless you plan wrong and ask for too little ;)
Greets,
Jeroen
--------------enigFB70323F0FE6FC952F632F46
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFJhxpWKaooUjM+fCMRAtvlAJsFtGxEsq3Nb/LdUsCDsTkBdZzkMACfTZaO
jcVHfHQouUJ9fOtnTotWM80=
=Bjw9
-----END PGP SIGNATURE-----
--------------enigFB70323F0FE6FC952F632F46--
