NAME

  S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsg.seq - Reply message transmission

TARGET

  Server

SYNOPSIS

 S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsg.seq [-tooloption ...]
 -pkt S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsg.def 
 -tooloption: v6eval tool option
See Also  DHCPv6.def 
 

INITIALIZATION

• Network Topology

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

• Verification Points

Packet's destination address
	
unicast address
	
The address  is same as the source address field from the IP datagram in which the Request message. 
	

Reply Message
	
msg-type
	REPLY(7)
	
transaction-id
        Same as the Request Message
	
Server Identifier option
	Any
	
Client Identifier option
	Same as the Request Message
	
IA_NA option

option-code
OPTION_IA_NA (3)
option-len
12 + length of IA_NA-options field
IAID
Same as Request message
T1
number
T2
number
IA_NA-options
IA Address option

	

• 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
        | ----> | Advertise
        | <---- | Request
        | ----> | Reply (*1)
        |       | 

JUDGEMENT

(*1) PASS: The format of Advertise,Solicit & Request message is correct.
           The Reply message with configuration parameters and assigned address is received by TN.

TERMINATION

REFERENCE

   see also RFC3315
   17.2.3.  Creation and Transmission of Reply Messages 

SEE ALSO