NAME

  C_RFC3315_18_1_2_TransCnf.seq - Check the format of Confirm

TARGET

  Client

SYNOPSIS

   C_RFC3315_18_1_2_TransCnf.seq [-tooloption...] 
  -pkt   C_RFC3315_18_1_2_TransCnf.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 sets the "msg-type" field to CONFIRM. 

   The client generates a transaction ID and inserts this value in the
   "transaction-id" field.

   The client MUST include a Client Identifier option to identify itself
   to the server. 

   The client includes IA options for all of the IAs  assigned to the 
   interface for which the Confirm message is being sent. 

   The IA options include all of the addresses the client currently has
   associated with those IAs.

   

• 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 donw/up)
        |       |
        | ----> |Confirm (7*)
        |       |

JUDGEMENT

  
  (7*)PASS: TN receives Confirm which conforms to Verification Points.

TERMINATION

  N/A

REFERENCE

  Also see RFC3315


  18.1.2. Creation and Transmission of Confirm Messages

SEE ALSO

  perldoc  V6evalTool