NAME

  C_RFC3315_18_1_6_RelReplyFail.seq - Check Failure of Release-Reply Exchange 

TARGET

  Client

SYNOPSIS

   C_RFC3315_18_1_6_RelReplyFail.seq [-tooloption...] 
  -pkt   C_RFC3315_18_1_6_RelReplyFail.def 
  -tooloption : v6eval tool option


  See Also  DHCPv6.def  

INITIALIZATION

• Network Topology

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

• Verification Points



   If addresses are released but the Reply from a DHCP server is lost,
   the client will retransmit the Release message, and the server may
   respond with a Reply indicating a status of NoBinding.  Therefore,
   the client does not treat a Reply message with a status of NoBinding
   in a Release message exchange as if it indicates an error.
   

• 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 
        | <---- |Advertise 
        | ----> |Request 
        | <---- |Reply 
        |       |
        | <---- |Echo Request
        | ----> |Echo Reply
        |       |	 
        |       |NUT initiates the Release-Reply Exchange
        |       |
        | ----> |Release 
        |       |
        |       |Before first RT time expires
        |       |
        | ----> |Release 
        | <---- |Reply(W/Status code/NoBinding) 
        | ----> |Release (10*)
        |       |

JUDGEMENT

  
  (10*)PASS: NUT does not transmit Release any more.

TERMINATION

  N/A

REFERENCE

  Also see RFC3315


  18.1.6. Creation and Transmission of Release Messages

SEE ALSO

  perldoc  V6evalTool