[multipathtcp] some questions about the closure of MPTCP

王帅 <13211134@bjtu.edu.cn> Mon, 13 March 2017 08:51 UTC

Return-Path: <13211134@bjtu.edu.cn>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4020A129561 for <multipathtcp@ietfa.amsl.com>; Mon, 13 Mar 2017 01:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.391
X-Spam-Level:
X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L4=0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6f7qOVqJSxuW for <multipathtcp@ietfa.amsl.com>; Mon, 13 Mar 2017 01:51:34 -0700 (PDT)
Received: from bjtu.edu.cn (mail.bjtu.edu.cn [218.249.29.198]) by ietfa.amsl.com (Postfix) with ESMTP id 9293B127ABE for <multipathtcp@ietf.org>; Mon, 13 Mar 2017 01:51:33 -0700 (PDT)
Received: by ajax-webmail-Jdweb2 (Coremail) ; Mon, 13 Mar 2017 16:51:48 +0800 (GMT+08:00)
Date: Mon, 13 Mar 2017 16:51:48 +0800 (GMT+08:00)
From: =?GBK?B?zfXLpw==?= <13211134@bjtu.edu.cn>
To: multipathtcp@ietf.org
Message-ID: <34c9721e.38e9c.15ac6ddcba0.Coremail.13211134@bjtu.edu.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_844874_1476006843.1489395108766"
X-Originating-IP: [166.111.130.148]
X-Priority: 3
X-Mailer: Coremail Webmail Server Version 4.0.8 dev build 20150608(70565.7215.7117) Copyright (c) 2002-2017 www.mailtech.cn bjtu
X-SendMailWithSms: false
X-CM-TRANSID: M55wygCXebKkXcZYD0WxAA--.54524W
X-CM-SenderInfo: yrtsiiartuquxmwxhvlgxou0/1tbiAg0SA1RyqAPRfAAAs+
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VW5Jw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/_2R9RoCMzYrtZuQTy3JnTwlq6hM>
X-Mailman-Approved-At: Mon, 13 Mar 2017 03:53:51 -0700
Subject: [multipathtcp] some questions about the closure of MPTCP
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2017 09:04:32 -0000

Hi,

     I am doing a project about MPTCP, but I have some questions about the closure of MPTCP.
     Why does the closure of subflows need FIN?  Is it necessary and compulsory?  When the sender has sent DATA_FIN to the receiver and received DATA_ACK from the receiver, doesn't the data have been transferred from the sender to the receiver completely? So, I wonder whether we can terminate all subflows by sending RST? It will be faster than the FIN, and it can free resources.
     Thank you very much!


Sincerely,
Wang Shuai