Thanks for your explain, please see inline.
Regards
Xiangsong
----- Original Message -----
From: "Cameron Byrne" <[email protected]>
To: "Xiangsong Cui" <[email protected]>
Cc: "Nick Heatley" <[email protected]>; "Hui Deng" <[email protected]>; "Sri Gundavelli" <[email protected]>;
<[email protected]>; <[email protected]>
Sent: Friday, December 04, 2009 1:25 PM
Subject: Re: [Softwires] Transition roadmap // Re: Host based translation: v4-v6
On Thu, Dec 3, 2009 at 9:16 PM, Xiangsong Cui <[email protected]> wrote:
Dear Cameron,
I agree IPv6 only client is no problem, but how about dual stack?
I am wondering at the dual stack issue, in my question 1).
Most application servers are still IPv4 only now,
so how many UEs turn on their IPv6 or Dual Stack?
As many as the operators wants to turn-on and support. Dual stack is
just adding functionality and does not take away functionality.
IPv6-only is the end-game we have to work towards (some more long term
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
than others) and the BEHAVE WG members are working on bridging that
gap.
^^^^^^^^^^^^^^^^^^^
[Xiangsong] I am sorry I came to behave/softwire wgs recently and know
little about the background, I am thinking about this work, it seems we are
taking such a precondition, the bearer network or the app servers are IPv4,
so translation for IPv6 only clients is introduced, is that correct?
This seems the UE-starting transition.
But on the other hand, if we firstly migrate bearer network to IPv6 or
dual stack, then migrate app servers to IPv6, since the IPv4 UEs are the
long tail, we migrate UEs at last, in this situation, the translation for IPv6
only clients is unnecessary? because when IPv6 only UEs appear, they
would find IPv6 has been ready. What we should pay attention is translation
for IP v4 only clients, which seems just out of scope of behave wg?
This seems the UE-following transition.
What I am doing is just comparing these two approaches.
Thanks and Regards
Xiangsong
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
