1 - 2 - 3 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
neighbor discovery
Click on the red underlined text to get to the source
...
This specification defines the Neighbor Discovery (ND) protocol for
Internet Protocol Version 6 ...
... hosts and routers) use
Neighbor Discovery to determine the link-layer addresses for
neighbors ...
... links and to quickly purge
cached values that become invalid. Hosts also use Neighbor Discovery
to find neighboring routers that are willing to forward packets on
...
... proxy - a router that responds to Neighbor Discovery query
messages on behalf of another node ...
... Different link layers have different properties. The ones of concern
to Neighbor Discovery are:
...
...
In addition to addressing the above general problems, Neighbor
Discovery also handles the following situations:
...
... the same link may be configured to recognize the same Anycast
address. Neighbor Discovery handles anycasts by having nodes
expect to receive multiple Neighbor ...
...
The Neighbor Discovery protocol provides a multitude of improvements
over the IPv4 set of protocols:
...
...
Unlike ARP, Neighbor Discovery detects half-link failures (using
Neighbor Unreachability Detection ...
...
Neighbor Discovery supports links with different properties. In the
presence of certain properties only a subset of the ND ...
... interfaces
can be assigned link-local addresses.) Neighbor
Discovery should be implemented as described in
this document.
...
...
multicast - Neighbor Discovery should be implemented as
described in this document.
...
... asymmetric reachability
- Neighbor Discovery detects the absence of
symmetric reachability; a node ...
...
Neighbor Discovery messages include zero or more options, some of
which may appear multiple times in the same message. All options are
of the form:
...
...
These options MUST be silently ignored for other
Neighbor Discovery messages.
...
...
This option MUST be silently ignored for other
Neighbor Discovery messages.
...
...
This option MUST be silently ignored for other
Neighbor Discovery messages.
In configurations in which heterogeneous
...
... nodes. The described
organization is provided to facilitate the explanation of how the
Neighbor Discovery protocol should behave. This document does not
mandate that implementations adhere to this model as long as their
external behavior is consistent with that described in this document.
...
... This model is only concerned with the aspects of host behavior
directly related to Neighbor Discovery. In particular, it does not
concern itself with such issues as source address selection or the
...
... Implementations may find it convenient to store
additional information not directly related to
Neighbor Discovery in Destination Cache entries,
such as the Path MTU ...
... hosts have multiple interfaces. The remainder
of this document assumes that all sent and received Neighbor
Discovery messages refer to the interface of appropriate context.
...
... active entries. A small cache may result in an
excessive number of Neighbor Discovery messages if entries are
discarded and rebuilt in quick succession. Any LRU-based policy that
only reclaims entries that have not been used in some time (e.g., ten
...
... router and host behavior related to the Router
Discovery portion of Neighbor Discovery. Router Discovery is used to
locate neighboring routers ...
... different link layers. This rule simplifies the configuration of
Neighbor Discovery over link types with widely differing performance
characteristics.
...
...
A host maintains certain Neighbor Discovery related variables in
addition to the data structures defined in Section 5.1. The specific
...
... specific documents that describe how IP operates over different link
layers. This rule allows Neighbor Discovery to operate over links
with widely varying performance characteristics ...
... default router and receive a redirect rather than sending
packets directly to a neighbor) the Neighbor Discovery protocol does
not impose such a check on the prefix lifetime values ...
... Neighbor Cache. In such
situations, a node will first have to use Neighbor Discovery to
determine the link-layer address of its neighbor ...
...
From the perspective of Neighbor Discovery, anycast addresses are
treated just like unicast addresses ...
... flag set to one are sent only in response to a Neighbor Solicitation.
Receipt of other Neighbor Discovery messages such as Router
Advertisements and Neighbor Advertisement with the Solicited flag set
to zero ...
... state is entered upon receiving an
unsolicited Neighbor Discovery message that updates
the cached link-layer address. Receipt of such a
...
...
Options in Neighbor Discovery packets can appear in any order;
receivers MUST be prepared to process them independently of their
...
... IPv6 operates over different link layers.
This rule allows Neighbor Discovery to operate over links with widely
varying performance characteristics ...
...
Neighbor Discovery protocol packet exchanges can be authenticated
using the IP Authentication Header ...
... node SHOULD
include an Authentication Header when sending Neighbor Discovery
packets if a security association for use with the IP Authentication
Header ...
...
Received Authentication Headers in Neighbor Discovery packets MUST be
verified for correctness and packets with incorrect authentication
...
... system administrator to configure a
node to ignore any Neighbor Discovery messages that are not
authenticated using either the Authentication Header ...
...
There are a number of complicating issues that arise when Neighbor
Discovery is used by hosts that have multiple interfaces. This
...
... section does not attempt to define the proper operation of multihomed
hosts with regard to Neighbor Discovery. Rather, it identifies
issues that require further study. Implementors are encouraged to
...
... issues that require further study. Implementors are encouraged to
experiment with various approaches to making Neighbor Discovery work
on multihomed hosts and to report their experiences.
...
... router on
one of the other interfaces. Neighbor Discovery does not
address this scenario; it does not arise in the non-multihomed
...
... Added text to section 6.3.4 to point out that [ADDRCONF] might
ignore short lifetimes but that Neighbor Discovery does not ignore
short prefix lifetimes.
...