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

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Thu, 25 October 2012 10:02 UTC

Return-Path: <nishida@sfc.wide.ad.jp>
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 D569621F89A9 for <multipathtcp@ietfa.amsl.com>; Thu, 25 Oct 2012 03:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.874
X-Spam-Level:
X-Spam-Status: No, score=-99.874 tagged_above=-999 required=5 tests=[AWL=-1.401, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
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 rQb4v1ubzODf for <multipathtcp@ietfa.amsl.com>; Thu, 25 Oct 2012 03:02:27 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) by ietfa.amsl.com (Postfix) with ESMTP id 3341321F899E for <multipathtcp@ietf.org>; Thu, 25 Oct 2012 03:02:27 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 9CC092780C3 for <multipathtcp@ietf.org>; Thu, 25 Oct 2012 19:02:19 +0900 (JST)
Received: by mail-la0-f44.google.com with SMTP id b11so1379390lam.31 for <multipathtcp@ietf.org>; Thu, 25 Oct 2012 03:02:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.100.164 with SMTP id ez4mr6998694lbb.106.1351159337103; Thu, 25 Oct 2012 03:02:17 -0700 (PDT)
Received: by 10.112.103.193 with HTTP; Thu, 25 Oct 2012 03:02:17 -0700 (PDT)
In-Reply-To: <8555143.2iqzCu1CV5@cpaasch-mac>
References: <CAO249yeRJru7ySTDSNE-7uz5fqiCKrUowD+ipcydnavnxYdZGg@mail.gmail.com> <8555143.2iqzCu1CV5@cpaasch-mac>
Date: Thu, 25 Oct 2012 03:02:17 -0700
Message-ID: <CAO249ydV60Vtasz--jq_Mz=RVybuqHX4at36-zaJESZ8_WVDqA@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Christoph Paasch <christoph.paasch@uclouvain.be>
Content-Type: multipart/alternative; boundary="f46d04016a5b52b03804ccdf4c7e"
Cc: multipathtcp@ietf.org
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
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 10:02:28 -0000

Hello Christoph,

Thank you so much for your clarification.

On Thu, Oct 25, 2012 at 2:25 AM, Christoph Paasch <
christoph.paasch@uclouvain.be> wrote:

> 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.
>

Sorry. I was not clear enough. Yes, that's what I meant.
I thought if someone overlooks this part, it might be dangerous.

Thanks,
--
Yoshifumi