Multipath TCP Inactivity Time Option
draft-hoang-mptcp-inactivity-time-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
MPTCP Working Group                                              V. Tran
Internet-Draft                                            O. Bonaventure
Intended status: Informational          Universite catholique de Louvain
Expires: January 9, 2020                                   July 08, 2019

                  Multipath TCP Inactivity Time Option
                  draft-hoang-mptcp-inactivity-time-00

Abstract

   This document discusses the lifetime of idle MPTCP sessions, and
   defines an MPTCP Option subkind for hosts to announce and request
   this value.

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 January 9, 2020.

Copyright Notice

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

Tran & Bonaventure       Expires January 9, 2020                [Page 1]
Internet-Draft            mptcp-inactivity-time                July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Lifetime of Multipath TCP connections . . . . . . . . . . . .   3
   4.  The Multipath TCP Inactivity Timer Option . . . . . . . . . .   4
     4.1.  Option Format . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  ITO Option and Local Policies . . . . . . . . . . . . . .   5
   5.  Implementation and Interoperability . . . . . . . . . . . . .   5
     5.1.  Interaction with TCP Keepalives . . . . . . . . . . . . .   5
     5.2.  Interaction with User Timeout . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Multipath TCP [RFC6824] [I-D.ietf-mptcp-rfc6824bis] is used in
   various use cases [RFC8040].  In several of these deployments, a
   Multipath TCP connection is composed of a number of subflows that
   varies during the lifetime of the connection.  TCP implementations
   create state when a connection starts and maintain this state until
   the abrupt or graceful termination of the connection according to the
   TCP state machine [RFC0793].  Multipath TCP implementations need to
   maintain two types of states:

   o  the per-Multipath TCP connection state that includes the
      connection keys, data sequence numbers, ...

   o  the per-TCP subflows connection states

   The per-TCP state of each subflow is managed according to [RFC0793].
   The Multipath TCP connection state also needs to be managed.  We
   consider a subflow to be active if its TCP state machine exists and
   is in the Established state.  We call inactive a Multipath TCP
   connection that currently has no active subflow.  It is important to
   note that it is possible for one host to consider a given Multipath
   TCP connection to be inactive while the other endpoint considers that
   the connection is still active.  This can happen for example when
   some packets are lost or when one of the hosts has received a
   spurious RST on the only active subflow.  [RFC6824] and
   [I-D.ietf-mptcp-rfc6824bis] specify how this state can be removed
   upon transmission or reception of a FASTCLOSE and after having
   exchanged DATA_FINs.  However, [RFC6824] and

Tran & Bonaventure       Expires January 9, 2020                [Page 2]
Internet-Draft            mptcp-inactivity-time                July 2019
Show full document text