Re: [multipathtcp] 6824bis -11 review

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Mon, 06 August 2018 22:25 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 33352124C04 for <multipathtcp@ietfa.amsl.com>; Mon, 6 Aug 2018 15:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 ofxpQfkJh9yE for <multipathtcp@ietfa.amsl.com>; Mon, 6 Aug 2018 15:25:35 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:146]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E60A12DD85 for <multipathtcp@ietf.org>; Mon, 6 Aug 2018 15:25:33 -0700 (PDT)
Received: from mail-it0-f43.google.com (mail-it0-f43.google.com [209.85.214.43]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 2BEB52782DE for <multipathtcp@ietf.org>; Tue, 7 Aug 2018 07:25:31 +0900 (JST)
Received: by mail-it0-f43.google.com with SMTP id v71-v6so20419582itb.3 for <multipathtcp@ietf.org>; Mon, 06 Aug 2018 15:25:31 -0700 (PDT)
X-Gm-Message-State: AOUpUlFpuEMWZ+leW2DM3GBQadDfXWmQWgG4kchib0HGKUxgZGf2HaT1 lLuBOPn97wsxiHuGhT8ypcd9GWG3OiTlOYY2dWY=
X-Google-Smtp-Source: AAOMgpfn7P1ygiVFh6lRVW2WFoIew49rfjbq+GLjFJaJKKZvcGUrMB1e+JMV9AHT6cTv8sszE9tvLJ5ccT4ns0tntco=
X-Received: by 2002:a02:1103:: with SMTP id 3-v6mr13863549jaf.144.1533594329963; Mon, 06 Aug 2018 15:25:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:7599:0:0:0:0:0 with HTTP; Mon, 6 Aug 2018 15:25:29 -0700 (PDT)
In-Reply-To: <2FB78E5E-961F-4077-815F-158142B8E7E2@gmail.com>
References: <982B626E107E334DBE601D979F31785C5DC5A15C@BLREML503-MBX.china.huawei.com> <92A53501-4728-4E02-816A-92CEE703AA49@gmail.com> <20754FD9-627F-4AAC-A1B5-6EF2BD09B2AD@gmail.com> <982B626E107E334DBE601D979F31785C5DC5D84B@BLREML503-MBS.china.huawei.com> <AEC8384E-87BB-48F4-9C42-58D2A6FCF251@gmail.com> <982B626E107E334DBE601D979F31785C5DC6884D@BLREML503-MBS.china.huawei.com> <2FB78E5E-961F-4077-815F-158142B8E7E2@gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Mon, 06 Aug 2018 15:25:29 -0700
X-Gmail-Original-Message-ID: <CAO249yeY3o5RuuH08GjhiLJod9MjeV_xxmScVT5g5rk3p40qGA@mail.gmail.com>
Message-ID: <CAO249yeY3o5RuuH08GjhiLJod9MjeV_xxmScVT5g5rk3p40qGA@mail.gmail.com>
To: Alan Ford <alan.ford@gmail.com>
Cc: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>, Christoph Paasch <cpaasch@apple.com>, multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004465ac0572cbc121"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/dwbpsw8VHE-QtscJoFXZL4YMTPc>
Subject: Re: [multipathtcp] 6824bis -11 review
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.27
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, 06 Aug 2018 22:25:37 -0000

On Tue, Jul 31, 2018 at 5:07 AM, Alan Ford <alan.ford@gmail.com> wrote:

> Hi Rahul, all,
>
>
> On 31 Jul 2018, at 01:21, Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
> wrote:
>
> c) sending a new ADD_ADDR with same ID + address and different port is fine
> [RJ] again this is what the text already says, but I’m not still clear
> about this. Why ID + address has to match? Only ID should be enough.
>
> Consider:
>
> a) ADD_ADDR comes in saying ID=2, addr=10.0.0.1 (private)
> b) MP_JOIN comes in saying ID=2, addr=8.9.10.11 (public)
> c) ADD_ADDR comes in saying ID=2, addr=192.168.0.1
>
> What does this mean? Is (c) an implicit REMOVE+ADD? And thus does this
> mean the subflow created in (b) is now no longer valid?
>
> By keeping the address / ID mapping, if an address is lost, then so is the
> subflow.
>
> [RJ2] Rather than viewing ( c) as an implicit REMOVE+ADD, can we see it as
> an UPDATE? Because ID remains same. Subflow created in (b) remains valid
> (not sure if I’m missing anything here, I see no reason to lose this
> subflow).
> In step ( c), the receiver can override Address field in context to ID=2
> to the new addr (192.168.0.1) ……   8.9.10.11 is kept separately as the
> learnt actual rcvd IP (from MP_JOIN) in the same context ID=2. We have to
> agree that an implementation needs to maintain this IP separately in
> context to ID=2 anyways.
> So if we do an explicit REMOVE+ADD, the end result is the same as this
> UPDATE (but with much less overhead & impl ease).
>
>
> I would be interested in hearing from other implementers here… Is there an
> issue with “updating” using ADD_ADDR?
>
> Given we say that REMOVE_ADDR should not remove a subflow if it’s still
> alive, we have precedent for implying a subflow can exist to an address
> which does not have an Address ID - to - IP address mapping.
>
> So given that, does updating, as Rahul suggests, cause a problem?
>
>
Hmm.. I am wondering why we want to re-use the same address ID while we
have 0-255 values for it?
Do we have some advantage for it? I thought picking up a new ID would be
safer and simpler..
As Alan mentioned, when we try to "update" the address ID, we will have to
keep both addresses until we confirm that old one is not used anymore.
Also, in the case described above, what will happen if (b) was delayed and
arrived after (c)?

Thanks,
--
Yoshi