Intended status: Experimental A.Eromenko September 2016
draft-eromenko-ipff-mops-02

Document Type Active Internet-Draft (individual)
Last updated 2016-09-29
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT
"Internet Protocol Five Fields - Mobile TCP", 
Alexey Eromenko, 2016-09-29,
<draft-eromenko-ipff-mops-02.txt>
expiration date: 2017-03-29

Intended status: Experimental
                                                              A.Eromenko
                                                          September 2016

                          Mobile Protocol Stack
                   -----------------------------------
                   for Internet Protocol "Five Fields"
                          Specification draft

Abstract

   This document describes a mechanism, that can be used to live-migrate
   opened TCP/UDP/other transport sessions between a mobile server and 
   a mobile client. This can work even after a mobile node moved to 
   a different subnet or disconnected, as long as a session did 
   not timeout.
   It also describes limitations and includes NAT traversal scenarios 
   and guidelines for "middlebox" vendors.

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 http://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."

Copyright Notice

   Copyright (c) 2015 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
   (http://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.

Table of Contents

   1. Introduction..................................................
   2. Comparison of Mobile Protocol Stack to Mobile IP..............
   2.1 Comparison of Mobile TCP to Multipath-TCP....................
   3. Socket creation...............................................
   3.1.  Initiating a Mobile TCP Session............................
   3.2.  Notification on received Source IP address and port........
   4. New ICMP Commands.............................................
   4.1 ICMP Migrate.................................................
   4.2 ICMP Anycast Server acknowledgement..........................
   4.3 ICMP NAT acknowledgement.....................................
   5. Incoming sessions: Dynamic DNS................................
   5.1. Incoming sessions: Destination NATs and Load Balancers......
   6. Limitations...................................................
   7. Requirements from middleboxes.................................
   8. Requirements from operating systems...........................
   9. Security considerations.......................................
   Appendix A: Simple Mobile TCP scenario...........................
   Appendix B: Mobile TCP Double NAT traversal scenario.............
   Author Contacts..................................................

1. Introduction

    "basically TCP/UDP/other session migration... of mobile nodes 
    between subnets, without losing connectivity"

    Mobile Protocol Stack (MOPS) is a solution to the Mobile IP problem.
    Mobile IP problem derived from IP itself.
    Traditional IP has chained the "location" and the "identity"
    of a device by the routing location and traditional socket 5-tuple:
    (s.port, d.port, s.address, d.address, protocol)

    Historically, it was never possible in the original TCP/IP
    design to live-migrate a session or socket.
    An old socket had to be closed, and a new one had to be opened,
    and a new session had to be established.

    This is not a problem for desktop computers, as they always 
    reside in the same particular LAN, and the same subnet.
    But it becomes a problem, if you want to move "mobile nodes" from
    one subnet to the next, without losing connectivity.
    Mobile node can be either a client or a mobile server live-
    migrating from one subnet to the next.

    This whole idea comes from "Live Migration" in the virtualization
    field, where you can migrate a living virtual machine, and it 
Show full document text