NAME

  C_RFC3315_18_1_8_RelReply.seq - Check Reply to Release with IA option with Status code of NoBinding 

TARGET

  Client

SYNOPSIS

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


  See Also  DHCPv6.def  

INITIALIZATION

• Network Topology

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

• Verification Points



   When the client receives a valid Reply message in response to a
   Release message, the client considers the Release event completed,
   regardless of the Status Code option(s) returned by the server.
   

• 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 release address
        |       |
        | ----> |Release
        | <---- |Reply w/IA option(Status code = NoBinding)
        |       |
        | ---->X|Release (9*)	
        |       |
        | <---- |Echo Request 
        | ----> |Echo Reply (11*)
        |       |

JUDGEMENT

  
  (9*) PASS: NUT does NOT transmit Release message.
  (11*)PASS: NUT does NOT transmit Echo Reply.

TERMINATION

  N/A

REFERENCE

  Also see RFC3315


  18.1.8. Receipt of Reply Messages

SEE ALSO

  perldoc  V6evalTool