The Experts below are selected from a list of 19950 Experts worldwide ranked by ideXlab platform
Zheng Xiang - One of the best experts on this subject based on the ideXlab platform.
-
A Mobile Table for the Communication in IPv4/v6 Mixed Networks
2016Co-Authors: Zheng XiangAbstract:RFC3344 and RFC3775 respectively, but not yet discussed Mobile IPv4/v6 in any published RFC. This paper proposes a scheme to solve one of Mobile IPv4/v6 problems which Home Agent (HA) is located in IPv4 network, Correspondent Node (CN) is located in IPv6 network, while MN moves within IPv4 network. In the solution, a gateway called Mobile IPv4/v6 translation gateway (MIPv4/v6-TG) is introduced to bridge between IPv4 network and IPv6 network, which is made up of a traditional NAT-PT gateway and a Mobile IP application level gateway (MIP-ALG) built upon the NAT-PT gateway. MIP-ALG maintains a MIP table, a data structure, which is formed by entries. We use the MIP table to realize the communication between the IPv4 entities and the IPv6 entities. The creation, usage and update processes of MIP table are described in this paper. Through the experiment we find it can realize the basic communication in IPv4/v6 mixed network. The measurement of performance test proves the solution’s efficiency. And it can work compatibly with RFC3344 and RFC3775
-
Mobile IPv4/v6 translation gateway
2016Co-Authors: Zheng XiangAbstract:RFC3344 and RFC3775 respectively, but not yet discussed Mobile IPv4/v6 in any published RFC. This paper proposes a scheme to solve one of Mobile IPv4/v6 problems which Home Agent (HA) is located in IPv4 network, Correspondent Node (CN) is located in IPv6 network, while MN moves within IPv6 network. In the solution, a gateway called Mobile IPv4/v6 translation gateway (MIPv4/v6-TG) is introduced to bridge between IPv4 network and IPv6 network, which is made up of a traditional NAT-PT gateway and a Mobile IP application level gateway (MIP-ALG) built upon the NAT-PT gateway. MIP-ALG maintains a MIP table, a data structure, which is formed by entries. And it can work compatibly with RFC3344 and RFC3775
-
Research on Mobility management based on MIP table in mixed IPv4/v6 networks
2016Co-Authors: Zheng XiangAbstract:RFC3344 and RFC3775 respectively, but not yet discussed Mobile IPv4/v6 in any published RFC. This paper proposes a scheme to solve one of Mobile IPv4/v6 problems which Home Agent (HA) locates in IPv6 network, and Correspondent Node (CN) locates in IPv4 network, while Mobile Node (MN) moves within IPv4 network. In the solution, a gateway called Mobile IPv4/v6 translation gateway (MIPv4/v6-TG) is introduced to bridge between IPv4 network and IPv6 network, which is made up of a traditional NAT-PT gateway and a Mobile IP application level gateway (MIP-ALG) built upon the NAT-PT gateway. MIP-ALG maintains a MIP table, a data structure, which is formed by entries. We use the MIP table to realize the communication between the IPv4 entities and the IPv6 entities. The creation, usage and update processes of MIP table are described in this paper. And it can work compatibly with RFC3344 and RFC3775. Keywords—MobileIP(MIP;NAT-PT;Mobile IP application level gateway (MIP-ALG);Mobile IPv4/v6 translation gateway (MIPv4/v6-TG), MIP Tabl
-
mobile ipv4 v6 translation gateway
International Conference on Computer Science and Electronics Engineering, 2013Co-Authors: Zheng XiangAbstract:IETF has specified Mobile IPv4 and Mobile IPv6 in RFC3344 and RFC3775 respectively, but not yet discussed Mobile IPv4/v6 in any published RFC. This paper proposes a scheme to solve one of Mobile IPv4/v6 problems which Home Agent (HA) is located in IPv4 network, Correspondent Node (CN) is located in IPv6 network, while MN moves within IPv6 network. In the solution, a gateway called Mobile IPv4/v6 translation gateway (MIPv4/v6-TG) is introduced to bridge between IPv4 network and IPv6 network, which is made up of a traditional NAT-PT gateway and a Mobile IP application level gateway (MIP-ALG) built upon the NAT-PT gateway. MIP-ALG maintains a MIP table, a data structure, which is formed by entries. And it can work compatibly with RFC3344
-
research on mobile communication in ipv4 v6 mixed networks
International Conference on Computer Science and Service System, 2012Co-Authors: Zheng XiangAbstract:IETF has specified Mobile IPv4 and Mobile IPv6 in RFC3344 and RFC3775 respectively, but not yet discussed Mobile IPv4/v6 in any published RFC. This paper proposes a solution to Mobile IPv4/v6 problems and gives an example when Home Agent (HA ) and Correspondent Node (CN ) located in IPv4 network, Mobile Node (MN) moving in IPv4/v6 mixed networks. A gateway called Mobile IPv4/v6 translation gateway (MIPv4/v6-TG) is introduced to bridge between IPv4 network and IPv6 network, which is made up of a NAT-PT gateway and a Mobile IP application level gateway (MIP-ALG) built upon the NAT-PT gateway. On IPv4 side, MIPv4/v6-TG acts as one of the Mobile IPv4 entities to interact with other IPv4 entities under the specification of RFC3344. On IPv6 side, MIPv4/v6-TG acts as one of the Mobile IPv6 entities to interact with other IPv6 entities under the specification of RFC3775. Inside the gateway, Mobile IP related packets and messages received or sent by the entities that the gateway acts as are translated between Mobile IPv4 format and Mobile IPv6 format. In this way, the Mobile IP entities in IPv4 network and the Mobile IP entities in IPv6 network will be transparent to each other.
Charles E Perkins - One of the best experts on this subject based on the ideXlab platform.
-
ip mobility support for ipv4 revised
RFC, 2010Co-Authors: Charles E PerkinsAbstract:This document specifies protocol enhancements that allow transparent routing of IP datagrams to mobile nodes in the Internet. Each mobile node is always identified by its Home address, regardless of its current point of attachment to the Internet. While situated away from its Home, a mobile node is also associated with a care-of address, which provides information about its current point of attachment to the Internet. The protocol provides for registering the care-of address with a Home Agent. The Home Agent sends datagrams destined for the mobile node through a tunnel to the care-of address. After arriving at the end of the tunnel, each datagram is then delivered to the mobile node.
-
foreign Agent error extension for mobile ipv4
RFC, 2006Co-Authors: Charles E PerkinsAbstract:This document specifies a new extension for use by Foreign Agents operating Mobile IP for IPv4. The new extension option allows a foreign Agent to supply an error code without disturbing the data supplied by the Home Agent within the Registration Reply message. In this way, the mobile node can verify that the Registration Reply message was generated by the Home Agent even in cases where the foreign Agent is required by protocol to insert new status information into the Registration Reply message.
-
authentication authorization and accounting aaa registration keys for mobile ipv4
RFC, 2005Co-Authors: Charles E PerkinsAbstract:Authentication, Authorization, and Accounting (AAA) servers, such as RADIUS and DIAMETER, are in use within the Internet today to provide authentication and authorization services for dial-up computers. Mobile IP for IPv4 requires strong authentication between the mobile node and its Home Agent. When the mobile node shares an AAA Security Association with its Home AAA server, however, it is possible to use that AAA Security Association to create derived Mobility Security Associations between the mobile node and its Home Agent, and again between the mobile node and the foreign Agent currently offering connectivity to the mobile node. This document specifies extensions to Mobile IP registration messages that can be used to create Mobility Security Associations between the mobile node and its Home Agent, and/or between the mobile node and a foreign Agent. [STANDARDS-TRACK]
-
authentication authorization and accounting aaa registration keys for mobile ipv4
RFC, 2005Co-Authors: Charles E PerkinsAbstract:Authentication, Authorization, and Accounting (AAA) servers, such as RADIUS and DIAMETER, are in use within the Internet today to provide authentication and authorization services for dial-up computers. Mobile IP for IPv4 requires strong authentication between the mobile node and its Home Agent. When the mobile node shares an AAA Security Association with its Home AAA server, however, it is possible to use that AAA Security Association to create derived Mobility Security Associations between the mobile node and its Home Agent, and again between the mobile node and the foreign Agent currently offering connectivity to the mobile node. This document specifies extensions to Mobile IP registration messages that can be used to create Mobility Security Associations between the mobile node and its Home Agent, and/or between the mobile node and a foreign Agent. [STANDARDS-TRACK]
-
mobile ipv4 regional registration
RFC, 2004Co-Authors: Eva Fogelstroem, Annika Jonsson, Charles E PerkinsAbstract:Using Mobile IP, a mobile node registers with its Home Agent each time it changes care-of address. This document describes a new kind of "regional registrations", i.e., registrations local to the visited domain. The regional registrations are performed via a new network entity called a Gateway Foreign Agent (GFA) and introduce a layer of hierarchy in the visited domain. Regional registrations reduce the number of signaling messages to the Home network, and reduce the signaling delay when a mobile node moves from one foreign Agent to another within the same visited domain. This document is an optional extension to the Mobile IPv4 protocol. This memo defines an Experimental Protocol for the Internet community.
Du Jian-jun - One of the best experts on this subject based on the ideXlab platform.
-
Simulation of Binding Update Message Authentication Based on Home Agent
Computer Simulation, 2008Co-Authors: Du Jian-junAbstract:Binding update registration is the foundation of actualizing IPv6 mobility and route optimization,and at the same time,it brings a series of security menace.The authentication of binding update acknowledgement message is the key to solve the problem.Using the trust relationship and shared key between mobile node and Home Agent,a novel binding update registration authentication mechanism based on Home Agent is proposed and the simulation model in Mobile IPv6 network is built.By the comparative analysis of the simulation results in the same platform,the pro- posed mechanism has better performance in binding update security and route reachable dependency than other mech- anisms of same research field.Since the controllability and management of Home Agent is utilized,deployment of Mo- bile IPv6 becomes flexible.
Pascal Thubert - One of the best experts on this subject based on the ideXlab platform.
-
network mobility route optimization solution space analysis
RFC, 2007Co-Authors: Masafumi Watari, Chanwah Ng, Fan Zhao, Pascal ThubertAbstract:With current Network Mobility (NEMO) Basic Support, all communications to and from Mobile Network Nodes must go through the Mobile Router and Home Agent (MRHA) tunnel when the mobile network is away. This results in increased length of packet route and increased packet delay in most cases. To overcome these limitations, one might have to turn to Route Optimization (RO) for NEMO. This memo documents various types of Route Optimization in NEMO and explores the benefits and tradeoffs in different aspects of NEMO Route Optimization. This memo provides information for the Internet community.
-
network mobility route optimization problem statement
RFC, 2007Co-Authors: Chanwah Ng, Masafumi Watari, Pascal Thubert, Fan ZhaoAbstract:With current Network Mobility (NEMO) Basic Support, all communications to and from Mobile Network Nodes must go through the bi-directional tunnel established between the Mobile Router and Home Agent when the mobile network is away. This sub-optimal routing results in various inefficiencies associated with packet delivery, such as increased delay and bottleneck links leading to traffic congestion, which can ultimately disrupt all communications to and from the Mobile Network Nodes. Additionally, with nesting of Mobile Networks, these inefficiencies get compounded, and stalemate conditions may occur in specific dispositions. This document investigates such problems and provides the motivation behind Route Optimization (RO) for NEMO. This memo provides information for the Internet community.
-
network mobility nemo basic support protocol
RFC, 2005Co-Authors: Alexandru Petrescu, Pascal Thubert, Ryuji Wakikawa, Vijay DevarapalliAbstract:This document describes the Network Mobility (NEMO) Basic Support protocol that enables Mobile Networks to attach to different points in the Internet. The protocol is an extension of Mobile IPv6 and allows session continuity for every node in the Mobile Network as the network moves. It also allows every node in the Mobile Network to be reachable while moving around. The Mobile Router, which connects the network to the Internet, runs the NEMO Basic Support protocol with its Home Agent. The protocol is designed so that network mobility is transparent to the nodes inside the Mobile Network. [STANDARDS-TRACK]
Kent K. Leung - One of the best experts on this subject based on the ideXlab platform.
-
generic routing encapsulation gre key extension for mobile ipv4
RFC, 2011Co-Authors: Parviz Yegani, Kent K. Leung, Kuntal Chowdhury, Avi Lior, Jay NavaliAbstract:The GRE specification contains a Key field, which MAY contain a value that is used to identify a particular GRE data stream. This specification defines a new Mobile IP extension that is used to exchange the value to be used in the GRE Key field. This extension further allows the Mobility Agents to setup the necessary protocol interfaces prior to receiving the mobile's traffic. The new extension option allows a foreign Agent to request GRE tunneling without disturbing the Home Agent behavior specified for Mobile Ipv4. GRE tunneling provides an advantage that allows operator's private Home networks to be overlaid and allows the HA to provide overlapping Home addresses to different subscribers. When the tuple < Care of Address, Home Address and Home Agent Address > is the same across multiple subscriber sessions, GRE tunneling will provide a means for the FA and HA to identify data streams for the individual sessions based on the GRE key. In the absence of this key identifier, the data streams cannot be distinguished from each other, a significant drawback when using IP-in-IP tunneling.
-
network mobility nemo extensions for mobile ipv4
RFC, 2008Co-Authors: Vidya Narayanan, Kent K. Leung, Alexandru Petrescu, Gopal DommetyAbstract:This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks.
-
network mobility nemo extensions for mobile ipv4
RFC, 2008Co-Authors: Vidya Narayanan, Kent K. Leung, Alexandru Petrescu, Gopal DommetyAbstract:This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks.
-
mobile ipv4 message string extension
RFC, 2007Co-Authors: Venkateshwara Sastry, Kent K. Leung, Alpesh PatelAbstract:This document specifies a new extension for use in Mobile IPv4. This extension can be added by the Home Agent and the Foreign Agent to Registration Reply messages. This extension carries a text string that is intended for the user of the Mobile Node. [STANDARDS-TRACK]
-
mobile ipv4 dynamic Home Agent ha assignment
RFC, 2006Co-Authors: Alpesh Patel, Milind M Kulkarni, Kent K. LeungAbstract:Mobile IPv4 (RFC 3344) uses the Home Agent (HA) to anchor sessions of a roaming mobile node (MN). This document proposes a messaging mechanism for dynamic Home Agent assignment and HA redirection. The goal is to provide a mechanism to assign an optimal HA for a Mobile IP session while allowing any suitable method for HA selection. [STANDARDS-TRACK]
