NAME
C_RFC3736_DUID_ENFormat.seq - Verify the DUID Format using Basic message exchange
TARGET
Client
SYNOPSIS
C_RFC3736_DUID_ENFormat.seq [-tooloption...]
-pkt C_RFC3736_DUID_ENFormat.def
-tooloption : v6eval tool option
See Also DHCPv6.def
INITIALIZATION
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
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) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- type of DUID is 0x02
- enterprise-number of DUID is IANA-maintaiied value
- identifier of DUID is ANY Non-zero number
- Configurations
Device Name |
Device Type |
Interface |
Assigned Prefix |
Link Local Addr |
MAC Addr |
Client Id Option |
Client |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address |
NUT's MAC address |
Yes |
Server |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a1a1 |
00:00:00:00:a1:a1 |
N/A |
=end html
TEST PROCEDURE
NUT TN
| |
| |Initialize NUT (as a DHCPv6 Client)
| |
| ----> |information request (1*)
| |
| |
JUDGEMENT
(1*)PASS: TN receives Solicit from NUT and Verfication points are satisfied.
TERMINATION
N/A
REFERENCE
See RFC3315
9. DHCP Unique Identifier (DUID)
9.1. DUID Contents
9.2. DUID Based on Link-layer Address Plus Time [DUID-LLT]
22.2. Client Identifier Option
SEE ALSO
perldoc V6evalTool