seamoby-1----Page:1
2  3 

Cache Contamination Issue
Issue
Cache entries might exist for ARs that are not geographically adjacent to AR
Common Problems
Memory consumption: Current AR stores information of these AR, i.e., L2/L3 identifiers plus capabilities
Processing overhead: if capabilities are retrieved directly from these ARs, this adds protocol overhead to the current AR
Problem with sleeping interface scenario:
Consider MN with two interfaces A and B, connected to current AR through A and having interface B sleeping
MN requests CARs of current AR with radio capability of interface B
Contaminated cache would result in list of CARs that contains invalid entries, leading to e.g., failure in TAR selection, unnecessary scanning for L2 beacons, wasting of bandwidth for CAR list download
There might exist solution-specific problems!
Note
This is only a problem for the MN if the MN receives a wrong L2-L3 mapping result!
Usually, this should not happen though since non-malicious MN would present AP to current AR that it can actually hear, i.e., the AP is actually a GAAP (geographically adjacent AP)
PPT Version