S_RFC3315_6_ServerMsgFormat.seq - Check Message Format
Server
S_RFC3315_6_ServerMsgFormat.seq [-tooloption ...]
-pkt S_RFC3315_6_ServerMsgFormat.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
Reply Message Format
msg-type
REPLY(7)
transaction-id
Any
options
Server ID option
Client ID option
Rapid commit option
| 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 (w/ Rapid Commit)
| ----> | Reply (*1)
| |
The server's Format of Reply message(*1) must be base on description
of RFC(see above Verification Points).
N/A
See also RFC3315
6 Client/Server Message Formats
perldoc V6evalTool