S_RFC3633_9_IAPD_IgnoreInValidT1T2.seq - Ignore the invalid values of T1 and T2.
Server
S_RFC3633_9_IAPD_IgnoreInValidT1T2.seq [-tooloption ...]
-pkt S_RFC3633_9_IAPD_IgnoreInValidT1T2.def
-tooloption: v6eval tool option
TN(Requesting router1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Delegating router1)
Verification Points
If a delegating router receives an IA_PD with T1 greater than T2, and
both T1 and T2 are greater than 0, the delegating router ignores the
invalid values of T1 and T2 and processes the IA_PD as though the
delegating router had set T1 and T2 to 0.
The Delegating router runs like the case "T1=0 & T2=0",
That is, the parameters is determined by the client.
Format of IA_PD option in the Reply
- option-code
OPTION_IA_PD (25)
- option-length
12 + length of IA_PD-options field.
- IAID
Same as the Request.
- T1
Same as the Request.
- T2
Same as the Request.
Solicit Message
IA_PD option
T1 = 5700
T2 = 4800
| 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) T1>T2>0
| ----> | Advertise (w/ IA_PD option)
| <---- | Request (w/ IA_PD option)
| ----> | Reply (w/ IA_PD option) (*1)
| |
(*1)PASS: The TN & NUT exchanges above messages correctly.
And NUT will ignore the T1, T2.
That is, the value of fileds of IA_PD option is same as the Request message.
or
Return Reply message without IA_Prefix option.
N/A
see also RFC3633
9. Identity Association for Prefix Delegation Option
perldoc V6evalTool