host
Click on the red underlined text to get to the source
...
This document specifies the steps a host takes in deciding how to
autoconfigure its interfaces in IP version 6 ...
... Stateless autoconfiguration requires no manual
configuration of hosts, minimal (if any) configuration of routers,
and no additional servers. The stateless ...
... routers,
and no additional servers. The stateless mechanism allows a host to
generate its own addresses using a combination of locally available
...
... subnet(s) associated with a link, while
hosts generate an "interface identifier" that uniquely identifies an
interface ...
... address is formed by combining the two. In
the absence of routers, a host can only generate link-local
addresses. However, link-local addresses are sufficient for allowing
...
... database that keeps track of which
addresses have been assigned to which hosts. The stateful
autoconfiguration protocol allows hosts ...
... hosts. The stateful
autoconfiguration protocol allows hosts to obtain addresses, other
configuration information ...
... Stateless and
stateful autoconfiguration complement each other. For example, a host
can use stateless autoconfiguration ...
... stateless approach is used when a site is not particularly
concerned with the exact addresses hosts use, so long as they are
unique and properly routable. The stateful approach is used when a
site requires tighter control over exact address ...
... The autoconfiguration process specified in this document applies only
to hosts and not routers. Since host autoconfiguration ...
... to hosts and not routers. Since host autoconfiguration uses
information advertised by routers ...
... them to the network should not be required. Consequently, a
mechanism is needed that allows a host to obtain or create
unique addresses ...
... link to which a set of nodes
attach. A host forms a link-local address by appending its
interface identifier ...
... In order to generate site-local or global addresses, hosts must
determine the prefixes that identify the subnets ...
... should be used. Router Advertisements include flags specifying
which mechanisms a host should use.
...
... interface is enabled, e.g., during system startup.
Nodes (both hosts and routers) begin the autoconfiguration process by
...
... nodes. The remaining
autoconfiguration steps are performed only by hosts; the
(auto)configuration of routers is beyond the scope of this document.
...
... Router Advertisements that specify what
sort of autoconfiguration a host should do. If no routers are
present, stateful autoconfiguration ...
... Router Advertisements periodically, but the delay
between successive advertisements will generally be longer than a
host performing autoconfiguration will want to wait [DISCOVERY]. To
...
... autoconfiguration will want to wait [DISCOVERY]. To
obtain an advertisement quickly, a host sends one or more Router
...
... autoconfiguration (if any) should be performed. A "managed address
configuration" flag indicates whether hosts should use stateful
autoconfiguration to obtain addresses ...
... autoconfiguration to obtain addresses. An "other stateful
configuration" flag indicates whether hosts should use stateful
autoconfiguration to obtain additional information (excluding
...
... stateful address
autoconfiguration fields in Router Advertisements are processed
independently of one another, and a host may use both stateful and
stateless address autoconfiguration simultaneously. One Prefix ...
... Because routers generate Router Advertisements periodically, hosts
will continually receive new advertisements. Hosts process the
...
... Router Advertisements periodically, hosts
will continually receive new advertisements. Hosts process the
information contained in each advertisement as described above,
adding to and refreshing information received in previous
...
...
To speed the autoconfiguration process, a host may generate its
link-local address (and verify its uniqueness) in parallel with
...
... to time-out addresses assigned to interfaces in hosts. At present,
upper layer protocols such as TCP ...
... multicast-capable interfaces. For multihomed hosts,
autoconfiguration is performed independently on each interface ...
... interface.
Autoconfiguration applies primarily to hosts, with two exceptions.
Routers are expected to generate a link-local address ...
...
Hosts maintain the following variables on a per-interface basis:
...
... TRUE as well. It is not a valid configuration for
a host to use stateful address autoconfiguration
to request addresses ...
...
A host also maintains a list of addresses together with their
corresponding lifetimes. The address ...
... nodes
multicast address. To obtain an advertisement quickly, a host sends
out Router Solicitations as described in [DISCOVERY ...
... If a link has no routers, a host MUST attempt to use stateful
autoconfiguration to obtain addresses ...
... Router Advertisement (as defined in
[DISCOVERY]), a host copies the value of the advertisement's M bit
into ManagedFlag. If the value of ManagedFlag changes from FALSE to
...
... M bit
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 ...
... 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 and other information. If the value of the ManagedFlag
...
... stateful
address autoconfiguration protocol, requesting both address
information and other information. If the value of the ManagedFlag
changes from TRUE to FALSE, the host should continue running the
stateful address autoconfiguration, i.e., the change in the value of
...
... 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 MUST
NOT reinvoke stateful address configuration if it is already
...
... An advertisement's O flag field is processed in an analogous manner.
A host copies the value of the O flag into OtherConfigFlag. If the
value of OtherConfigFlag changes from FALSE to TRUE, the host should
...
... A host copies the value of the O flag into OtherConfigFlag. If the
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
takes place. In particular, a host MUST NOT reinvoke stateful
configuration if it is already participating in the stateful protocol
as a result of an earlier advertisement.
...
...
If an address is formed successfully, the host adds it to the
list of addresses assigned to the interface ...
... consistent. However, it is not considered a fatal error if
information received from multiple sources is inconsistent. Hosts
accept the union of all information received via the stateless and
...
...
Stateless address autoconfiguration allows a host to connect to a
network, configure an address ...
... Bound, J. and C. Perkins, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", Work in Progress ...
... delivery of packets sent to a multicast group that the
sending host is a member of. Some applications know that there will
be no other group members on the same host ...
... host is a member of. Some applications know that there will
be no other group members on the same host, and suppressing loopback
prevents them from having to receive (and discard) the packets they
...