NAME

  S_RFC3633_12.2_ClientInitPDLifetime0.seq - Reply message with lifetimes = 0.


TARGET

  Server


SYNOPSIS

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


INITIALIZATION

          TN(Requesting router1)  
             |
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
                         |
                       NUT(Delegating router1)
  
  
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 options)                
        | ----> | Reply	(w/ IA_PD option,IA_PD Prefix 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

N/A


REFERENCE

   see also RFC3633
   12.2 Delegating Router behavior


SEE ALSO

perldoc V6evalTool