Tuesday, March 16, 2010

Mobile IPv6


Then we design the system model of this Mobile IPv4 authentication mechanism. Using the MIP extension of OpenDiameter which is the open source of AAA, and modifying Dynamics which is the open source of MIPv4, we implement the cooperation of MIPv4 and AAA protocol, and finally implement the security mechanism under Mobile IPv4 environment. This paper detailedly describes how to realize every entity and modules, and finally finishes the software for this system.In the second part of the paper, we focus on the security mechanism of Mobile IPv6. First we analyse the basic Mobile IPv6 and IPSec protocol, and find the problem existed in the current protocol, which therefore makes IKE protocol introduced. Based on the general idea of RFC 3776 and RFC 4877, a solution of key exchange deployed under mobile IP environment is designed. This solution can implement IKEv2 exchange under Mobile IPv6 environment, negotiate IPSec Security Associations between mobile node and home agent before the mobile registration, which can be used later for IPSec ESP to encrypte mobile registration message and protect the privacy of mobility signal between mobile node and home agent.Then we design the system model of this Mobile IPv6 signal encryption mechanism. Using OpenIKEv2 which is the open source of IKEv2 for dynamic key exchange, modifying MIPL which is the open source of MIPv6, we implement the cooperation of MIPv6 and IKEv2 protocol, and finally implement the security mechanism under Mobile IPv6 environment. This paper detailedly describes how to realize every entity and modules, and finally finishes the software for this system.At last, based on the two system model above, test environment is set up independently. The test focuses on the protocol coherency of the system model. The analysis of test results is finally presented, which indicates that the system model of Mobile IPv4 authentication mechanism accords with RFC 4004 and the system model of Mobile IPv6 signal encryption mechanism accords with RFC 3776 and RFC 4877.

No comments:

Post a Comment