[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FW: I-D ACTION:draft-ietf-v6ops-ent-scenarios-03.txt




Hi Tim,


At 1:26 AM +0100 7/2/04, Tim Chown wrote:
Finally, how does communication between IPv4-only and IPv6-only nodes or
applications fit into the above three scenarios, if any of them?  Would
that be part of Scenario 3?  Perhaps make that clearer?

Can you describe a situation where this is necessary?


My preferred "solution" to this problem is to avoid the situation.  Nodes
that  need to speak to IPv4-only nodes must implement IPv4, and nodes
that need to speak to IPv6-only nodes must implement IPv6.  Nodes
that need to talk to both IPv4-only and IPv6-only nodes must be dual
stack.  An IPv4-only  node would not be able to communicate directly
with an IPv6-only node.

In this situation, the question changes from "How does an IPv4-only
node talk to  an IPv6-only node?" to "How do we get IPv6 connectivity
to a node that only has local IPv4 connectivity, and vice versa?".

So far, I haven't heard of any situation where IPv4<=>IPv6 translation
would be technically superior to dual stack/tunneling.

Margaret