Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
|
NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
|
|
|
|
IPv6 ND Overview, History, Motivation and Standards
(Page 1 of 2)
The
purpose of network layer protocols like the Internet Protocol
is to provide a means of connecting together individual local networks
to create a much larger internetwork. To higher protocol layers and
to users, this internetwork behaves in most respects as if it were a
single large network, because the lower layers hide the details that
glue together the individual networks. Any device can send
information to any other, regardless of where it is located, and like
magic, it will work. At least, most of the time.
The existence of an internetwork
means that devices can treat all other devices as peers, at least from
the perspective of higher protocol layers and applications. From the
standpoint of lower layers, however, there is a very important difference
between devices that are on a host's local network and those that are
elsewhere. In a general sense, most devices have a more important relationship
with the devices that are on its local network than those that are far
away. Some of the most obvious tasks that a device must perform specifically
with other devices on its local network include:
- Direct Datagram Delivery: Devices
deliver data directly to other devices on their local network,
while data going to distant devices must be indirectly delivered
(routed).
- Layer Two Addressing: To facilitate direct
delivery, devices need to know the layer two addresses of the other
devices on the local network; they don't need to know them for non-local
devices.
- Router Identification: To deliver indirectly,
a device needs to find a router on its local network that it can talk
to.
- Router Communication: The local router
must communicate information to each of the local hosts using it so
they know how best to use it.
- Configuration: Hosts will usually look
to information provided by local devices to let them perform configuration
tasks such as determining their own IP address.
To support these and other requirements,
several special protocols and functions were developed along with the
original Internet Protocol (version 4). The IP addressing scheme lets
devices differentiate local addresses from distant ones. The Address
Resolution Protocol (ARP) lets devices
determine layer two addresses from layer three addresses. The Internet
Control Message Protocol (ICMP) provides
a messaging system to support various communication requirements between
local devices, including the ability of a host to find a local router
and the router to provide information to local hosts.
These features all work properly
in IPv4, but they were developed sort of in an ad hoc manner. They are
defined not in a single place, but rather in a variety of different
Internet standards. There were also some limitations with the way these
local device functions were implemented.
| If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |
|
|
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.
|