autoconfiguration
Click on the red underlined text to get to the source
... autoconfigure its interfaces in IP version 6. The autoconfiguration
process includes creating a link-local address and verifying its
...
... for generating site-local and global addresses via stateless address
autoconfiguration, and the Duplicate Address Detection procedure. The
details of autoconfiguration ...
... stateless address
autoconfiguration, and the Duplicate Address Detection procedure. The
details of autoconfiguration using the stateful protocol are
specified elsewhere.
...
...
IPv6 defines both a stateful and stateless address autoconfiguration
mechanism. Stateless autoconfiguration ...
... stateless address autoconfiguration
mechanism. Stateless autoconfiguration requires no manual
configuration of hosts, minimal (if any) configuration of routers ...
... addresses have been assigned to which hosts. The stateful
autoconfiguration protocol allows hosts to obtain addresses, other
...
... configuration information or both from a server. Stateless and
stateful autoconfiguration complement each other. For example, a host
can use stateless ...
... host
can use stateless autoconfiguration to configure its own addresses,
but use stateful autoconfiguration ...
... autoconfiguration to configure its own addresses,
but use stateful autoconfiguration to obtain other information.
Stateful autoconfiguration for IPv6 ...
... but use stateful autoconfiguration to obtain other information.
Stateful autoconfiguration for IPv6 is the subject of future work
...
... site requires tighter control over exact address assignments. Both
stateful and stateless address autoconfiguration may be used
simultaneously. The site administrator specifies which type of
...
... simultaneously. The site administrator specifies which type of
autoconfiguration to use through the setting of appropriate fields in
Router Advertisement messages [DISCOVERY ...
... independent of whether they are obtained via stateless or stateful
autoconfiguration. This document defines the Duplicate Address
Detection algorithm.
...
...
The autoconfiguration process specified in this document applies only
to hosts and not routers ...
... hosts and not routers. Since host autoconfiguration uses
information advertised by routers, routers ...
... Section 2 provides definitions for terminology used throughout this
document. Section 3 describes the design goals that lead to the
current autoconfiguration procedure. Section 4 provides an overview
of the protocol, while Section 5 describes the protocol in detail.
...
... that is (at least) unique per link [ADDR-ARCH]. Stateless
address autoconfiguration combines an interface identifier with
a prefix ...
... a prefix to form an address. From address autoconfiguration's
perspective, an interface identifier is a bit string ...
...
Stateless autoconfiguration is designed with the following goals in
mind:
...
... unique addresses for each of its interfaces. Address
autoconfiguration assumes that each interface can provide a
unique identifier ...
... System administrators need the ability to specify whether
stateless autoconfiguration, stateful autoconfiguration, or both
should be used. Router Advertisements ...
... stateless autoconfiguration, stateful autoconfiguration, or both
should be used. Router Advertisements include flags specifying
...
... This section provides an overview of the typical steps that take
place when an interface autoconfigures itself. Autoconfiguration is
performed only on multicast-capable links ...
... Nodes (both hosts and routers) begin the autoconfiguration process by
generating a link-local address for the interface ...
... node determines that its tentative link-local address is not
unique, autoconfiguration stops and manual configuration of the
interface ...
... interface
identifier that overrides the default identifier in such a way that
the autoconfiguration mechanism can then be applied using the new
(presumably unique) interface identifier. Alternatively, link-local ...
... IP-level connectivity with neighboring nodes. The remaining
autoconfiguration steps are performed only by hosts; the
(auto)configuration of routers ...
...
The next phase of autoconfiguration involves obtaining a Router
Advertisement or determining that no routers are present. If routers ...
... are present, they will send Router Advertisements that specify what
sort of autoconfiguration a host should do. If no routers are
...
... between successive advertisements will generally be longer than a
host performing autoconfiguration will want to wait [DISCOVERY]. To
obtain an advertisement quickly, a host ...
... multicast group. Router
Advertisements contain two flags indicating what type of stateful
autoconfiguration (if any) should be performed. A "managed address
configuration" flag indicates whether hosts should use stateful
...
... managed address
configuration" flag indicates whether hosts should use stateful
autoconfiguration to obtain addresses. An "other stateful
configuration" flag indicates whether hosts ...
... stateful
configuration" flag indicates whether hosts should use stateful
autoconfiguration to obtain additional information (excluding
addresses).
...
... Router Advertisements also contain zero or more Prefix Information
options that contain information used by stateless address
autoconfiguration to generate site-local and global addresses. It
...
... addresses. It
should be noted that the stateless and stateful address
autoconfiguration fields in Router Advertisements are processed
independently of one another, and a host ...
... independently of one another, and a host may use both stateful and
stateless address autoconfiguration simultaneously. One Prefix
Information option field, the "autonomous address ...
... flag", indicates whether or not the option even applies to stateless
autoconfiguration. If it does, additional option fields contain a
subnet prefix together with lifetime values ...
... interface identifier need not be tested individually. In
contrast, all addresses obtained manually or via stateful address
autoconfiguration should be tested for uniqueness individually. To
accommodate sites that believe the overhead of performing Duplicate
Address Detection ...
... responding to a Router Solicitation for a few seconds, the total time
needed to complete autoconfiguration can be significantly longer if
the two steps are done serially.
...
... interfaces. For multihomed hosts,
autoconfiguration is performed independently on each interface.
Autoconfiguration ...
... autoconfiguration is performed independently on each interface.
Autoconfiguration applies primarily to hosts, with two exceptions.
Routers ...
...
A node MUST allow the following autoconfiguration-related variable to
be configured by system management for each multicast ...
... IPv6-ETHER]).
Autoconfiguration also assumes the presence of the
variable RetransTimer as defined in [DISCOVERY].
...
... variable RetransTimer as defined in [DISCOVERY].
For autoconfiguration purposes, RetransTimer
specifies the delay between consecutive Neighbor
Solicitation transmissions performed during
...
... Autoconfiguration-Related Variables ...
... host maintains a number of data structures and flags related to
autoconfiguration. In the following, we present conceptual variables
and show how they are used to perform autoconfiguration. The specific
...
... autoconfiguration. In the following, we present conceptual variables
and show how they are used to perform autoconfiguration. The specific
variables are used for demonstration purposes only, and an
implementation is not required to have them, so long as its external
...
... addresses are
to be configured using the stateful
autoconfiguration mechanism. It starts out in a
FALSE state ...
... other than addresses is to be obtained using the
stateful autoconfiguration mechanism. It starts
out in a FALSE state ...
... valid configuration for
a host to use stateful address autoconfiguration
to request addresses only, without also accepting
...
... interface identifier is more than 118
bits in length, autoconfiguration fails and manual configuration is
required. Note that interface identifiers ...
... Each individual unicast address SHOULD be tested for uniqueness.
However, when stateless address autoconfiguration is used,
address uniqueness is determined solely by the interface
identifier ...
... routers, a host MUST attempt to use stateful
autoconfiguration to obtain addresses and other configuration
information. An implementation MAY provide a way to disable the
...
... addresses and other configuration
information. An implementation MAY provide a way to disable the
invocation of stateful autoconfiguration in this case, but the
default SHOULD be enabled. From the perspective of
autoconfiguration ...
... autoconfiguration in this case, but the
default SHOULD be enabled. From the perspective of
autoconfiguration, a link has no routers if no Router Advertisements ...
... into ManagedFlag. If the value of ManagedFlag changes from FALSE to
TRUE, and the host is not already running the stateful address
autoconfiguration protocol, the host should invoke the stateful
address autoconfiguration protocol, requesting both address
information ...
... host is not already running the stateful address
autoconfiguration protocol, the host should invoke the stateful
address autoconfiguration protocol, requesting both address
information and other information. If the value of the ManagedFlag
changes from TRUE to FALSE, the host ...
... changes from TRUE to FALSE, the host should continue running the
stateful address autoconfiguration, i.e., the change in the value of
the ManagedFlag has no effect. If the value of the flag stays
unchanged, no special action takes place. In particular, a host ...
... value of OtherConfigFlag changes from FALSE to TRUE, the host should
invoke the stateful autoconfiguration protocol, requesting
information (excluding addresses if ManagedFlag is set to FALSE). If
...
... the value of the OtherConfigFlag changes from TRUE to FALSE, the host
should continue running the stateful address autoconfiguration
protocol, i.e., the change in the value of OtherConfigFlag has no
effect. If the value of the flag stays unchanged, no special action
...
... address (i.e., one obtained via stateless or stateful address
autoconfiguration) in the list of addresses associated with the
interface ...
... learned from both Router Advertisements and the stateful
autoconfiguration protocol. If the same configuration information is
provided by multiple sources, the value of this information should be
...