[multipathtcp] primary/secondary path concept in mptcp?

Yoshifumi Nishida <nsd.ietf@gmail.com> Mon, 24 June 2019 05:50 UTC

Return-Path: <nsd.ietf@gmail.com>
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 87BF7120293 for <multipathtcp@ietfa.amsl.com>; Sun, 23 Jun 2019 22:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2JnlMhPYJymJ for <multipathtcp@ietfa.amsl.com>; Sun, 23 Jun 2019 22:50:04 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A92BE12003F for <multipathtcp@ietf.org>; Sun, 23 Jun 2019 22:50:03 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id f9so12375831wre.12 for <multipathtcp@ietf.org>; Sun, 23 Jun 2019 22:50:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Th3TFLC4Y39gGrqEA9YuFEppsYviAullgHMNyRH8IBc=; b=Ul24s1QCLcOQ704/8Dv5wqB5deymj9cm9SFAlz9WxJ+6TJDqPbOviNd0bDwP0S2DCi F+tyzEyllnirWG+PaBaONU2/Grs2cRdbY8xwFwtoF4u0eHuec900wgs5SitQcTUOSpGg Ars9j06CAtLzHWFs94/7l+U7ZDSOp8q9smLeJ0t/8eXEVAT5TqgUovNgEBEaEjF4Am4+ y2KpxTRS7zCruDZVG9Z5d2oB3xo/73byt2lpando9wRnUBhDr1rdTh2MgglMOeACWyp0 aP4OofF6m0I2gBfXQP49u1831GNvJsKQVnULHPoWo8qJkaog2tE6Z84LsFqsdp6s5bGm utSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Th3TFLC4Y39gGrqEA9YuFEppsYviAullgHMNyRH8IBc=; b=GTRpVtDDaPxU0xTwS5NPSFVaD40Rh3RdejPjgainYhnuZbS+xIpgldl29SHMB31r4N aNSu6LkM+AR60ncO3EqQYJu0e5uzMQvJjczyL4TJDPYZclbWEAkKg4aIpoLjxJ43Bvke eod/UJ9Fn9CsArNuc2zVGFCiF2e7YprQ6UZDVdwXgQWVZQsNAEw+0yRL5uVXYhXxIbaJ WaGw640iY2s7eYEyuD3XqmwkQzzP0sRvHEpdp4F0fthRKCHuT+cInv1o43ymM8+YLo1a hogCxjxbemUOZEi+9hWZkdOi1JeowgPCQujCIT+Wd5JIxZYoQW5xr/pGbWr5hFgIufUL gAXw==
X-Gm-Message-State: APjAAAV9UCeEqL6QrxQkkEOx18Uh6nRvwcy6CEVz5xbUQogn0vLEfSl+ /1dZ/c0mtqwClzDfwkYjsfjY9Wbzp35sihbp7TFwow==
X-Google-Smtp-Source: APXvYqybdoTWbO3E5vYu2ZPOmRNQxuXs3ZfpySD5knpJ+4i9nu1UH8Ar6HRZEcaqOQZdN9OP8i8+Fw8vRsf5dactIgs=
X-Received: by 2002:adf:a38b:: with SMTP id l11mr27601039wrb.325.1561355401966; Sun, 23 Jun 2019 22:50:01 -0700 (PDT)
MIME-Version: 1.0
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Sun, 23 Jun 2019 22:49:50 -0700
Message-ID: <CAAK044R0qpgEmL2m+Gpg-BLO-nrivrrzKU0yb5JAuKUhPPo0zQ@mail.gmail.com>
To: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001a3799058c0b620f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/uMJCZROzpRBz4a5s-_TTp8wygxA>
Subject: [multipathtcp] primary/secondary path concept in mptcp?
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Jun 2019 05:50:06 -0000

Hi,
While I'm reading the recent threads in mptcp WG ML, I start wondering
there might be a need for primary/secondary path concept in mptcp path
managements, which is similar to the one in SCTP.

The mptcp spec already allows us to set backup flag to the path. But, in
this case, failover will happen only when the regular path becomes
unavailable. I think this will mean it can take longer time unless the
regular path can correctly sends RST.

The primary/secondary path idea is more light-weight approach than the
backup mode. When packets has been lost on the primary, it tries to utilize
the secondary path while checking the status of the primary (e.g. by
sending keep alives). Once the primary has been recovered, it starts using
the primary again.

A potential use case for this approach would be wifi and LTE combination.
While wifi link has intermittent connection failure (e.g due to handover or
minor connection problems), it uses LTE and after the wifi link has been
recovered, it starts using it again.

Some folks may say a well sophisticated path scheduler can handle this kind
of situations, but I'm not very sure yet because it may need complex
controls to be effective.

Thanks,
--
Yoshi