NAME

  S_RFC3315_18.2.1_ReceiptRequestMsg.seq - Checking the Reply message

TARGET

  Server

SYNOPSIS

 S_RFC3315_18.2.1_ReceiptRequestMsg.seq [-tooloption ...]
 -pkt S_RFC3315_18.2.1_ReceiptRequestMsg.def 
 -tooloption: v6eval tool option
See Also  DHCPv6.def 
 

INITIALIZATION

• Network Topology

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

• Verification Points

Reply Message
	
msg-type
	REPLY(7) 
	
transaction ID
	Same as the Request message
	
Server ID option
	Any
	
Client ID option
	Same as the Request message
	

• 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 Solicit & Advertise & Request message must exchanged correctly.
          NUT will respond with Reply message.
          The Reply message must include Server ID option, Client ID option,
          and check its 'msg-type' and 'transaction ID' OK.

TERMINATION

REFERENCE

   see also RFC3315
   18 DHCP Client-Initiated Configuration Exchange
   18.2.1 Receipt of Request Messages

SEE ALSO