I agree. When there is a case of v4 legacy app unable to use IPv6 transport for what ever reasons, its rather better to go enable IPv4 on the peer, still supporting IPv6-only network over dual-stack lite network. Or, modify the app to use IPv6 transport and avoid the huge cost and management of dealing with a modified stack and on all OS variants. We are mainly mixing a true legacy requirement with new requirements which are debatable.
Sri On 12/1/09 9:04 AM, "Durand, Alain" <[email protected]> wrote: > Why go through all that trouble when you could make the server app dual-stack > capable in the first place? > That could be done with or without assigning a unique v4 address to it, simply > running v4 over v6... > Not you¹d be back to a v4 app talking to a v4 app on hosts only having v6 > addresses configured natively. > > - Alain. > >
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
