[193975] in North American Network Operators' Group
Re: WEBINAR TUESDAY: Can We Make IPv4 Great Again?
daemon@ATHENA.MIT.EDU (Carsten Bormann)
Mon Mar 6 17:45:46 2017
X-Original-To: nanog@nanog.org
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5645714e-e468-4655-34cf-6e70aa7cfa26@gmail.com>
Date: Mon, 6 Mar 2017 23:45:39 +0100
To: Baldur Norddahl <baldur.norddahl@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
On 6 Mar 2017, at 22:00, Baldur Norddahl <baldur.norddahl@gmail.com> =
wrote:
>=20
> Encode extra address bits in extension headers. Add a network element =
near the destination that converts such that the destination IP of a =
packet to IP a.b.c.d with extension header containing e.f is translated =
to 192.168.e.f. In the reverse direction translate source address =
192.168.e.f to a.b.c.d and add option header with e.f.
6to4 essentially did this already. The main problem with 6to4 that made =
us stop using it was communicating to non-6to4 (=E2=80=9Cnative=E2=80=9D) =
IPv6 addresses; if you don=E2=80=99t want that, you have running code =
for both router and host side and plenty of gear that already works.
(All this is still complete nonsense in the face of accelerating native =
IPv6 adoption; I write this just to show that the idea already has been =
implemented out there.)
Gr=C3=BC=C3=9Fe, Carsten
