S_RFC3633_10_IAPDPreOP.seq - Checking the format of IA_PD Prefix option.
Server
S_RFC3633_10_IAPDPreOP.seq [-tooloption ...]
-pkt S_RFC3633_10_IAPDPreOP.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Requesting router1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Delegating router1)
Format of IA_PD Prefix option
option-code
OPTION_IAPREFIX (26)
option-length
25 + length of IAprefix-options field
preferred-lifetime
Any
valid-lifetime
Any
prefix-length
Length for this prefix in bits
IPv6-prefix
Any
IAprefix-options
Any
- Configuration
| Device Name |
Device Type |
I/F |
Assigned Prefix |
Link Local Addr |
MAC Addr |
| Delegating router1 |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address |
NUT's MAC address |
| Requesting router1 |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a2a2 |
00:00:00:00:a2:a2 |
NUT TN
| |
| | initialize NUT (as a Delegating router)
| |
| <---- | Solicit (w/ IA_PD option,IA_PD Prefix option)
| ----> | Advertise (w/ IA_PD option,IA_PD Prefix option) (*1)
| <---- | Request (w/ IA_PD option,IA_PD Prefix option)
| ----> | Reply (w/ IA_PD option,IA_PD Prefix option) (*2)
| |
(*1)(*2)PASS: The TN & NUT exchanges above messages correctly.
And the format of IA_PD Prefix option must be base on description
of RFC(see above Verification Points).
N/A
see also RFC3633
10. IA_PD Prefix option
perldoc V6evalTool