S_RFC3315_18.2.1_DiscardRequestMsg.seq - Reply for the not permitted Request message via unicast
Server
S_RFC3315_18.2.1_DiscardRequestMsg.seq [-tooloption ...] -pkt S_RFC3315_18.2.1_DiscardRequestMsg.def -tooloption: v6eval tool option See Also DHCPv6.def
TN(Client1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
Reply Message
The Request message is transimited via unicast from the client.
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
NUT TN
| |
| | initialize NUT (as a DHCPv6 Server)
| |
| <---- | Solicit
| ----> | Advertise
| <---- | Request(unicast)
| | NUT Discard the Request message
| ----> | Reply(w/ Status Code Option/UseMulticast) (*1)
| |
<PRE> (*1) PASS: The Solicit & Advertise & Request message must exchanged correctly. NUT must discard the Request message and respond with Reply message. The Reply message must only include Server ID option, Client ID option, and a Status Code option with value ``UseMulticast''. </PRE>
N/A
see also RFC3315 18 DHCP Client-Initiated Configuration Exchange 18.2.1 Receipt of Request Messages
perldoc V6evalTool