snMspsDhcpClient6IfDuid

Each DHCP client has a unique DUID. DHCP servers use DUIDs to identify 
clients for the selection of configuration parameters and in the 
association of IAs with clients.  DHCP clients use DUIDs to Identify 
a client in messages where a client needs to be identified.
Clients MUST treat DUIDs as opaque values and MUST only compare DUIDs 
for equality Clients and servers MUST NOT in any Other way interpret 
DUIDs. The DUID is carried in an option because it may be variable length 
and because it is not required in all DHCP messages.  The DUID is 
designed to be unique across all DHCP clients and servers, and stable
for any specific client or server - that is, the DUID used by a client 
or server SHOULD NOT change over time if at all possible; for example, 
a device's DUID should not change as a result of a change in
the device's network hardware.
The motivation for having more than one type of DUID is that the DUID 
must be globally unique, and must also be easy to generate. The sort of 
globally-unique identifier that is easy to generate for any given device 
can differ quite widely. Also, some devices may not contain any 
persistent storage. Retaining a generated DUID in such a device is not 
possible, so the DUID scheme must accommodate such devices. A DUID can be
no more than 130(including the type code) octets long.