On 6to4 gateway and recommended MTU setting

Rickman, Phil phrickman at upcbroadband.com
Thu Mar 11 18:48:55 CET 2010

You cant go full native without massive application incompatibility
Embedded IPv4 addresses etc ... with only 5% of "potential" content available for standard users let alone IP based VPN clients, RDP, the list is endless of what breaks when you leave dual stack.  You also have issues with bi-directional routing, DR & LI, DNS64 preferences .....

And Holger is right 6rd has the same its own personal problems.

From: ipv6-ops-bounces+ipv6=aorta.net at lists.cluenet.de [ipv6-ops-bounces+ipv6=aorta.net at lists.cluenet.de] On Behalf Of holger.zuleger at vodafone.com [holger.zuleger at vodafone.com]
Sent: 11 March 2010 14:05
To: Jeroen Massar
Cc: Martin Millnert; ipv6-ops at lists.cluenet.de; ipv6-ops-bounces+holger.zuleger=arcor.net at lists.cluenet.de
Subject: Re: Re: On 6to4 gateway and recommended MTU setting

> The better question is actually: why bother with 6to4?
> Yes, it is a nice quick deployment strategy, but for anything long term,
> go native... (or at least native addresses using 6rd or something).
But with 6rd you will end up in the same discussion.


More information about the ipv6-ops mailing list