NAME
C_RFC3315_9_4_CltDUIDLLFormat.seq - Check the format of DHCPv6 Client`s DUID-LL
TARGET
Client
SYNOPSIS
C_RFC3315_9_4_CltDUIDLLFormat.seq [-tooloption...]
-pkt C_RFC3315_9_4_CltDUIDLLFormat.def
-tooloption : v6eval tool option
See Also DHCPv6.def
INITIALIZATION
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
The following diagram illustrates the format of a DUID-LL:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 3 | hardware type (16 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. link-layer address (variable length) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- type of DUID is 0x03
- hardware type of DUID is IANA-assigned value in RFC826
- link-layer address of DUID is link-layer address
- Configurations
Device Name |
Device Type |
Interface |
Assigned Prefix |
Link Local Addr |
MAC Addr |
Client |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address |
NUT's MAC address |
Server |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a1a1 |
00:00:00:00:a1:a1 |
TEST PROCEDURE
NUT TN
| |
| |Initialize NUT(as a DHCPv6 Client)
| |
| ----> |Solicit (1*)
| |
| |
(1*)TN Captures Solicit from NUT.
JUDGEMENT
(1*)PASS: Verification points should be satisified.
TERMINATION
N/A
REFERENCE
Also see RFC3315
9. DHCP Unique Identifier (DUID)
9.1. DUID Contents
9.4. DUID Based on Link-layer Address [DUID-LL]
22.2. Client Identifier Option
SEE ALSO
perldoc V6evalTool