Fault Management Mechanism in MPTCP Session
draft-kang-tcpm-fault-management-in-mptcp-session-00
TCP Maintenance and Minor Extensions J. Kang, Ed.
Internet-Draft Q. Liang
Intended status: Informational Huawei
Expires: 10 February 2021 9 August 2020
Fault Management Mechanism in MPTCP Session
draft-kang-tcpm-fault-management-in-mptcp-session-00
Abstract
This document presents a mechanism for fault management during a
MPTCP session. It is used to convey subflow failure information from
client to server by other subflow running normally. It includes: 1)
a new Fault Announce Option for describing subflow failure, 2)
implementation and interoperability of this option during a MPTCP
session when one subflow suffers a failure. In fact, the server is
able to determine network problems accurately based on these fault
information reported from multiple clients for their connections.
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 10 February 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Kang & Liang Expires 10 February 2021 [Page 1]
Internet-Draft Fault Management in MPTCP August 2020
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Fault Announce Exchanges . . . . . . . . . . . . . . . . . . 3
3. Fault Announce option . . . . . . . . . . . . . . . . . . . . 4
3.1. Option format . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Additional requirements to be considered . . . . . . . . 5
3.2.1. Scenario of middlebox failure . . . . . . . . . . . . 5
3.2.2. Scenario of distinguishing fault types . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
During data transmission in a MPTCP session, subflows may encounter
some problems, for example, port failure on one endpoint, network
failure, or middlebox working abnormally. Current MPTCP protocol
does not provide exchanges between client and server when a fault
happens on a subflow which will cause transmission failure or delay.
[RFC8684] introduces TCP RST Reason (MP_TCPRST) option to signal
reasons for sending a RST on a subflow which can help an
implementation decide whether to attempt later reconnection. TCP RST
Reason (MP_TCPRST) option only reports the reason for a specific
subflow that has been determined to be closed later. This solution
does not cover the case of abnormal termination of one ongoing
subflow.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Kang & Liang Expires 10 February 2021 [Page 2]
Internet-Draft Fault Management in MPTCP August 2020
2. Fault Announce Exchanges
This document proposes a fault announce mechanism with a new option
that can be used to deliver failure information of abnormal subflow
between client and server via another subflow in the MPTCP session
that works properly. The flow is illustrated in Figure 1.
Show full document text