On Tue, 13 Nov 2012, Robin Whittle wrote:
https://www.ripe.net/ripe/mail/archives/address-policy-wg/2012-November/007374.html
then excluding "the top 10% of the v6 talkers", IPv6 traffic volumes are
an order of 1/100,000 of IPv4 traffic volumes.
Yes, that is the current state of affairs.
However, IPv6 is happening. There is no other plan, people are looking
into NAT44, NAT444 or equivalent, to bridge the gap until IPv6 is
supported on enough edge devices, so we then can go dual stacked
(basically add IPv6 to the beforementioned IPv4 infrastructure), and then
phase out IPv4 over time. People have stopped saying "if" and started
asking "how" and "when". This is a good sign.
It tooks us more than 10 years to get here. Anything being discussed right
now should look 10 years into the future and see itself influensing the
future, but rely on IPv6 in the current incarnation being the basic
infrastructure.
We already have multiple IPv4 mobility protocols. 3GPP style tunneling is
one (I've seen it being re-invented to handle large enterprise Wifi
networks, at least in the presentations it looks almost identical).
It's my strong opinion that anything that wants to get deployed in the
real world needs to be "compatible" with the basic IPv6 infrastructure as
seen today, and overlay on it somehow. It can be host-style like SHIM6, it
can be tunneling, it can be anything, but I firmly believe the core
routers need to stay the way they are right now when it comes to
destination based forwarding with the help of BGP.
The possibility to do rapid adoption of new tech on L3 is over. Anything
from now on needs to be able to get incrementally implemented using IPv6.
IPv4 is carrying the bulk of real life traffic but IPv6 is where everybody
is going, that's at least what I see from the operational world. So for
designing for the 3+ year future, IPv6 is what it needs to handle. Stop
beating the dying IPv4 horse, it's done a great job but it's being
replaced and from a design point of view, designing with IPv6 as a
requirement is a sane assumption.
--
Mikael Abrahamsson email: swm...@swm.pp.se
_______________________________________________
rrg mailing list
rrg@irtf.org
http://www.irtf.org/mailman/listinfo/rrg
