Applicability of Reliable Server Pooling for SCTP-Based Endpoint Mobility
draft-dreibholz-rserpool-applic-mobility-28
Network Working Group T. Dreibholz
Internet-Draft SimulaMet
Intended status: Informational J. Pulinthanath
Expires: March 13, 2021 University of Duisburg-Essen
September 09, 2020
Applicability of Reliable Server Pooling for SCTP-Based Endpoint
Mobility
draft-dreibholz-rserpool-applic-mobility-28
Abstract
This document describes a novel mobility concept based on a
combination of SCTP with Dynamic Address Reconfiguration extension
and Reliable Server Pooling (RSerPool).
Status of This Memo
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 March 13, 2021.
Copyright Notice
Copyright (c) 2020 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 Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Dreibholz & Pulinthanath Expires March 13, 2021 [Page 1]
Internet-Draft SCTP Mobility with RSerPool September 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Existing Mobility Solutions . . . . . . . . . . . . . . . . . 2
2.1. Mobile IP and Mobile IPv6 . . . . . . . . . . . . . . . . 2
2.2. SCTP with Dynamic Address Reconfiguration . . . . . . . . 3
3. Solutions for Simultaneous Handovers . . . . . . . . . . . . 3
3.1. SCTP with Add-IP and Mobile-IP . . . . . . . . . . . . . 3
3.2. SCTP with Add-IP and RSerPool . . . . . . . . . . . . . . 4
4. Reference Implementation . . . . . . . . . . . . . . . . . . 4
5. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
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).
2. Existing Mobility Solutions
2.1. Mobile IP and Mobile IPv6
In the concept of Mobile IP [RFC5944] 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.
Dreibholz & Pulinthanath Expires March 13, 2021 [Page 2]
Show full document text