Trusted Multipath-TCP (MPTCP) extension
draft-hewu-mptcp-trust-00

Document Type Active Internet-Draft (individual)
Last updated 2019-10-30
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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 Engineering Task Force                                    H. Li
Internet-Draft                                                     Q. Wu
Intended status: Informational                                     B. Wu
Expires: May 1, 2020                                            Q. Zhang
                                                                 J. Zhou
                                                                  J. Liu
                                                     Tsinghua University
                                                        October 29, 2019

                Trusted Multipath-TCP (MPTCP) extension
                       draft-hewu-mptcp-trust-00

Abstract

   Multipath TCP (MPTCP) adds the capability of using multiple paths to
   a regular TCP session and is being deployed extensively.  Source
   Address Validation (SAV) technologies are proposed to prevent network
   nodes from spoofing others' IP addresses and thus improve the
   accountability of networks.  This document proposes a trusted MPTCP
   extension based on SAV, which enables MPTCP to work with SAV and thus
   improve the accountability of MPTCP connections.  This extension
   doesn't intend to replace the security solutions to resolving IP
   forged attacks, like Hash-based Message Authentication Code (HMAC),
   but to improve the accountability of them and the whole connection.

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 May 1, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Li, et al.                 Expires May 1, 2020                  [Page 1]
Internet-Draft           Trusted MPTCP extension            October 2019

   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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Operation Overview  . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Trusted Address notification  . . . . . . . . . . . . . .   3
     3.2.  Trusted Connection notification . . . . . . . . . . . . .   4
     3.3.  Control packets processing  . . . . . . . . . . . . . . .   5
   4.  ADD_ADDR extension  . . . . . . . . . . . . . . . . . . . . .   5
   5.  ADDR_TRUST option . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Trusted Path Binding Table (TPBT) . . . . . . . . . . . . . .   6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   10. Informative References  . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Multipath TCP (MPTCP) [I-D.ietf-mptcp-rfc6824bis][RFC6824] adds the
   capability of using multiple paths to a regular TCP session and is
   being deployed extensively.  The main threats of MPTCP are described
   in [RFC6181], [RFC7430] and they are mainly caused by forged control
   packets sent by malicious hosts with forged IP addresses.  Source
   Address Validation (SAV) methods like Source Address Validation
   Architecture (SAVA) [RFC5210] and Source Address Validation
   Improvement (SAVI) [RFC7039] are developed to prevent nodes from
   spoofing others' IP addresses with finer-grained ingress filtering.

   This document proposes a SAV based MPTCP enhancement, which enables
   MPTCP to work with SAV and thus improve the accountability of MPTCP
   connections.

2.  Terminology

   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 [RFC2119].
Show full document text