> This is fine if you assume a one-to-one mapping of the original domain names to > IP addresses. The problem comes when the server a domain points to is the map > for several domains, say via Virtual Hosts or selected forwarding. Many servers > use this if they're on a dedicated web-hoster, or for subdomains. Without the
The function of FUCANN is to do away with mapping monopoly. If you want my.shit or amazon.com to point to 22.33.44.55, that's what my.shit and amazon.com will resolve to. If you *then* use 22.33.44.55 to send a packet via a particular protocol (say, http), then it's up to http client to send the full URL (containg target host symbolic name among other stuff) and up to demon listening on 22.33.44.55:80 to resolve that name to a particular virtual domain. Nothing to do with FUCANN, wich operates on L3/4. If the particular server does not run "amazon.com" virtual domain it's the problem that the server owner should deal with. FUCANN is about distributing naming authority, not about pointing to unsuspecting targets. ===== end (of original message) Y-a*h*o-o (yes, they scan for this) spam follows: Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/
