Re: [multipathtcp] comments on draft-paasch-mptcp-lowoverhead and draft-paasch-mptcp-ssl

Christoph Paasch <christoph.paasch@uclouvain.be> Thu, 25 October 2012 09:26 UTC

Return-Path: <christoph.paasch@uclouvain.be>
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 E4F4B21F89BB for <multipathtcp@ietfa.amsl.com>; Thu, 25 Oct 2012 02:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aHdV4DUwR2SD for <multipathtcp@ietfa.amsl.com>; Thu, 25 Oct 2012 02:26:05 -0700 (PDT)
Received: from smtp5.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by ietfa.amsl.com (Postfix) with ESMTP id 3018C21F87BD for <multipathtcp@ietf.org>; Thu, 25 Oct 2012 02:26:05 -0700 (PDT)
Received: from cpaasch-mac.localnet (cpaasch-mac.dhcp.info.ucl.ac.be [130.104.228.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cpaasch@smtp5.sgsi.ucl.ac.be) by smtp5.sgsi.ucl.ac.be (Postfix) with ESMTPSA id DF2C611EF86; Thu, 25 Oct 2012 11:25:58 +0200 (CEST)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp5.sgsi.ucl.ac.be DF2C611EF86
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1351157158; bh=phVeemNkLYX8KJT/HcuxPGMCuorC+4Vl4CGUURdaA08=; h=From:To:Reply-To:Cc:Subject:Date:Message-ID:In-Reply-To: References:MIME-Version:Content-Transfer-Encoding:Content-Type; b=trQwHSdjbcByZubeVX+WSnD6Cc2yKQfR1tUScwF4ga7a3R/fqtECTvzTS3YsU8dTj AHi28/z1OnQwBJUyQGY0XSMCfubNkkyFfG4qCIXb6VWPFG5l0Zuz/nzlz1QeZ17gIi S18C81AViFJSV7C3zkEDXXjRA2OuDZw/an0riN4k=
From: Christoph Paasch <christoph.paasch@uclouvain.be>
To: multipathtcp@ietf.org
Date: Thu, 25 Oct 2012 11:25:58 +0200
Message-ID: <8555143.2iqzCu1CV5@cpaasch-mac>
Organization: Université Catholique de Louvain
User-Agent: KMail/4.9.2 (Linux/3.2.0-33-mptcp; KDE/4.9.2; x86_64; ; )
In-Reply-To: <CAO249yeRJru7ySTDSNE-7uz5fqiCKrUowD+ipcydnavnxYdZGg@mail.gmail.com>
References: <CAO249yeRJru7ySTDSNE-7uz5fqiCKrUowD+ipcydnavnxYdZGg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-Virus-Scanned: clamav-milter 0.97.3-exp at smtp-5.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-MailScanner-ID: DF2C611EF86.A1C0A
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: christoph.paasch@uclouvain.be
X-SGSI-Spam-Status: No
Subject: Re: [multipathtcp] comments on draft-paasch-mptcp-lowoverhead and draft-paasch-mptcp-ssl
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Christoph Paasch <christoph.paasch@uclouvain.be>
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: <http://www.ietf.org/mail-archive/web/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: Thu, 25 Oct 2012 09:26:06 -0000

Hi Yoshifumi,

thanks for your comments. Please find my replies below.


On Thursday 25 October 2012 01:51:58 Yoshifumi Nishida wrote:
> 1: I'm wondering if experimental status might be better for them. Is there
> any thoughts on this?

You are probably right. I can change this for the next version.

> 2: How is the relationships between these drafts? Is it totally
> independent?

Yes, they are independent from each other. MPTCP v0 or MPTCP v1 (low overhead) 
can use a key provided by the application.

> 3: In my feeling, it could be dangerous If token is used for high-order
> 32bit. (draft-paasch-mptcp-lowoverhead)
>     We might want to emphasize this point.

What part in the draft are you referring to?
It is the random number that is used for the 32 high-order bits of the IDSN.

Or do you mean that we just should explain why the random number is used, and 
not the token for the high-order bits.

> 4: In section 5 of draft-paasch-mptcp-lowoverhead.
>     "if an attacker manages to join an existing connection...".
>     Does this mean the attacker steals the token? I just would like to
> confirm..

The attacker might know (through sniffing) the token or guess it and thus can 
add a subflow to the connection.


Cheers,
Christoph


-- 
IP Networking Lab --- http://inl.info.ucl.ac.be
MultiPath TCP in the Linux Kernel --- http://mptcp.info.ucl.ac.be
Université Catholique de Louvain
--