NAME

  S_RFC3315_15_1_TransactionIDSync.seq - TransactionID field check(keep consitence)

TARGET

  Server

SYNOPSIS

 S_RFC3315_15_1_TransactionIDSync.seq [-tooloption ...]
 -pkt S_RFC3315_15_1_TransactionIDSync.seq.def 
 -tooloption: v6eval tool option
See Also  DHCPv6.def 
 

INITIALIZATION

• Network Topology

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

• Verification Points

 
NUT(Server) must keep one same transaction ID in a same DHCP message exchangement.

• Configuration

Device Name	Device Type	I/F	Assigned Prefix	Link Local Addr	MAC Addr
Server1	NUT	Link0	3ffe:501:ffff:100::/64	NUT's Linklocal address	NUT's MAC address
Client1	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 DHCPv6 Server)
        |       | 
        | <---- | Solicit            transaction ID1
        | ----> | Advertise   (*1)   transaction ID1
        | <---- | Request            transaction ID2
        | ----> | Reply       (*2)   transaction ID2
        |       | 

JUDGEMENT

(*1) The NUT respond to the Solicit message with same transaction
     ID1 in the Advertise message from the TN.
(*2) The NUT respond to the Request message with same transaction
     ID2 in the Reply message from the TN.

TERMINATION

REFERENCE

   see also RFC3315
   15.1 Use of Transaction IDs

SEE ALSO