[99557] in North American Network Operators' Group
Re: WG Action: Conclusion of IP Version 6 (ipv6)
daemon@ATHENA.MIT.EDU (Jeroen Massar)
Fri Sep 28 03:48:01 2007
Date: Fri, 28 Sep 2007 08:45:20 +0100
From: Jeroen Massar <jeroen@unfix.org>
To: "Steven M. Bellovin" <smb@cs.columbia.edu>
CC: nanog@nanog.org
In-Reply-To: <20070928021130.7eac389a@berkshire.machshav.com>
Errors-To: owner-nanog@merit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6B9153E06F0C8890B28D6511
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Steven M. Bellovin wrote:
[..]
> IPv6 isn't what I wanted it to be. During the IPng directorate,
> several of us (including me and at least one of the chairs) pushed very=
> hard for id/locator split. We lost. That was 1994; it's over and done=
> with. But it took 13 years from then to a (mostly) complete set of
> specs and universal implementation, at least in all systems shipping
> today.
[..]
The good thing about the current state of IPv6 is though that
applications have the following:
- 128bits source address
- 128bits destination address
and in many cases they are now also AF independent due to getaddrinfo(),
though there will always be some dependent code in their unfortunately.
Why is the above good? Well, the application doesn't further really care
about how the packets are sent from source to destination. As such those
bits are now identifiers already. The OS can change them and do whatever
it wants with them, eg it could change them to something which is
available only on the link, tell the other end to do the same when it
receives them to make them identical when sent from the source applicatio=
n.
This should provide for a pretty good outcome in a couple of years where
next the second biggest "problem" of the current Internet will be solved
(the first being 32bits not being enough to address all hosts): too many
DFZ routes.
That will require a id/locator split, or IMHO better mentioned using
those 128bits as both ID's and locators. It will need a signaling
protocol for mentioning when something is an ID and when something is a
locator and how to get back to an ID, but that magic should not be too
hard to do and can be done both in the endhost and in middle boxes.
As such, IPv6 has already solved the currently biggest problem: there is
enough address space. Applications are mostly ready for this and so are
Operating Systems. Now the web should follow, and while the IPv6 DFZ
grows (it is still <900 routes) we will have enough time to create the
ID/LOC system that ISP operators and Enterprise operators will accept.
Especially that 'acceptance' is a big problem it seems and that is mosly
a political issue, not a technical one.
Btw, ram@iab.org if you want to join in on those discussions.
Greets,
Jeroen
--------------enig6B9153E06F0C8890B28D6511
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)
Comment: Jeroen Massar / http://unfix.org/~jeroen/
iHUEARECADUFAkb8sRYuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I0BvAJ91ml0vo5Se0CkU/aK5J2wo0rmU
6QCgvegNDe1ll653pZgw9JZ1L9aLWK0=
=RNUe
-----END PGP SIGNATURE-----
--------------enig6B9153E06F0C8890B28D6511--
