 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| n |
Suppose
MH1 moves away from MH2 towards MH7 and
|
|
|
|
has
active sessions with MH3 and MH6:
|
|
|
– |
MH2
notices that its link to MH1 is broken
|
|
|
– |
MH2
checks its routing table and finds that its link to MH1 was
|
|
|
actively
in use by MH3 and MH4
|
|
|
– |
MH2
unicasts an ¥-metric route update, with an incremented
|
|
|
destination
sequence number, to MH3 and MH4. MH3 may
|
|
|
subsequently
issue a new route request for MH4
|
|
|
– |
MH4
also notes that its route to MH1 was actively in use and
|
|
|
forwards
a ¥ -metric route update to MH6
|
|
|
– |
the ¥-metric
route update for MH1 may also be included in the
|
|
|
next
periodic limited broadcast issued by MH2
|
|
|
– |
MH6
may subsequently issue a new route request for MH1
|
|
|
– |
any
subsequent route request for MH1 which is satisfied by a route
|
|
reply
through MH2 may cause MH2 to update its route table
|
|
