IPv6 allocation plan, security, and 6-to-4 conversion
elouie at techintegrity.com
Sat Jan 31 01:05:37 UTC 2015
And, we're in sort of the same predicament - I have no choice on the
current infrastructure but to run IPv4. IPv6 is a service we would like to
start to offer to new customers in this current infrastructure. And to
existing customers who believe that they have the need for IPv6 and have
the equipment in their network to support it.
We may end up as IPv6-only on the customer side in new markets because we
don't have enough PUBLIC IPv4 address space to support a new market, but
that will STILL require private IPv4 for management and monitoring of the
equipment that does not support IPv6 yet. (and yes, there's a lot of
equipment that is greater than 2 years old that still works and that does
not support IPv6)
eric at techintegrity dot com
619-335-8148 voice & text
ericlouie on Twitter
On Fri, Jan 30, 2015 at 4:54 PM, Baldur Norddahl <baldur.norddahl at 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.
> Den 30/01/2015 21.23 skrev "Tore Anderson" <tore at 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
> > > 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
More information about the NANOG