client identifier
Click on the red underlined text to get to the source
...
RFC 2132draft recommends that client identifiers be generated by using the
permanent link-layer address of the network interface ...
... DHCPv4 clients and servers
to identify clients. In some cases, the value of the 'client
identifier' option is used to mediate access to resources (for
example, the client's domain name ...
... 3315prop specify different methods for
deriving client identifiers. These methods guarantee that the DHCPv4
...
... RFC 2131draft does not require the use of a client identifier. ...
... DHCPv4 server to identify clients either by using
the client identifier option sent by the client or, if the client did
...
... not send one, the client's link-layer address. Like the client
identifier format recommended by RFC 2131draft, this suffers from the
problems previously described in sections 4.2 and 4.3.
...
... - They must be persistent, in the sense that a particular host's
client identifier must not change simply because a piece of network
hardware ...
... - DHCPv4 servers that do not conform to this specification, but that
are compliant with the older client identifier specification, must
correctly handle client identifiers sent by clients ...
... are compliant with the older client identifier specification, must
correctly handle client identifiers sent by clients that conform to
this specification.
...
... client-identifier option. DHCPv4
clients MUST NOT use client identifiers based solely on layer two
addresses ...
... section 9.2 of RFC 3315prop. DHCPv4 clients MUST send a 'client
identifier' option containing an Identity Association Unique
Identifier ...
... The general format of the DHCPv4 'client identifier' option is
defined in section 9.14 of RFC 2132draft.
...
... binding identifier in a DHCPv4 'client
identifier' option, the type of the 'client identifier' option is set
to 255. The type field ...
... identifier in a DHCPv4 'client
identifier' option, the type of the 'client identifier' option is set
to 255. The type field is immediately followed by the IAID, which is
...
... opaque 32-bit quantity. The IAID is immediately followed by the
DUID, which consumes the remaining contents of the 'client
identifier' option. The format of the 'client identifier' option is
as follows:
...
... 32-bit quantity. The IAID is immediately followed by the
DUID, which consumes the remaining contents of the 'client
identifier' option. The format of the 'client identifier' option is
as follows:
...
... 2131draft and RFC 2132draft, in the sense
that they ignore the 'client identifier' option and use the client's
hardware address ...
... DHCPv4 servers that conform to this specification MUST use the
'client identifier' option to identify the client if the client sends
...
... client, even if the client sends
a client identifier option. This is ONLY permitted in the case where
the DHCPv4 server administrator ...
... In section 2 of RFC 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
...
... client MAY choose to
explicitly provide the identifier through the 'client identifier'
option. If the client supplies a 'client identifier ...
... client identifier'
option. If the client supplies a 'client identifier', the client
MUST use the same 'client identifier ...
... client identifier', the client
MUST use the same 'client identifier' in all subsequent messages, and
the server MUST use that identifier to identify the client ...
... client. If the
client does not provide a 'client identifier' option, the server MUST
use the contents of the 'chaddr' field to identify the client." is
...
... client." is
replaced by the text "The client MUST explicitly provide a client
identifier through the 'client identifier' option. The client MUST
...
... replaced by the text "The client MUST explicitly provide a client
identifier through the 'client identifier' option. The client MUST
use the same 'client identifier ...
... client identifier' option. The client MUST
use the same 'client identifier' option for all messages."
In the same section, the text "Use of 'chaddr' as the client ...
... new
client. Some sites may choose to use a manufacturer's serial number
as the 'client identifier', to avoid unexpected changes in a client's
network ...
... interfaces among
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 ...
... 4.3.1, where RFC 2131draft says that 'chaddr' may be used instead of the
'client identifier' option, the text "or 'chaddr'" and "'chaddr' or"
is deleted.
...
... identifier if the client does not
send a 'client identifier' option. Rather, they oblige clients that
conform with this document to send a 'client identifier ...
... client identifier' option. Rather, they oblige clients that
conform with this document to send a 'client identifier' option, and
not rely on 'chaddr' for identification. DHCPv4 servers MUST use
...
... DHCPv4 servers MUST use
'chaddr' as an identifier in cases where 'client identifier' is not
sent, in order to support old clients that do not conform with this
...
...
The text in section 9.14, beginning with "The client identifier MAY
consist of" through "that meet this requirement for uniqueness." is
...
... consist of" through "that meet this requirement for uniqueness." is
replaced with "the client identifier consists of a type field whose
value is normally 255, followed by a four-byte IA_ID field, followed
...
... over the network. In such cases, it may be that the first-stage boot
uses a different client identifier, or no client identifier, than the
subsequent stage or stages.
...
... network. In such cases, it may be that the first-stage boot
uses a different client identifier, or no client identifier, than the
subsequent stage or stages.
...
... Some DHCP servers work around this problem for the common case where
the boot Programmable Read Only Memory (PROM) presents no client
identifier, and the operating system DHCP client presents a client
identifier ...
... client
identifier, and the operating system DHCP client presents a client
identifier constructed from the Message Authentication Code (MAC)
...
...
A compliant DHCPv4 client does not use a client identifier
constructed from the MAC address of the network interface ...