S_RFC3736_DUID-ENPersit.seq - The consistency of DUID-EN
Server
S_RFC3736_DUID-ENPersit.seq[-tooloption ...]
-pkt S_RFC3736_DUID-ENPersit.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
DUID Format in the Server ID option
The following diagram summarizes the structure of a DUID-EN:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 2 | enterprise-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| enterprise-number (contd) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. identifier .
. (variable length) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
DUID type
2
enterprise-number
IANA-maintaiied value
identifier
ANY Non-zero number
After rebooting
Keep the DUID value
Option Request option in the Information-request message
option-code
OPTION_ORO(6)
option-len
Any
requested-option-code-1
OPTION_DNS_SERVERS(23)
| Device Name |
Device Type |
I/F |
Assigned Prefix |
Link Local Addr |
MAC Addr |
| Server1 |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address |
NUT's MAC address |
| Client1 |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a2a2 |
00:00:00:00:a2:a2 |
NUT TN
| |
| | initialize NUT (as a DHCPv6 Server)
| |
| <---- | Information-request(w/ Option Request option)
| ----> | Reply (w/ Server ID option) (*1)
| |
reboot
| |
| <---- | Information-request(w/ Option Request option)
| ----> | Reply (w/ Server ID option) (*2)
(*1)PASS: The DUID's format in the Server's Identifier option of Reply
message must be base on description of RFC(see above Verification Points).
(*2)PASS: After restarting, the DUID must be keeped.
N/A
see also RFC3315
9.3. DUID Assigned by Vendor Based on Enterprise Number [DUID-EN]
22.3. Server Identifier Option see also RFC3736
5.2. Options Required for Stateless DHCP Service
perldoc V6evalTool