NAME

  S_RFC3315_9.3_DUID-ENPersit.seq  - The consistency of DUID-EN

TARGET

  Server

SYNOPSIS

 S_RFC3315_9.3_DUID-ENPersit.seq [-tooloption ...]
 -pkt S_RFC3315_9.3_DUID-ENPersit.def 
 -tooloption: v6eval tool option
 

INITIALIZATION

• Network Topology

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

• Verification Points

DUID Format in the Server ID option
      
DUID type
          2
      
enterprise-number
          Any
      
identifier
          Any
          

After rebooting
	  
Keep the DUID value
	  

• Configuration

	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

TEST PROCEDURE

	       NUT      TN
	        |       | 
	        |       | initialize NUT (as a DHCPv6 Server)
	        |       | 
	        | <---- | Solicit (w/ Rapid Commit)
	        | ----> | Reply   (*1)
	        |       | 
         restart
	        | <---- | Solicit (w/ Rapid Commit)
	        | ----> | Reply   (*2)

JUDGEMENT

 The DUID's  format in the Server's Identifier option of Reply message
 must be base on description of RFC(see above Verification Points).(*1)
 After restarting the DUID must be keeped. (*2)

TERMINATION

REFERENCE

see also RFC3315
9.2 DUID Based on Link-layer Address Plus Time [DUID-LLT]
22.3. Server Identifier Option

SEE ALSO