[86637] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: IAB and "private" numbering

daemon@ATHENA.MIT.EDU (Jeroen Massar)
Sat Nov 12 12:55:04 2005

Date: Sat, 12 Nov 2005 18:53:47 +0100
From: Jeroen Massar <jeroen@unfix.org>
To: bmanning@vacation.karoshi.com
Cc: "Christopher L. Morrow" <christopher.morrow@mci.com>,
	nanog@nanog.org
In-Reply-To: <20051112172455.GC12051@vacation.karoshi.com.>
Errors-To: owner-nanog@merit.edu


This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig19DB955193E16A5FFE1B89E3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

bmanning@vacation.karoshi.com wrote:
> On Sat, Nov 12, 2005 at 04:40:20PM +0000, Christopher L. Morrow wrote:
>>
>> On Fri, 11 Nov 2005, Tony Tauber wrote:
>>> The registries (including IANA as their root) should provide just
>>> that, a place to register the use of number resources to avoid collis=
ions.
>>> 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 allocation=
s
>> that don't appear in the public route table. There are many reasons wh=
y

A prefix doesn't have to reside in this beast called 'DFZ' for to be
used. There is (atm) no need for one to announce the address space used
by their cool chocolate factory machines, but maybe in the future one
might want to do it to be able to monitor from the comfort of ones home.
Thus the address space does need to be globally unique.

> i rant, yet again. =20
>=20
> 	what is this "the" public routing table?  where does one
> 	get it?  in my 25 years of networking I have NEVER seen it.

Have you seen the moon? Touched it? I still can't be convinced that
pluto exists, I haven't seen it, but it appears to be there ;)

> 	i am convinced that it is a fictional as the "public" Internet.
> 	or the "DFZ" ... they do not exist, except in the fevered=20
> 	imaginations of marketing droids... and the virus is more virulent
> 	than the H5N1 strain.  Note that it affects normally sane engineers
> 	who KNOW better.

Well I apparently have a lot of nasty viruses floating around in my body
at http://www.sixxs.net/tools/grh/dfp/ I used "DFP" with which I mean:

"Default Free Prefix, a prefix routed without having any smaller
prefixes covering it. Removing such a prefix will make the
prefix unreachable."

DFZ would be the group of all DFP's.

> 	back in the SRInic days, there was the "connected" and "unconnected"
> 	databases.  ... to mark prefixes that were connected to the ARPAnet
> 	and those that were in "private" networks, like CSnet, NSFnet, and
> 	enterprise networks.  Tony is right in this respect, RFC1918 space
> 	is a feeble attempt to get around/past the lack of address space
> 	that became apparent in IPv4 ... with IPv6, there is no real=20
> 	reason to try and recreate private space (leaving aside renumbering)

Indeed.

> 	IMHO, assigning globally unique prefixes to those who utilize IP
> 	protocols, regardsless of whom else they choose to "see" via routing
> 	is the right course.  every other attempt to split the assignements
> 	into "us" vs. "them" has had less than satisfactory results.

Absolutely. Address space is there to address hosts and thus should be
made available to places that have a hosts.

The only issues at a certain point will become routing table size and
that is the new problem to fix, there is now "enough" address space.
(Taking into consideration that 2000::/3 is only 1/8th of the total IPv6
address space and that we can peep up 8 times before it runs out :)

Greets,
 Jeroen


--------------enig19DB955193E16A5FFE1B89E3
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.2 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQFDdiwwKaooUjM+fCMRAvK6AJ9LcFZ9SPbhQxvNbEDzHWJ0sYvH2ACgmJBu
zmm6BwqaCrqgocueGVUlIoI=
=R7Y6
-----END PGP SIGNATURE-----

--------------enig19DB955193E16A5FFE1B89E3--

home help back first fref pref prev next nref lref last post