S_RFC3315_9.3_DUID-ENFormat.seq - Check the DUID Assigned by Vendor Based on Enterprise Number [DUID-EN]
Server
S_RFC3315_9.3_DUID-ENFormat.seq [-tooloption ...]
-pkt S_RFC3315_9.3_DUID-ENFormat.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
The type of DUID used by server is DUID_EN(2).
| 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)
| |
| <---- | Solicit
| ----> | Advertise (*1)
| |
The DUID's formatin the server's Identifier option of Advertise message
must be base on description of RFC(see above Verification Points).(*1)
N/A
see also RFC3315
9.3. DUID Assigned by Vendor Based on Enterprise Number [DUID-EN]
22.3. Server Identifier Option
perldoc V6evalTool