CN_PingAfterDeleteBinding - Ping from MN to NUT (After Delete Binding)
Host and Router
CN_PingAfterDeleteBinding.seq [-tooloption ...] -pkt CN_PingAfterDeleteBinding.def
-tooloption: v6eval tool option
MN'
|
--------+-------+------- LinkY
|
R2 MN
| |
Link1 --------+------- --------+-------+-------+------- LinkX
| |
NUT R1
| |
Link0 --------+-----------------------+-----------------------
Link0 3ffe:501:ffff:100::/64 Link1 3ffe:501:ffff:101::/64 LinkX 3ffe:501:ffff:102::/64 home link LinkY 3ffe:501:ffff:103::/64 foreign link R1(Link0) 3ffe:501:ffff:100:200:ff:fe00:a0a0 MN 3ffe:501:ffff:102:200:ff:fe00:0005 home address MN' 3ffe:501:ffff:103:200:ff:fe00:0005 care-of address
NUT R1 MN MN'
| | | |
| <---- | | | RA
| | | |
| <-------------------- | Echo Request
| ----> | | | NS
| <---- | | | NA
| --------------------> | Echo Reply (*1)
| | | |
| <---- | | | NA
| | | |
| <-------------------- | Binding Update
| | | |
| <-------------------- | Binding Update (Lifetime is zero)
| | | |
| <-------------------- | Echo Request
| ------------> | | Echo Reply (*2)
| | | |
1. check routing table - LinkY
1.1. Host
1.1.1. R1 sends RA
1.1.2. MN' sends Echo Request
1.2.3. Wait Echo Reply
1.1.4. Receive Echo Reply
1.2. Router
1.2.1. MN' sends Echo Request
1.2.2. Wait Echo Reply or NS
1.2.3. If NS received then send NA, and wait Echo Reply again
1.2.4. Receive Echo Reply
2. overwrite NCE on NUT
2.1. R1 sends NA
3. check Binding Cache entry operation
3.1. MN' sends Binding Update to Cache a Binding
3.2. MN' sends Binding Update to Delete a Binding
3.3. MN' sends Echo Request
3.4. Wait Echo Reply
3.5. Receive Echo Reply
(*1) PASS: MN' receives Echo Reply
(*2) PASS: MN receives Echo Reply
<draft-ietf-mobileip-ipv6-15.txt>
8.2. Receiving Binding Updates
If the Binding Update is valid according to the tests above, then the Binding Update is processed further as follows:
- If the Lifetime specified in the Binding Update is nonzero and
the specified Care-of Address is not equal to the home address
for the binding, then this is a request to cache a binding for
the mobile node. If the Home Registration (H) bit is set in the
Binding Update, the Binding Update is processed according to the
procedure specified in Section 9.1; otherwise, it is processed
according to the procedure specified in Section 8.3.
- If the Lifetime specified in the Binding Update is zero or the
specified Care-of Address matches the home address for the
binding, then this is a request to delete the mobile node's
cached binding. If the Home Registration (H) bit is set in the
Binding Update, the Binding Update is processed according to the
procedure specified in Section 9.2; otherwise, it is processed
according to the procedure specified in Section 8.4.
8.4. Requests to Delete a Binding
When a node receives a Binding Update, it MUST validate it and determine the type of Binding Update according to the steps described in Section 8.2. This section describes the processing of a valid Binding Update that requests a node to delete a mobile node's binding from its Binding Cache, for which the Home Registration (H) bit is not set in the Binding Update. In this case, the receiving node MUST delete any existing entry in its Binding Cache for this mobile node.
CN_Common.def