Hi, The indicated by the subject, which is perhaps not fully solved in the discovery draft, I guess at least the following scenarios should be considered. As I'm not an expert on roaming technology, please correct me if you find I am wrong.
(1) The ALTO client has left its home network, and its IP address is dynamically assigned by the current network provider (through DHCP or any other method), but the ALTO client still uses its home agent to access the Internet. In this case, the ALTO server resided in its home network should be the right ALTO server to be discovered. (2) The ALTO client has left its home network, and its IP address is dynamically assigned by the current network provider, and the ALTO client uses the foreign agent to access Internet or uses its IP address directly to access Internet. In this scenario, the ALTO server resided in the current network should be the right one. And the existing discovery mechanism works in this scenario. (3) If the ALTO client has a persistent IP address when roaming, and it uses home agent to access Internet, but make large data route to the foreign agent directly (optimized routing mode). In this scenario, the ALTO server resided in the current network should be the right one to be discovered. However, if it does not adopt the optimized routing mode, the ALTO server in the home network should be the right one. (4) (this one is not about roaming) Assume in a big company which has a few branch offices in different locations, and VPN tunnels are used to connect these branch offices, employees use one proxy to access Internet. Then the ALTO server discovery should be based on the proxy's IP address instead of the user's IP address. It also applies to other similar scenarios when end-hosts using proxies. It might not be a problem when doing third party discovery, but have to consider when doing the discovery by the end-host itself. BR, -Haibin _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
