Hi Bill, William Herrin wrote: > In addition, the definition of address is demonstrably wrong. > > >> address An address is a name that is used as both an interface >> locator and an endpoint identifier. > > Counterexample #1: RFC1918 IP addresses used inside a LAN consisting > of a personal computer, an ethernet hub and a NAT device. The IP > address in this example contains no locator semantics whatsoever, at > least not as you've defined a locator.
I disagree. The IP address is used to locate the component's interface within the subnet. The resolution protocol is ARP in this case as it "locates" the interface belonging to the particular IP address. So first it is checked whether the destination is in the same subnet (to me this is also related to finding the location) and if it is the case, ARP "locates" the particular interface. > Counterexample #2: The IP address of an anycasted DNS service. The IP > address neither identifies an endpoint nor locates a particular > interface's points of attachment to the network. Instead it identifies > a service and specifies multiple locations via which that service can > be obtained. Correct, but I don't think that this is really a counterexample: The Anycast address identifies _an_ endpoint (though not a particular/specific one) that hosts the DNS service. Anycast routing will locate _an_ interface belonging to such an endpoint. Regards, Roland _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
