Brian E Carpenter wrote:
However, see draft-wing-v6ops-happy-eyeballs-ipv6
Yuk. That approach appears to be from a completely different universe
that solutions to the IPv4->IPv6 migration issue.
Instead of solving the problem where it originates, at the network level,
it dumps the entire problem onto the application in the worst conceivable
fashion. It makes IPv6 and IPv4 worlds appear like two completely
seperate and independent Internets, i.e. this proposal incurs on apps
the exact same effort as migrating a completely different network protocol
or completely different network.
If anyone had suggested that for a migration from PSTN to VoiP, then
everyone would have to use two phones these days, dial in parallel
and hang up on whichever call establishes second.
The problem that this draft tries to solve at the app-level really
ought to be solved at the network level. Use IPv6 addresses that
embed the alternative IPv4 address and have the network figure out
whether the route is IPv6 clean and the connection can be established
as IPv6 or only IPv4. (IPv4-NATing the IPv4 part of such an
address along the way is probably "fun"...) ... for exactly those
network interfaces that _have_ dual IPv4+IPv6 addresses.
-Martin
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf