[124940] in North American Network Operators' Group

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

RE: ARIN IP6 policy for those with legacy IP4 Space

daemon@ATHENA.MIT.EDU (Deepak Jain)
Wed Apr 7 18:33:59 2010

From: Deepak Jain <deepak@ai.net>
To: Lee Howard <lee@asgard.org>, "'Gary E. Miller'" <gem@rellim.com>, 'Owen
	DeLong' <owen@delong.com>
Date: Wed, 7 Apr 2010 18:31:25 -0400
In-Reply-To: <003001cad69e$b61d97d0$2258c770$@org>
Cc: 'NANOG list' <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


Now I may be talking crazy...=20

IIRC, all of IPv4 space maps to a section of IPv6 space.=20

<mad hat on>

If one has legacy IPv4 space, but actually talks IPv6 couldn't one announce=
 a prefix much longer than a /64 to map them onto the IPv6 universe (assumi=
ng people would allow such craziness... perhaps on their IPv4 speaking rout=
ers) and originate/terminate traffic as normal?=20

</mad hat off>

Isn't this all left to the networks to enforce, as usual, but unlike the st=
atus quo, these are all valid allocations...

Technical note: I know this breaks lots of IPv6 goodness (no need to enumer=
ate it here).

DJ



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