Motivations and Design Choices of the Flexible Session Protocol
draft-gao-fsp-motivations-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-17
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                                                    J. Gao
Intended Status: Informational                                          
Expires: April 20, 2019                                 October 17, 2018

    Motivations and Design Choices of the Flexible Session Protocol
                      draft-gao-fsp-motivations-00

Abstract

   This document introduces the motivation to design the Flexible
   Session Protocol which supports mobility and multihoming at the
   transport layer. FSP is to avoid, if not to extirpate, the routing
   scalability problem in the IPv6 internetwork.

   The document serves to explain choices of design goals of FSP as
   well.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2018 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
 

Gao                      Expires April 20, 2019                 [Page 1]
INTERNET DRAFT             Motivations of FSP           October 17, 2018

   (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  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.2. Mobility and Multihoming Support in the IPv6 Internet . . .  4
   2. Survey of Infrastructure-Dependent Mobility Support . . . . . .  4
     2.1. Separation of Identifier and Locator  . . . . . . . . . . .  5
       2.1.1. Host Identity Protocol  . . . . . . . . . . . . . . . .  5
       2.1.2. Identifier-Locator Network Protocol . . . . . . . . . .  6
       2.2.3. The Locator/ID Separation Protocol  . . . . . . . . . .  7
     2.2. Tunneling . . . . . . . . . . . . . . . . . . . . . . . . .  8
       2.2.1. Mobile IPv6 . . . . . . . . . . . . . . . . . . . . . .  8
       2.2.2. Proxy Mobile IPv6 . . . . . . . . . . . . . . . . . . . 10
       2.2.3. Hierarchical Mobile IPv6  . . . . . . . . . . . . . . . 10
       2.2.4. Network Mobility (NEMO) Basic Support Protocol  . . . . 11
     2.3. MinimalT  . . . . . . . . . . . . . . . . . . . . . . . . . 12
     2.4. DMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
   3. Survey of Infrastructure-Independent Mobility Support . . . . . 15
     3.1. IKEv2 Mobility and Multihoming Protocol . . . . . . . . . . 15
     3.2. Mobile SCTP . . . . . . . . . . . . . . . . . . . . . . . . 17
     3.3. Multipath TCP . . . . . . . . . . . . . . . . . . . . . . . 18
     3.4. REST Architecture Style . . . . . . . . . . . . . . . . . . 18
   4. A Solution at the Origin of the Problem . . . . . . . . . . . . 20
     4.1. Separation of Identity and Locator at Transport Layer . . . 20
     4.2. Adding Programmer-Friendly Session Semantics  . . . . . . . 20
       4.2.1. Intuitiveness . . . . . . . . . . . . . . . . . . . . . 20
       4.2.2. Really Parallel Streams . . . . . . . . . . . . . . . . 21
       4.2.3. Mixed Traffic Class . . . . . . . . . . . . . . . . . . 21
       4.2.4. Session Adjournment and Resumption  . . . . . . . . . . 21
     4.3. Adding Programmer-friendly Security Service . . . . . . . . 21
       4.3.1. Ubiquitous Encryption and Authentication of Data  . . . 21
       4.3.2. Key Establishment versus Application of Keys  . . . . . 22
   5. Choices of Design Goals . . . . . . . . . . . . . . . . . . . . 22
     5.1. Featured Scenarios  . . . . . . . . . . . . . . . . . . . . 22
       5.1.1. Goal: Support for Mobile Computing  . . . . . . . . . . 22
       5.1.2. Goal: Adaptable to Specific-Purpose Networks  . . . . . 23
       5.1.3. Non-Goal: General Multicast Transport . . . . . . . . . 23
Show full document text