1st meet of Wed, 12:45PM, 1st line of lunch tables

[Tina TSOU]

Problem Statement:
IPv4 addresses are limited. As of today, IANA's IPv4 address pool is
down to 16 blocks of /8. The current projection [ref to
ipv4.potaroo.net]
is that IANA will exhaust this pool in less than a year, with the RIRs
allocating all their remaining blocks in January 2012.
IPv6 is the next generation IP protocol which
will solve the address exhaustion problem. IPv4 and IPv6 are not
interoperable and the uptake of IPv6 in client and server nodes will
be
gradual. An ISP will need to take steps to ensure service
continuity and transparency to the customers at all times during
transition and coexistence.

IETF working groups have defined several
techniques to address IPv6 transition and coexisence. The various
techniques address different
deployment secnarios and give different results. Many ISPs are
confused
and seek guidance to decide what
steps and technologies are best fit to their networks.

For example: An ISP uses DSL to provide Internet service to the
customers. It gives one public IPv4 address for its customers. The
ISP engineer team knows that long term they will need to transition
to IPv6 to resolve the IPv4 exhaustion problem. However, they don't
know how to address the short term problem and start the
transitioning without service interruption. Should they deploy NAT-
444 and incrementally upgrade the access network to IPv6 to migrate
to DS-lite? If they deploy NAT-444 today, what design guidelines
they need to consider and what operation issues they need to pay
attention? When they deploy DS-lite tomorrow, what are the steps to
migrate from NAT-44 to DS-lite? Similar questions will be asked
when
they analyze NAT64 and 6RD.

This memo attempts to describe the common problems stopping ISP to
start the transitioning and provide guidance for applying the
available
transition and coexistence techniques in an ISP network.

[Lee, Yiu]

Here we go.

[Fred Baker]

Hi. I'm here. Where are you?

http://www.ipinc.net/IPv4.GIF