> DNS names are not a > good way to solve this problem for reasons of performance and > reliability and because a DNS name does not, in practice, > uniquely bind to a particular host. And DNS names are not in use on all Internet Protocol internetworks. This is because of the security issues of trusting a third party to supply an address-name mapping. > it is not reasonable to assume that for all apps the correct > model is to do a DNS lookup and then try the resulting IP > addresses one at a time until a connection succeeds for one of them. For instance, applications in the global finance industry typically do not do any DNS lookups at all. Admittedly, they often have a list of destination IP addresses which they try until a connection succeeds. But the point is that IPv6 transition has to be explicitly programmed into each and every application and it has to be embedded in the operational processes as well. > my, you have a simplistic view of the application world! This can be solved by talking to network operators, large consultancy firms and large enterprises. One can learn a lot about how IP networks are really implemented if one is willing to listen and learn. --Michael Dillon _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf