| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The Need For Address Resolution (Page 3 of 3) General Address Resolution Methods In fact, not only do we need to have way of making this translation, we need to be concerned with the manner in which it is done. Since the translation occurs for each hop of every datagram sent over an internetwork, the efficiency of the process is extremely important. We don't want to use a resolution method that takes a lot of network resources. Address resolution can be accomplished in two basic ways:
The next two topics explore these two methods in more detail. You should bear in mind that of necessity, it is not possible to have a fully general address resolution method that works automatically. Since it deals with linking data link layer addresses to network layer addresses, the implementation must be specific to the technologies used in each of these layers. The only method that could really be considered generic would be the use of static, manually-updated tables that say link this layer three address to this layer two address. This, of course, is not automatic and brings with it all the limitations of manual configuration.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||