S_RFC3633_12.2_ClientInitPDLifetime0.seq - Reply message with lifetimes = 0.
Server
S_RFC3633_12.2_ClientInitPDLifetime0.seq [-tooloption ...]
-pkt S_RFC3633_12.2_ClientInitPDLifetime0.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Requesting router1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Delegating router1)
- Verification Points
The delegating router MUST include an IA_PD Prefix option or options
(in an IA_PD option) in Reply messages. The lifetimes are all 0.
Format of IA_PD option
option-code
OPTION_IA_PD (25)
option-length
Any
IAID
Any
T1
Any
T2
Any
IA_PD-options
Any
Format of IA_PD Prefix option
option-code
OPTION_IAPREFIX (26)
option-length
Any
preferred-lifetime
0
valid-lifetime
0
prefix-length
Any
IPv6-prefix
Any
IAprefix-options
Any
- Configuration
The prefixes in the IA_PD prefix options of Renew messages are not in
the Requesting router's binding entry.
| 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
| ----> | Advertise
| <---- | Request
| ----> | Reply
| |
| <---- | Renew (w/ IA_PD option,IA_PD Prefix options)
| ----> | Reply (w/ IA_PD option,IA_PD Prefix option) (*1)
| |
(*1)PASS: The TN & NUT exchanges above messages correctly.
And the format of options must be base on description
of RFC(see above Verification Points).
N/A
see also RFC3633
12.2 Delegating Router behavior
perldoc V6evalTool