| Internet-Draft | SCTP Mobility with RSerPool | September 2022 |
| Dreibholz & Pulinthanath | Expires 21 March 2023 | [Page] |
This document describes a novel mobility concept based on a combination of SCTP with Dynamic Address Reconfiguration extension and Reliable Server Pooling (RSerPool).¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 21 March 2023.¶
Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
An increasing amount of Internet devices is getting mobile. Therefore, there is a growing demand for software solutions allowing for a seamless handover of communication sessions between multiple networks, e.g. to allow for a laptop or PDA to use a fast Ethernet connection when available, hand over to a WLAN when moving and hand over again to UMTS when the WLAN becomes unreachable - without interrupting the running communication sessions.¶
Mobility handling is a deficiency of the common IP-based networks. Most of the available solutions are based on the network layer. The disadvantage of such solutions is that fundamental changes in the network infrastructure are needed. Therefore, we propose a new solution based on the upper layers to overcome these disadvantages. In this document, we present our mobility solution based on the SCTP protocol with Dynamic Address Reconfiguration extension and Reliable Server Pooling (RSerPool).¶
In the concept of Mobile IP [4] every node must register to a Home-Agent (HA) in its own home network. Then, the nodes are reachable under their home addresses managed by the HA. When a node leaves its home network, it must also register at a Foreign Agent (FA) in the new network. After that, a tunnel is established between the HA and the FA. Any traffic to the mobile node is then tunnelled by its HA to the FA and forwarded by the FA to the node itself. Clearly, the detour of all traffic via HA and FA is inefficient and results in an increased transmission delay.¶
Mobile IPv6 [5] is an extension of Mobile IP. In Mobile IPv6, the FA is not needed. The packets will be tunnelled from the HA to the Gateway Router in the foreign network, which forwards the packets to the endpoint. The inefficiency due to the detour of traffic as described for Mobile IP remains.¶
Using the SCTP protocol (see [2] together with its Dynamic Address Reconfiguration extension (Add-IP, see [3]), it is possible for a mobile endpoint to inform its peer on address changes. That is, when a moving mobile client gets in the vicinity of an additional radio station, it sends an "ASCONF Add Address Request" to tell its peer that it is now reachable under an additional network-layer address. After that, the peer endpoint can use this additional address for a new SCTP path. When the first radio station becomes unreachable, the node can send an "ASCONF Delete Address Request" to the peer endpoint. After that, the peer removes the corresponding SCTP path to the unusable network-layer address.¶
The following two cases for handovers are possible:¶
Using SCTP with Add-IP and Mobile IP/Mobile IPv6, the ASCONF messages will be sent to the home address of the peer node. That is, even when both nodes are mobile, each endpoint is able to reach its peer endpoint using the corresponding home address. However, this solution still requires the full Mobile IP/Mobile IPv6 infrastructure.¶
Using RSerPool (see [1], [6], [7], [8], [9], [10], [11], at least one node registers as a Pool Element (PE) at an ENRP server under a Pool Handle (PH) known to both endpoints. Upon handover, it is simply necessary for the PE endpoint to re-register, i.e. to update its registration with its new address. The other endpoint can - in the role of a Pool User (PU) - ask an ENRP server for its peer node's new addresses. After the new address is known, it is able to create a new SCTP path and continue the communication.¶
The usage of RSerPool to provide support for mobile endpoints provides the following advantages:¶
A more detailed description of our approach for endpoint mobility, as well as a performance analysis using a prototype implementation, can be found in our paper [16].¶
The RSerPool reference implementation RSPLIB can be found at [18]. It supports the functionalities defined by [6], [7], [8], [9] and [11] as well as the options [12], [14] and [13]. An introduction to this implementation is provided in [15].¶
A large-scale and realistic Internet testbed platform with support for the multi-homing feature of the underlying SCTP protocol is NorNet. A description of NorNet is provided in [17], some further information can be found on the project website [19].¶
Security considerations for RSerPool systems are described by [10].¶
This document introduces no additional considerations for IANA.¶