NAME

  S_RFC3633_12.2_ClientInitPDNoBinding.seq - Renew/Reply message exchange with IA_PD Prefix option.

TARGET

  Server

SYNOPSIS

 S_RFC3633_12.2_ClientInitPDNoBinding.seq [-tooloption ...]
 -pkt S_RFC3633_12.2_ClientInitPDNoBinding.def 
 -tooloption: v6eval tool option
See Also  DHCPv6.def 
 

INITIALIZATION

• Network Topology

          TN(Requesting router1)  
             |
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
                         |
                       NUT(Delegating router1)
  

• Verification Points

The Delegating router returns Reply message without IA_PD Prefix option.
Includes IA_PD option. It's format is,
      
option-code
      OPTION_IA_PD (25)
      
option-length
      12 + length of IA_PD-options field.
      
IAID
      Any
      
T1
      Any
      
T2
      Any
      
IA_PD-options
      

      
No Any prefixes options
      
Status Code option
      

      
option-code
      OPTION_STATUS_CODE (13)
      
option-len
      2 + length of status-message
      
 status-code 
      NoBinding(3)
      
status-message
       Any  
      
      

• Configuration

Device Name	Device Type	I/F	Assigned Prefix	Link Local Addr	MAC Addr
Delegating router1	NUT	Link0	3ffe:501:ffff:100::/64	NUT's Linklocal address	NUT's MAC address
Requesting router1	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 Delegating router)
        |       | 
        | <---- | Solicit                   
        | ----> | Advertise	            
        | <---- | Request	            
        | ----> | Reply		            
        |       | 
        | <---- | Renew 	(w/ IA_PD option,IA_PD Prefix option)                
        | ----> | Reply	(w/ IA_PD option,Status Code option)            (*1)
        |       | 

JUDGEMENT

(*1)PASS: The TN & NUT exchanges above messages correctly.
          And the format of options must be base on description 
          of RFC(see above Verification Points).

TERMINATION

REFERENCE

   see also RFC3633
   12.2 Delegating Router behavior

SEE ALSO