Re: IPv6 allocation plan, security, and 6-to-4 conversion

[Baldur Norddahl <baldur.norddahl () gmail com>]

We are talking about different things. If your business is servers, do
whatever you want. If you are in the business of selling internet, which
quite a few are on this mailinglist, you need to be dual stack.

We are dual stack towards our customers. On our internal network we are
single stack - ipv4 only. This is a new build. Why? Because half of our
equipment does not support ipv6 management and even some of the network
protocols will not function without ipv4 (MPLS). Adding ipv6 to the
internal network seems to have no purpose. It is all private address space
with not even NAT. The internal network is not directly connected to the
internet, so there is no need.

Regards,

Baldur
Den 30/01/2015 21.23 skrev "Tore Anderson" <tore () fud no>:

> * Baldur Norddahl
>
> > Single stacking on IPv6 is nice in theory. In practice it just doesn't
> work
> > yet. If you as an ISP tried to force all your customers to be IPv6 single
> > stack, you would go bust.
>
> Kabel Deutschland, T-Mobile USA, and Facebook are examples of companies
> who have already or are in the process of moving their network
> infrastructure to IPv6-only. Without going bust.
>
> What you *do* need, is some form of connectivity to the IPv4 internet.
> But there are smarter ways to do that than dual stack. Seriously, if
> you're building a network today, consider making IPv4 a legacy "app" or
> service running on top of an otherwise IPv6-only infrastructure. Five
> years down the road you'll thank me for the tip. :-)
>
> Tore