NAME

  S_RFC3315_18.2.1_ReceiptRequestMsgWithStatusCodeOPNoAddrsAvail.seq - respond when any address can't be assigned(w/ Status Code option/NoAddrsAvail)

TARGET

  Server

SYNOPSIS

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

INITIALIZATION

• Network Topology

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

• Verification Points

Reply Message for the Client2
	
msg-type
	REPLY(7)
	
transaction ID
	Same as the Request message
	
Server ID option
	Include Server's DUID
	
Client ID option
	Same as the Request message
	
IA_NA option
	
Include Status Code option
		value = NoAddrsAvail(2)
		Not include IA_NA 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
Client2	TN	Link0	3ffe:501:ffff:100::/64	fe80::200:ff:fe00:a3a3	00:00:00:00:a3:a3

Server can't assign any address to client according with the IA_NA in the  Request message.

TEST PROCEDURE

       NUT     TN
        |       | 
        |       | initialize NUT (as a DHCPv6 Server)
        |       | Client1
        | <---- | Solicit   
        | ----> | Advertise 
        | <---- | Request   
        | ----> | Reply 
        |       | 
        |       | Client2
        | <---- | Solicit   
        | ----> | Advertise 
        | <---- | Request   
        | ----> | Reply (w/ Status Code option ,IA_NA option)(*1)
        |       | 

JUDGEMENT

<PRE> (*1) PASS: The messages must exchanged correctly. NUT must respond with Reply message. The Reply message must have IA_NA option in which there is a Status Code option with NoAddrsAvail. </PRE>

TERMINATION

  N/A

REFERENCE

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

SEE ALSO

  perldoc V6evalTool