NAME

  C_RFC3315_18_1_2_CnfRetransRT.seq - Check RT of Confirm

TARGET

  Client

SYNOPSIS

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


  See Also  DHCPv6.def  

INITIALIZATION

• Network Topology

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

• Verification Points



   The client transmits the message using the following parameters:

      IRT   CNF_TIMEOUT 

      MRT   CNF_MAX_RT  

      MRC   0           

      MRD   CNF_MAX_RD  

   The first RT is based on IRT as followings:

      RT = IRT + RAND*IRT
   

• 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
        |       |
        |       |Restart NUT (or interface up/down)
        |       |
        | ----> |Confirm 
        |       |
        |       |Waiting until	DHCPv6 message arrives
        |       |
        | ----> |Confirm (8*)
        |       |

JUDGEMENT

  (8*)PASS: TN receives retransmitted Confirm from NUT.
            And first RT conforms to Verification Points.

TERMINATION

  N/A

REFERENCE

  Also see RFC3315

  
  18.1.2. Creation and Transmission of Confirm Messages

SEE ALSO

  perldoc  V6evalTool