Future wireless networks : key issues and a survey ( ID / locator split perspective )
---
paper_title: Proxy Mobile IPv6

paper_content:

Network-based mobility management enables IP mobility for a host ::: without requiring its participation in any mobility-related signaling. ::: The network is responsible for managing IP mobility on behalf of the ::: host. The mobility entities in the network are responsible for ::: tracking the movements of the host and initiating the required ::: mobility signaling on its behalf. This specification describes a ::: network-based mobility management protocol and is referred to as Proxy ::: Mobile IPv6. [STANDARDS-TRACK]
---
paper_title: IP Mobility Support for IPv4

paper_content:

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.
---
paper_title: Internet 3.0: Ten Problems with Current Internet Architecture and Solutions for the Next Generation

paper_content:

The basic ideas of the Internet architecture were developed 30+ years ago. In these 30 years, we have learnt a lot about networking and packet switching. Is this the way we would design the Internet if we were to start it now? This paper is an attempt to answer this question raised by US National Science Foundation, which has embarked on the design of the next generation Internet called GENI. In this paper, we point out key problems with the current Internet Architecture and propose directions for the solutions. We propose a general architectural framework for the next generation Internet, which we call Internet 3.0. The next generation Internet should be secure. It should allow business to set their boundaries and enforce their policies inside their boundaries. It should allow governments to set rules that protect their citizens on the Internet the same way they protect them on other means of transports. It should allow receivers to set policies for how and where they receive their information. They should have freedom to select their names, IDs and addresses with as little centralized control as possible. The architecture should be general enough to allow different governments to have different rules. Information transport architecture should provide at least as much control and freedom as the goods transport networks provide. We propose the framework of an architecture that supports all these requirements.
---
paper_title: Freeze-TCP: a true end-to-end TCP enhancement mechanism for mobile environments

paper_content:

Optimizing TCP (transport layer) for mobility has been researched extensively. We present a brief summary of existing results which indicates that most schemes require intermediaries (such as base stations) to monitor the TCP traffic and actively participate in flow control in order to enhance performance. Although these methods simulate end-to-end semantics, they do not comprise true end-to-end signaling. As a result, these techniques are not applicable when the IP payload is encrypted. For instance IPSEC, which is expected to be standard under IPv6, encrypts the entire IP payload making it impossible for intermediaries to monitor TCP traffic unless those entities are part of the security association. In addition, these schemes require changes (in the TCP/IP code) at intermediate nodes making it difficult for the mobile clients to inter-operate with the existing infrastructure. In this paper we explore the "freeze-TCP" mechanism which is a true end-to-end scheme and does not require the involvement of any intermediaries (such as base stations) for flow control. Furthermore, this scheme does not require any changes on the "sender side" or intermediate routers; changes in TCP code are restricted to the mobile client side, making it possible to fully inter-operate with the existing infrastructure. We then outline a method which integrates the best attributes of freeze-TCP and some existing solutions. Performance results highlight the importance of pro-active action/signaling by the mobile-host. The data indicate that in most cases, simply reacting to disconnections tends to yield lower performance than pro-active mechanisms such as freeze-TCP.
---
paper_title: Internet indirection infrastructure

paper_content:

Attempts to generalize the Internet's point-to-point communication abstraction to provide services like multicast, anycast, and mobility have faced challenging technical problems and deployment barriers. To ease the deployment of such services, this paper proposes a general, overlay-based Internet Indirection Infrastructure (i3) that offers a rendezvous-based communication abstraction. Instead of explicitly sending a packet to a destination, each packet is associated with an identifier; this identifier is then used by the receiver to obtain delivery of the packet. This level of indirection decouples the act of sending from the act of receiving, and allows i3 to efficiently support a wide variety of fundamental communication services. To demonstrate the feasibility of this approach, we have designed and built a prototype based on the Chord lookup protocol.
---
paper_title: Flow Bindings in Mobile IPv6 and Nemo Basic Support

paper_content:

This document introduces extensions to Mobile IPv6 [1] and Nemo Basic ::: Support [2] that allow nodes to bind one or more flows to a care-of ::: address. These extensions allow multihomed nodes to take full ::: advantage of the different properties associated with each of their ::: interfaces.
---
paper_title: TCP-R: TCP mobility support for continuous operation

paper_content:

The TCP-R (TCP Redirection) is an extension of TCP, which maintains active TCP connections when the disconnection occurs due to the change of the IP address or the change of the network device. In mobile computing environments, the IP address may be changed frequently as the host moves across subnets or changes a network device. However, it is difficult for most network applications to work continuously in such a situation. There is much research to support such dynamics in the network layer, but these attempts in the IP layer tend to incur some complexity. This paper is intended as an investigation of the end-to-end mobility support in transport layer. We developed the simple and secure redirection mechanism in TCP, which enables us to keep our working activities without any intermediate agents. We also show that TCP-R can serve as a solution to the retransmission timeout problem which frequently occurs in mobile environments. We implemented and evaluated a prototype of TCP-R by modifying FreeBSD. The measured performance indicates that TCP-R can maintain operation continuously with minimal overhead and complexity.
---
paper_title: A review of mobility support paradigms for the internet

paper_content:

Abstract With the development of mobile communication and Internet technology, there is a strong need to provide connectivity for roaming devices to communicate to other communication end point in the Internet at any time and anywhere. The key issue of this vision is how to support mobility in TCP/IP networks. In this paper, we review the TCP/IP protocol stack and analyze the problems associated with it in a mobile environment. We then investigate the mobility support techniques and existing solutions to provide mobility support in the Internet. We classify the proposed solutions based on the protocol layers and present examples for each category. We also provide a comparison of the different solutions belonging to different categories and in the same category, including their advantages and disadvantages, and conclude that there is no single solution perfectly addresses mobility support for the Internet. We conclude this survey with a recommendation of features that need to be satisfied in Internet mobility support.
---
paper_title: Multiple Care-of Addresses Registration

paper_content:

According to the current Mobile IPv6 specification, a mobile node may ::: have several care-of addresses, but only one, termed the primary care- ::: of address, can be registered with its home agent and the ::: correspondent nodes. However, for matters of cost, bandwidth, delay, ::: etc, it is useful for the mobile node to get Internet access through ::: multiple access media simultaneously, in which case multiple active ::: IPv6 care-of addresses would be assigned to the mobile node. We thus ::: propose Mobile IPv6 extensions designed to register multiple care-of ::: addresses bound to a single Home Address instead of the sole primary ::: care-of address. For doing so, a new identification number must be ::: carried in each binding for the receiver to distinguish between the ::: bindings corresponding to the same Home Address. Those extensions are ::: targeted to NEMO (Network Mobility) Basic Support as well as to Mobile ::: IPv6.
---
paper_title: MSOCKS: an architecture for transport layer mobility

paper_content:

Mobile nodes of the future will be equiped with multiple network interfaces to take advantage of overlay networks, yet no current mobility systems provide full support for the simultaneous use of multiple interfaces. The need for such support arises when multiple connectivity options are available with different cost, coverage, latency and bandwidth characteristics, and applications want their data to flow over the interface that best matches the characteristics of the data. We present an architecture called transport layer mobility that allows mobile nodes to not only change their point of attachment to the Internet, but also to control which network interfaces are used for the different kinds of data leaving from and arriving at the mobile node. We implement our transport layer mobility scheme using a split connection proxy architecture and a new technique called TCP splice that gives split connection proxy systems the same end to-end semantics as normal TCP connections.
---
paper_title: Designing DCCP: congestion control without reliability

paper_content:

Fast-growing Internet applications like streaming media and telephony prefer timeliness to reliability, making TCP a poor fit. Unfortunately, UDP, the natural alternative, lacks congestion control. High-bandwidth UDP applications must implement congestion control themselves-a difficult task-or risk rendering congested networks unusable. We set out to ease the safe deployment of these applications by designing a congestion-controlled unreliable transport protocol. The outcome, the Datagram Congestion Control Protocol or DCCP, adds to a UDP-like foundation the minimum mechanisms necessary to support congestion control. We thought those mechanisms would resemble TCP's, but without reliability and, especially, cumulative acknowledgements, we had to reconsider almost every aspect of TCP's design. The resulting protocol sheds light on how congestion control interacts with unreliable transport, how modern network constraints impact protocol design, and how TCP's reliable bytestream semantics intertwine with its other mechanisms, including congestion control.
---
paper_title: Multihoming with Mobile IP

paper_content:

Mobile IP is the standard for mobility management in IP networks. With today’s emerging possibilities within wireless broadband communication, mobility within networks will increase. New applications and protocols will be created and Mobile IP is important to this development, since Mobile IP support is needed to allow mobile hosts to move between networks with maintained connectivity. This article describes multihomed Mobile IP enabling mobile hosts to register multiple care-of addresses at the home agent, to enhance the performance of wireless network connectivity. Flows can be load-balanced between care-of addresses to achieve a more reliable connectivity. A prototype is also described.
---
paper_title: Fast Handovers for Mobile IPv6

paper_content:

Mobile IPv6 enables a Mobile Node to maintain its connectivity to the ::: Internet when moving from one Access Router to another, a process ::: referred to as handover. During handover, there is a period during ::: which the Mobile Node is unable to send or receive packets because of ::: link switching delay and IP protocol operations. This "handover ::: latency" resulting from standard Mobile IPv6 procedures, namely ::: movement detection, new Care of Address configuration, and Binding ::: Update, is often unacceptable to real-time traffic such as Voice over ::: IP. Reducing the handover latency could be beneficial to non-real- ::: time, throughput-sensitive applications as well. This document ::: specifies a protocol to improve handover latency due to Mobile IPv6 ::: procedures. This document does not address improving the link ::: switching latency. This memo defines an Experimental Protocol for the ::: Internet community.
---
paper_title: Proxy Mobile IPv6

paper_content:

Network-based mobility management enables IP mobility for a host ::: without requiring its participation in any mobility-related signaling. ::: The network is responsible for managing IP mobility on behalf of the ::: host. The mobility entities in the network are responsible for ::: tracking the movements of the host and initiating the required ::: mobility signaling on its behalf. This specification describes a ::: network-based mobility management protocol and is referred to as Proxy ::: Mobile IPv6. [STANDARDS-TRACK]
---
paper_title: IP Mobility Support for IPv4

paper_content:

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.
---
paper_title: Hierarchical Mobile IPv6 (HMIPv6) Mobility Management

paper_content:

This document introduces extensions to Mobile IPv6 and IPv6 Neighbour ::: Discovery to allow for local mobility handling. Hierarchical mobility ::: management for Mobile IPv6 is designed to reduce the amount of ::: signalling between the Mobile Node, its Correspondent Nodes, and its ::: Home Agent. The Mobility Anchor Point (MAP) described in this document ::: can also be used to improve the performance of Mobile IPv6 in terms of ::: handover speed.
---
paper_title: Mobile-TCP: an asymmetric transport protocol design for mobile systems

paper_content:

In this paper, we advocate the use, propose the design, and describe the implementation of an asymmetric transport-layer protocol for mobile systems. In an asymmetrically designed protocol, peer functions are implemented through algorithms and procedures that are of substantially different complexity, with the lower complexity procedures used on the mobile device. We have devised and implemented an example of such a communication protocol, termed by us Mobile-TCP that provides the TCP functionality. Although Mobile-TCP is based on the indirect interaction model, the semantics of the TCP protocol are preserved.
---
paper_title: At what layer does mobility belong?

paper_content:

Internetworking is a complex problem, traditionally tackled by splitting responsibilities between several layers of protocols arranged in a stack. A shortcoming of the current Internet suite's layers is that the responsibilities of individual layers are somewhat ill defined. The result is that frequently a feature may cause problems for higher layers when it unexpectedly exists lower in the stack, or may be unnecessarily and inefficiently implemented in multiple layers. Mobility is one such feature with no well defined place in classical protocol stacks. If a link layer hands over between two distinctly administered networks, a network layer protocol will likely need to acquire a new address. Similarly, if mobility is implemented at the network layer, such as with mobile IP, transport layer protocols must be prepared to deal with a slew of problems (rapid changes in available capacity and delay, the asymmetry of triangle routes, and security policies, to name a few). Code for higher-level protocols (above transport) is less frequently reused, so higher-layer mobility schemes fail to leverage the large base of TCP sockets code. We discuss the various strengths and weaknesses of implementing mobility at three different layers of the protocol stack, concluding that a transport layer mobility scheme is likely to suit today's mobile Internet users best, and that ideally there should be more communication between layers to avoid conflict and inefficiency.
---
paper_title: Fundamentals of WiMAX: Understanding Broadband Wireless Networking

paper_content:

This is the eBook version of the printed book. Praise for Fundamentals of WiMAX "This book is one of the most comprehensive books I have reviewed ... it is a must-read for engineers and students planning to remain current or who plan to pursue a career in telecommunications. I have reviewed other publications on WiMAX and have been disappointed. This book is refreshing in that it is clear that the authors have the in-depth technical knowledge and communications skills to deliver a logically laid out publication that has substance to it." Ron Resnick, President, WiMAX Forum "This is the first book with a great introductory treatment of WiMAX technology. It should be essential reading for all engineers involved in WiMAX. The high-level overview is very useful for those with non-technical background. The introductory sections for OFDM and MIMO technologies are very useful for those with implementation background and some knowledge of communication theory. The chapters covering physical and MAC layers are at the appropriate level of detail. In short, I recommend this book to systems engineers and designers at different layers of the protocol, deployment engineers, and even students who are interested in practical applications of communication theory." Siavash M. Alamouti, Chief Technology Officer, Mobility Group, Intel "This is a very well-written, easy-to-follow, and comprehensive treatment of WiMAX. It should be of great interest." Dr. Reinaldo Valenzuela, Director of Wireless Research, Bell Labs "Fundamentals of WiMAX is a comprehensive guide to WiMAX from both industry and academic viewpoints, which is an unusual accomplishment. I recommend it to anyone who is curious about this exciting new standard." Dr. Teresa Meng, Professor, Stanford University, Founder and Director, Atheros Communications "Andrews, Ghosh, and Muhamed have provided a clear, concise, and well-written text on 802.16e/WiMAX. The book provides both the breadth and depth to make sense of the highly complicated 802.16e standard. I would recommend this book to both development engineers and technical managers who want an understating of WiMAX and insight into 4G modems in general." Paul Struhsaker, VP of Engineering, Chipset platforms, Motorola Mobile Device Business Unit, former vice chair of IEEE 802.16 working group "Fundamentals of WiMAX is written in an easy-to-understand tutorial fashion. The chapter on multiple antenna techniques is a very clear summary of this important technology and nicely organizes the vast number of different proposed techniques into a simple-to-understand framework." Dr. Ender Ayanoglu, Professor, University of California, Irvine, Editor-in-Chief, IEEE Transactions on Communications "Fundamentals of WiMAX is a comprehensive examination of the 802.16/WiMAX standard and discusses how to design, develop, and deploy equipment for this wireless communication standard. It provides both insightful overviews for those wanting to know what WiMAX is about and comprehensive, in-depth chapters on technical details of the standard, including the coding and modulation, signal processing methods, Multiple-Input Multiple-Output (MIMO) channels, medium access control, mobility issues, link-layer performance, and system-level performance." Dr. Mark C. Reed, Principal Researcher, National ICT Australia, Adjunct Associate Professor, Australian National University "This book is an excellent resourc...
---
paper_title: A review of mobility support paradigms for the internet

paper_content:

Abstract With the development of mobile communication and Internet technology, there is a strong need to provide connectivity for roaming devices to communicate to other communication end point in the Internet at any time and anywhere. The key issue of this vision is how to support mobility in TCP/IP networks. In this paper, we review the TCP/IP protocol stack and analyze the problems associated with it in a mobile environment. We then investigate the mobility support techniques and existing solutions to provide mobility support in the Internet. We classify the proposed solutions based on the protocol layers and present examples for each category. We also provide a comparison of the different solutions belonging to different categories and in the same category, including their advantages and disadvantages, and conclude that there is no single solution perfectly addresses mobility support for the Internet. We conclude this survey with a recommendation of features that need to be satisfied in Internet mobility support.
---
paper_title: Fast Handovers for Mobile IPv6

paper_content:

Mobile IPv6 enables a Mobile Node to maintain its connectivity to the ::: Internet when moving from one Access Router to another, a process ::: referred to as handover. During handover, there is a period during ::: which the Mobile Node is unable to send or receive packets because of ::: link switching delay and IP protocol operations. This "handover ::: latency" resulting from standard Mobile IPv6 procedures, namely ::: movement detection, new Care of Address configuration, and Binding ::: Update, is often unacceptable to real-time traffic such as Voice over ::: IP. Reducing the handover latency could be beneficial to non-real- ::: time, throughput-sensitive applications as well. This document ::: specifies a protocol to improve handover latency due to Mobile IPv6 ::: procedures. This document does not address improving the link ::: switching latency. This memo defines an Experimental Protocol for the ::: Internet community.
---
paper_title: Proxy Mobile IPv6

paper_content:

Network-based mobility management enables IP mobility for a host ::: without requiring its participation in any mobility-related signaling. ::: The network is responsible for managing IP mobility on behalf of the ::: host. The mobility entities in the network are responsible for ::: tracking the movements of the host and initiating the required ::: mobility signaling on its behalf. This specification describes a ::: network-based mobility management protocol and is referred to as Proxy ::: Mobile IPv6. [STANDARDS-TRACK]
---
paper_title: IP Mobility Support for IPv4

paper_content:

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.
---
paper_title: PETS: Persistent TCP using simple freeze

paper_content:

Mobile applications often get disconnected because TCP times out when a user moves from one location and reconnects at another location. This happens even with the use of Mobile IP since the Mobile IP hides the IP address change from TCP but does nothing to prevent it from timing out. TCP freeze is a technique that is already part of TCP implementations and allows a receiver to stop the transmitter from sending further data when the receiver's buffers are full. In our proposed PErsistent TCP using Simple freeze (PETS) framework, we combine the TCP freeze and Mobile IP to prevent TCP from disconnecting during mobile operations. No modifications of the TCP or IP protocol are needed. The required PETS module can be implemented in mobile agents which are part of the Mobile IP or in IP routers. This flexibility allows our technique to be deployed incrementally with PETS-aware hosts or PETS-aware routers intermixed with legacy hosts and legacy routers with or without the Mobile IP.
---
paper_title: Freeze-TCP: a true end-to-end TCP enhancement mechanism for mobile environments

paper_content:

Optimizing TCP (transport layer) for mobility has been researched extensively. We present a brief summary of existing results which indicates that most schemes require intermediaries (such as base stations) to monitor the TCP traffic and actively participate in flow control in order to enhance performance. Although these methods simulate end-to-end semantics, they do not comprise true end-to-end signaling. As a result, these techniques are not applicable when the IP payload is encrypted. For instance IPSEC, which is expected to be standard under IPv6, encrypts the entire IP payload making it impossible for intermediaries to monitor TCP traffic unless those entities are part of the security association. In addition, these schemes require changes (in the TCP/IP code) at intermediate nodes making it difficult for the mobile clients to inter-operate with the existing infrastructure. In this paper we explore the "freeze-TCP" mechanism which is a true end-to-end scheme and does not require the involvement of any intermediaries (such as base stations) for flow control. Furthermore, this scheme does not require any changes on the "sender side" or intermediate routers; changes in TCP code are restricted to the mobile client side, making it possible to fully inter-operate with the existing infrastructure. We then outline a method which integrates the best attributes of freeze-TCP and some existing solutions. Performance results highlight the importance of pro-active action/signaling by the mobile-host. The data indicate that in most cases, simply reacting to disconnections tends to yield lower performance than pro-active mechanisms such as freeze-TCP.
---
paper_title: MSOCKS: an architecture for transport layer mobility

paper_content:

Mobile nodes of the future will be equiped with multiple network interfaces to take advantage of overlay networks, yet no current mobility systems provide full support for the simultaneous use of multiple interfaces. The need for such support arises when multiple connectivity options are available with different cost, coverage, latency and bandwidth characteristics, and applications want their data to flow over the interface that best matches the characteristics of the data. We present an architecture called transport layer mobility that allows mobile nodes to not only change their point of attachment to the Internet, but also to control which network interfaces are used for the different kinds of data leaving from and arriving at the mobile node. We implement our transport layer mobility scheme using a split connection proxy architecture and a new technique called TCP splice that gives split connection proxy systems the same end to-end semantics as normal TCP connections.
---
paper_title: Designing DCCP: congestion control without reliability

paper_content:

Fast-growing Internet applications like streaming media and telephony prefer timeliness to reliability, making TCP a poor fit. Unfortunately, UDP, the natural alternative, lacks congestion control. High-bandwidth UDP applications must implement congestion control themselves-a difficult task-or risk rendering congested networks unusable. We set out to ease the safe deployment of these applications by designing a congestion-controlled unreliable transport protocol. The outcome, the Datagram Congestion Control Protocol or DCCP, adds to a UDP-like foundation the minimum mechanisms necessary to support congestion control. We thought those mechanisms would resemble TCP's, but without reliability and, especially, cumulative acknowledgements, we had to reconsider almost every aspect of TCP's design. The resulting protocol sheds light on how congestion control interacts with unreliable transport, how modern network constraints impact protocol design, and how TCP's reliable bytestream semantics intertwine with its other mechanisms, including congestion control.
---
paper_title: TCP-R: TCP mobility support for continuous operation

paper_content:

The TCP-R (TCP Redirection) is an extension of TCP, which maintains active TCP connections when the disconnection occurs due to the change of the IP address or the change of the network device. In mobile computing environments, the IP address may be changed frequently as the host moves across subnets or changes a network device. However, it is difficult for most network applications to work continuously in such a situation. There is much research to support such dynamics in the network layer, but these attempts in the IP layer tend to incur some complexity. This paper is intended as an investigation of the end-to-end mobility support in transport layer. We developed the simple and secure redirection mechanism in TCP, which enables us to keep our working activities without any intermediate agents. We also show that TCP-R can serve as a solution to the retransmission timeout problem which frequently occurs in mobile environments. We implemented and evaluated a prototype of TCP-R by modifying FreeBSD. The measured performance indicates that TCP-R can maintain operation continuously with minimal overhead and complexity.
---
paper_title: Mobile-TCP: an asymmetric transport protocol design for mobile systems

paper_content:

In this paper, we advocate the use, propose the design, and describe the implementation of an asymmetric transport-layer protocol for mobile systems. In an asymmetrically designed protocol, peer functions are implemented through algorithms and procedures that are of substantially different complexity, with the lower complexity procedures used on the mobile device. We have devised and implemented an example of such a communication protocol, termed by us Mobile-TCP that provides the TCP functionality. Although Mobile-TCP is based on the indirect interaction model, the semantics of the TCP protocol are preserved.
---
paper_title: The paths toward IPv6 multihoming

paper_content:

A powder metallurgical method of producing metal bodies using spherical powder, produced by inert gas atomization, from magnetizable material with a particle size distribution closely approximating the so called Fuller curve for maximum density packing of spherical particles. Said powder is magnetized and filled into a form, which may take place before or after magnetization, said mixed and magnetized powder then sintered in said form with the exclusion of air, to produce a sintered body without communicating porosity.
---
paper_title: MILSA: A Mobility and Multihoming Supporting Identifier Locator Split Architecture for Naming in the Next Generation Internet

paper_content:

Naming and addressing are important issues for next generation Internet (NGI). In this paper, we discuss a new mobility and multihoming supporting identifier locator split architecture (MILSA). There are three main contributions of our solution. First, we separate trust relationships (realms) from connectivity (zones). A hierarchical identifier system for the realms and a Realm Zone Bridging Server (RZBS) infrastructure that performs the bridging function is introduced. Second, we separate the signaling and data plane functions to improve the performance and support mobility. Third, to provide transparency to the upper layer applications, identifier locator split happens in network layer. A Hierarchical URI-like Identifier (HUI) is used by the upper layers and is mapped to a locators set by HUI Mapping Sublayer (HMS) through interaction with RZBS infrastructure. Further scenarios description and analysis show the benefits of this scheme for routing scalability, mobility and multihoming.
---
paper_title: IP Mobility Support for IPv4

paper_content:

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.
---
paper_title: Multiple Care-of Addresses Registration

paper_content:

According to the current Mobile IPv6 specification, a mobile node may ::: have several care-of addresses, but only one, termed the primary care- ::: of address, can be registered with its home agent and the ::: correspondent nodes. However, for matters of cost, bandwidth, delay, ::: etc, it is useful for the mobile node to get Internet access through ::: multiple access media simultaneously, in which case multiple active ::: IPv6 care-of addresses would be assigned to the mobile node. We thus ::: propose Mobile IPv6 extensions designed to register multiple care-of ::: addresses bound to a single Home Address instead of the sole primary ::: care-of address. For doing so, a new identification number must be ::: carried in each binding for the receiver to distinguish between the ::: bindings corresponding to the same Home Address. Those extensions are ::: targeted to NEMO (Network Mobility) Basic Support as well as to Mobile ::: IPv6.
---
paper_title: Multihoming with Mobile IP

paper_content:

Mobile IP is the standard for mobility management in IP networks. With today’s emerging possibilities within wireless broadband communication, mobility within networks will increase. New applications and protocols will be created and Mobile IP is important to this development, since Mobile IP support is needed to allow mobile hosts to move between networks with maintained connectivity. This article describes multihomed Mobile IP enabling mobile hosts to register multiple care-of addresses at the home agent, to enhance the performance of wireless network connectivity. Flows can be load-balanced between care-of addresses to achieve a more reliable connectivity. A prototype is also described.
---
paper_title: HIERARCHICAL PEER-TO-PEER SYSTEMS

paper_content:

Structured peer-to-peer (P2P) lookup services organize peers into a flat overlay network and offer distributed hash table (DHT) functionality. Data is associated with keys and each peer is responsible for a subset of the keys. In hierarchical DHTs, peers are organized into groups, and each group has its autonomous intra-group overlay network and lookup service. Groups are organized in a top-level overlay network. To find a peer that is responsible for a key, the top-level overlay first determines the group responsible for the key; the responsible group then uses its intra-group overlay to determine the specific peer that is responsible for the key. We provide a general framework for hierarchical DHTs with scalable overlay management. We specifically study a two-tier hierarchy that uses Chord for the top level. Our analysis shows that by using the most reliable peers in the top level, the hierarchical design significantly reduces the expected number of hops. We also present a method to construct hierarchical DHTs that map well to the Internet topology and achieve short intra-group communication delay. The results demonstrate the feasibility of locality-based peer groups, which allow P2P systems to take full advantage of the hierarchical design.
---
paper_title: MILSA: A Mobility and Multihoming Supporting Identifier Locator Split Architecture for Naming in the Next Generation Internet

paper_content:

Naming and addressing are important issues for next generation Internet (NGI). In this paper, we discuss a new mobility and multihoming supporting identifier locator split architecture (MILSA). There are three main contributions of our solution. First, we separate trust relationships (realms) from connectivity (zones). A hierarchical identifier system for the realms and a Realm Zone Bridging Server (RZBS) infrastructure that performs the bridging function is introduced. Second, we separate the signaling and data plane functions to improve the performance and support mobility. Third, to provide transparency to the upper layer applications, identifier locator split happens in network layer. A Hierarchical URI-like Identifier (HUI) is used by the upper layers and is mapped to a locators set by HUI Mapping Sublayer (HMS) through interaction with RZBS infrastructure. Further scenarios description and analysis show the benefits of this scheme for routing scalability, mobility and multihoming.
---
paper_title: A reliable and scalable striping protocol

paper_content:

Link striping algorithms are often used to overcome transmission bottlenecks in computer networks. Traditional striping algorithms suffer from two major disadvantages. They provide inadequate load sharing in the presence of variable length packets, and may result in non- FIFO delivery of data. We describe a new family of link striping algorithms that solves both problems. Our scheme applies to any layer that can provide multiple FIFO channels.We deal with variable sized packets by showing how fair queuing algorithms can be transformed into load sharing algorithms. Our transformation results in practical load sharing protocols, and shows a theoretical connection between two seemingly different problems. The same transformation can be applied to obtain load sharing protocols for links with different capacities. We deal with the FIFO requirement for two separate cases. If a sequence number can be added to each packet, we show how to speed up packet processing by letting the receiver simulate the sender algorithm. If no header can be added, we show how to provide quasi- FIFO delivery. Quasi- FIFO is FIFO except during occasional periods of loss of synchronization. We argue that quasi- FIFO is adequate for most applications. We also describe a simple technique for speedy restoration of synchronization in the event of loss.We develop an architectural framework for transparently embedding our protocol at the network level by striping IP packets across multiple physical interfaces. The resulting strIPe protocol has been implemented within the NetBSD kernel. Our measurements and simulations show that the protocol offers scalable throughput even when striping is done over dissimilar links, and that the protocol synchronizes quickly after packet loss. Measurements show performance improvements over conventional round robin striping schemes and striping schemes that do not resequence packets.
---
paper_title: Bandwidth aggregation for real-time applications in heterogeneous wireless networks

paper_content:

A variety of wireless interfaces are available for today's mobile user to access Internet content. When coverage areas of these different technologies overlap, a terminal equipped with multiple interfaces can use them simultaneously to improve the performance of its applications. In this paper, we motivate the advantages that can be had through simultaneous use of multiple interfaces and present a network layer architecture that enables diverse multiaccess services. In particular, we explore in depth one such service provided by the architecture: Bandwidth Aggregation (BAG) for real-time applications. An important aspect of the architecture when providing BAG services for real-time applications is the scheduling algorithm that partitions the traffic onto different interfaces such that the QoS requirements of the application are met. We propose one such algorithm Earliest Delivery Path First (EDPF), that ensures packets meet their playback deadlines by scheduling packets based on the estimated delivery time of the packets. We show through analysis that EDPF performs close to an idealized Aggregated Single Link (ASL) discipline, where the multiple interfaces are replaced by a single interface with same aggregated bandwidth. A prototype implementation and extensive simulations carried using video and delay traces show the performance improvement BAG with EDPF scheduling offers over using just the Highest Bandwidth Interface (HBI) and other scheduling approaches based on weighted round robin.
---
paper_title: Flow Bindings in Mobile IPv6 and Nemo Basic Support

paper_content:

This document introduces extensions to Mobile IPv6 [1] and Nemo Basic ::: Support [2] that allow nodes to bind one or more flows to a care-of ::: address. These extensions allow multihomed nodes to take full ::: advantage of the different properties associated with each of their ::: interfaces.
---
paper_title: Multiple Care-of Addresses Registration

paper_content:

According to the current Mobile IPv6 specification, a mobile node may ::: have several care-of addresses, but only one, termed the primary care- ::: of address, can be registered with its home agent and the ::: correspondent nodes. However, for matters of cost, bandwidth, delay, ::: etc, it is useful for the mobile node to get Internet access through ::: multiple access media simultaneously, in which case multiple active ::: IPv6 care-of addresses would be assigned to the mobile node. We thus ::: propose Mobile IPv6 extensions designed to register multiple care-of ::: addresses bound to a single Home Address instead of the sole primary ::: care-of address. For doing so, a new identification number must be ::: carried in each binding for the receiver to distinguish between the ::: bindings corresponding to the same Home Address. Those extensions are ::: targeted to NEMO (Network Mobility) Basic Support as well as to Mobile ::: IPv6.
---
paper_title: A Transport Layer Approach for Improving End-to-End Performance and Robustness Using Redundant Paths

paper_content:

Recent work on Internet measurement and overlay networks has shown that redundant paths are common between pairs of hosts and that one can often achieve better end-to-end performance by adaptively choosing an alternate path [8, 28]. In this paper, we propose an end-to-end transport layer protocol, mTCP, which can aggregate the available bandwidth of those redundant paths in parallel. By striping one flow's packets across multiple paths, mTCP can not only obtain higher end-to-end throughput but also become more robust under path failures. When some paths fail, mTCP can continue sending packets on other living paths and the recovery process normally takes only a few seconds. Because mTCP could obtain an unfair share of bandwidth under shared congestion, we integrate a shared congestion detection mechanism into our system. It allows us to dynamically detect and suppress paths with shared congestion so as to alleviate the aggressiveness problem. mTCP can also passively monitor the performance of several paths in parallel and discover better paths than the path provided by the underlying routing infrastructure. We also propose a heuristic to find disjoint paths between pairs of nodes using traceroute. We have implemented our system on top of overlay networks and evaluated it in both Planet-Lab and Emulab.
---
paper_title: Always best connected

paper_content:

Over the last few years, we have experienced a variety of access technologies being deployed. While 2G cellular systems evolve into 3G systems such as UMTS or cdma2000, providing worldwide coverage, wireless LAN solutions have been extensively deployed to provide hotspot high-bandwidth Internet access in airports, hotels, and conference centers. At the same time, fixed access such as DSL and cable modem tied to wireless LANs appear in home and office environments. The always best connected (ABC) concept allows a person connectivity to applications using the devices and access technologies that best suit his or her needs, thereby combining the features of access technologies such as DSL, Bluetooth, and WLAN with cellular systems to provide an enhanced user experience for 2.5G, 3G, and beyond. An always best connected scenario, where a person is allowed to choose the best available access networks and devices at any point in time, generates great complexity and a number of requirements, not only for the technical solutions, but also in terms of business relationships between operators and service providers, and in subscription handling. This article describes the concept of being always best connected, discusses the user experience and business relationships in an ABC environment, and outlines the different aspects of an ABC solution that will broaden the technology and business base of 3G.
---
paper_title: SLM, a framework for session layer mobility management

paper_content:

This paper describes a novel framework for managing connections to mobile hosts in the Internet. The framework, SLM, integrates the notions of quality of service management and mobility management and forms a base for overall session management. We compare SLM with the currently most widely adopted mobility management framework, Mobile IP, and show how some of Mobile IP's deficiencies are overcome. The paper further presents some initial experimental results and future research.
---
paper_title: A transport layer approach for achieving aggregate bandwidths on multi-homed mobile hosts

paper_content:

Due to the availability of a wide variety of wireless access technologies, a mobile host can potentially have subscriptions and access to more than one wireless network at a given time. In this paper, we consider such a multi-homed mobile host, and address the problem of achieving bandwidth aggregation by striping data across the multiple interfaces of the mobile host. We show that both link layer striping approaches and application layer techniques that stripe data across multiple TCP sockets do not achieve the optimal bandwidth aggregation due to a variety of factors specific to wireless networks. We propose an end-to-end transport layer approach called pTCP that effectively performs bandwidth aggregation on multi homed mobile hosts. We show through simulations that pTCP achieves the desired goals under a variety of network conditions.
---
paper_title: Mobility through naming: impact on dns

paper_content:

An Identifier/Locator addressing scheme can enable a new approach to mobile hosts and mobile networks. Identifier and Locator information is stored in Domain Name System (DNS) Resource Records. In our on-going work using the Identifier-Locator Network Protocol (ILNP), the DNS would be updated with new Locator values as hosts and/or networks move; new sessions would obtain the correct Locator(s) for a mobile host and/or mobile network from the DNS, in much the same way as currently happens for IP address resolution. However, this use of the DNS is not currently required for IP mobility. We examine the potential impact on DNS from using a naming approach to mobility.
---
paper_title: SHIP mobility management hybrid SIP-HIP scheme

paper_content:

In future wireless communication networks such as 4G, different wireless technologies and architectures will coexist. In these heterogeneous network environments, mobility management is a critical issue. Session initiation protocol (SIP) is a widely discussed protocol, which is used for signaling and mobility management, especially in Voice over IP (VoIP) environment. However, its mobility management is restricted to SIP sessions only. To provide a full mobility management for services in future wireless IP networks, SIP can be combined with other protocols. In this paper, a new mobility management scheme based on host identity protocol (HIP) and SIP is proposed. The hybrid SIP and HIP (SHIP) scheme is for all services. SHIP has better performance in handoff signaling than SIP. Its signaling overhead is smaller and the signaling delay is much shorter. SHIP has been shown to outperform hybrid SIP and mobile IP, a widely discussed mobility management scheme, in a number of areas.
---

Title: Future Wireless Networks: Key Issues and a Survey (ID/Locator Split Perspective)

Section 1: Introduction
Description 1: Introduce the concept of future wireless networks (FWNs) and highlight the significant changes and requirements in terms of mobility, security, and scalability compared to current networks.

Section 2: Key Issues
Description 2: Discuss the four major challenges for FWNs: mobility, multihoming, routing scalability, and deployability. Briefly mention the importance of these issues and provide an overview of each.

Section 3: Classification and a Survey
Description 3: Survey recent techniques and proposals that use the ID/locator split concept to address the key issues in FWNs. Categorize the mobility, multihoming, routing scalability, and deployability solutions based on the network layer approach, transport layer approach, sub-layer approach, and application layer approach.

Section 4: Mobility
Description 4: Examine different approaches to support mobility in FWNs, including network layer approaches (e.g., Mobile IP and its extensions), transport layer approaches (e.g., modifications of TCP), sub-layer approaches, and application layer approaches (e.g., SIP).

Section 5: Routing Scalability
Description 5: Discuss the problem of routing scalability in FWNs and explain how the ID/locator split concept helps to mitigate this issue. Present various solutions such as provider aggregatable addresses and address rewriting techniques.

Section 6: Multihoming
Description 6: Explore the multihoming support in FWNs through network-based, host-based, and hybrid approaches. Discuss different techniques that enable multihoming and their implications.

Section 7: Multihoming Multi-interface Selection
Description 7: Address the issue of selecting the best networking interface in a multihoming environment. Discuss mechanisms for policy-based QoS and user requirements to achieve optimal multi-interface selection.

Section 8: Discussion
Description 8: Summarize and compare the different mobility and multihoming techniques discussed. Analyze their pros and cons, especially concerning user location privacy, scalability, secure identity, and deployability.

Section 9: Conclusions
Description 9: Conclude the survey by summarizing the key findings. Highlight the importance of the ID/locator split concept in addressing the issues of mobility, multihoming, routing scalability, and deployability in future wireless networks.