At 11:52 AM 1/12/99 -0800, Mark S. Miller wrote:
>My hope is that a host must have exactly one hostname.
[-] In the real world, a given host may have many different names. Consider a single host company with FTP and HTTP. They have www.foo.bar and ftp.foo.bar mapped to the same IP address. When they grow to need two separate servers, the add the new server and change the DNS entries. Everything outside doesn't have to change and there is only a small hiccup as the old DNS caches get invalidated.
>>An IP number maps to an interface
>>(maybe - for example, transparent proxies will map different ports on
>>the same IP to different IPs behind the proxy!) and an interface maps to
>[?] When proxies do map, do they normally change port numbers also?
>If they do, this creates further problems for E.
[#] It is up to the person setting up the mapping. That's why there is a form of the getConnectionsManager which allows specification of the port number. Then an administrator can have some chance of setting up the mapping and hitting the vat.
>When a Vat contacts the VLS through IP remapping, if the VLS is on the open
>internet, the VLS knows that the incoming IP address is adequate for others
>to use to contact the Vat, independent of the Vat's own notion of its IP
>However, if port numbers are being remapped as well, how can the Vat and
>VLS cooperate to figure out a port number by which others can contact the
>Vat's listen port?
[#] We would have to add support to advertise a different port number in that situation. Since port numbers are fluid, I don't know any reason to set up the mapping to change the port numbers. If there is such a reason, then we have some development to do to support it.