address
Click on the red underlined text to get to the source
... DHCP server on behalf of the
client will be handled more correctly. This change also addresses
certain limitations in the functioning of RFC 2131draft/2132-style DHCP
client identifiers ...
... 2132draft recommends that client identifiers be generated by using the
permanent link-layer address of the network interface that the client
...
... identity of the client changes. The client loses its IP address
and any other resources associated with its old identifier (for
...
... Under the current specification, each network interface will receive
a different IP address. The DHCPv4 server will treat each network
interface as a completely independent DHCPv4 client ...
... In some cases, this will achieve the desired result; when only one
network interface is connected, sometimes its IP address will be
published. In some cases, the one connected interface's IP address ...
... IP address will be
published. In some cases, the one connected interface's IP address
will not be the one that is published. When there are two
interfaces ...
... the wireless network. When a transition like this happens, under the
current scheme, if the address of the wired interface is the one that
gets published, this client ...
... client did
not send one, the client's link-layer address. Like the client
identifier format recommended by RFC 2131draft, this suffers from the
...
...
In order to address the problems stated in section 4, DHCPv4 client
identifiers must have the following characteristics:
...
... DHCPv4 server that these
two network interfaces are to receive different IP addresses, even
if they happen to be connected to the same link.
...
... interfaces, so that if they both happen to be
connected to the same network, they will both receive the same IP
address. In such cases, it must be possible for the client to use
exactly the same identifier ...
... client identifiers based solely on layer two
addresses that are hard-wired to the layer two device (e.g., the
ethernet ...
... layer two device (e.g., the
ethernet MAC address) as suggested in RFC 2131draft, except as allowed in
section 9.2 of RFC 3315prop ...
... client in the case where the administrator is
assigning a fixed IP address to the client, even if the client sends
...
... 2131draft, on page 9, the text that reads "; for
example, the 'client identifier' may contain a hardware address,
identical to the contents of the 'chaddr' field, or it may contain
another type of identifier ...
... computers. Sites may also choose to use a DNS name as the 'client
identifier', causing address leases to be associated with the DNS
name rather than a specific hardware box." is replaced by the text
...
... some cases more than two!) boot stages will present different
identities. A DHCPv4 server will therefore allocate two different IP
addresses to the two different boot stages.
Some DHCP servers ...
... Message Authentication Code (MAC)
address of the network interface -- both are treated as the same
identifier ...
... network interface -- both are treated as the same
identifier. This prevents the consumption of an extra IP address.
A compliant DHCPv4 client ...
... DHCPv4 client does not use a client identifier
constructed from the MAC address of the network interface, because
network interfaces ...
... DHCP clients in network boot loaders request
short lease times, so that their IP addresses are not retained. Such
clients should send a DHCPRELEASE message to the DHCP server ...
... expected ever to network boot using DHCPv6, and that have a MAC
address that cannot be easily changed may not need to implement the
changes described in this specification. There is some danger in
making this assumption--the first solution suggested is definitely
...
... Authors' Addresses ...
... copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
...