mobopts-7----Page:6
1 2 3 4 5 6 7
|
Requirements This framework should accommodate with future instances of the NetLMM protocol, and be flexible enough to allow and support possible optimizations of the NetLMM procedures. This framework does not aim at replacing L3 procedures rather to improve them by facilitating the information exchange between the host and the AR even prior to full network configuration. While several deployment scenarios of the MIHF and its relation to the upper layers are possible (IP stack, LMP engine), a more clear communication model needs to be agreed and specified. Need to align different identifiers. Link layer events have to be carefully registered by whoever can use them to trigger procedures. A single event can be forwarded to more than one high level entity, inducing parallel behavior that might not be desirable. The host must be able to store the previous network configuration information, both for detecting subnet changes upon attachment, and also to report it to the nAR upon a reactive handover. Sufficient authentication of devices supplying link-layer events has to be considered. For example, reachability and attachment notifications may be falsely asserted by an attacker |