NAME

  C_RFC3315_9_2_CltDUIDLLTRebootFormat.seq - Test for the consistence of DHCPv6 Client`s DUID-LLT after Client reboots

TARGET

  Client

SYNOPSIS

   C_RFC3315_9_2_CltDUIDLLTRebootFormat.seq [-tooloption...] 
  -pkt  C_RFC3315_9_2_CltDUIDLLTRebootFormat.def 
  -tooloption : v6eval tool option  See Also  DHCPv6.def  

INITIALIZATION

• Network Topology

          NUT(Client)
          |           
          |                        
Link0   --+--------+------------------------ 3ffe:501:ffff:100::/64
                   |
                   |          
                   TN(Server) 
   

• Verification Points



   Clients using DUID-LLT should store the DUID-LLT in stable storage. So if the client reboots,
   the DUID-LLT should not change.
   

• 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*)
        |       |
        |       |Reboot NUT 
        |       |
        | ----> |Solicit (2*)
        |       |

JUDGEMENT

  (2*)PASS: DUID-LLT of TN-received Solicit is the same with that of (1*). 

TERMINATION

  N/A

REFERENCE

  Also 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