
From nobody Thu Jun 11 09:29:13 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 4F6053A087B for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 09:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level: 
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=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 Eo9fPX93r_5T for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 09:29:09 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49C4E3A0A5F for <multipathtcp@ietf.org>; Thu, 11 Jun 2020 09:29:08 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 11DF8548045 for <multipathtcp@ietf.org>; Thu, 11 Jun 2020 18:29:05 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 05989440043; Thu, 11 Jun 2020 18:29:05 +0200 (CEST)
Date: Thu, 11 Jun 2020 18:29:04 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: multipathtcp@ietf.org
Message-ID: <20200611162904.GO16371@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/K-tkVuU3johYiONZHxughc33uEY>
Subject: [multipathtcp] mptcp quick Q: MP-TCP for address redundancy
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: Thu, 11 Jun 2020 16:29:11 -0000

Could not easily find the answer to the following question:

Can i effectively use MP-TCP just to overcome possible loss of interfaces ?

E.g.: server and client each have two interfaces, connection is established
from client interface 1 address to server interface 1 address, the
additional addresses are exchanged via MP-TCP. Sometime during life-time
of both client interface 1 and server interface 1 fail in short order.

Q1: Can MP-TCP survive that ? That being general case of N addresses
on client/server and N-1 address failures simulateneously.

Q2: If so, does it require full-mesh of subflows or any other setup
of subflows ?

Thanks!
    Toerless


From nobody Thu Jun 11 09:41:31 2020
Return-Path: <olivier.bonaventure@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 8E7C73A0AB9 for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 09:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 4VWoe84JXUOQ for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 09:41:04 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30117.outbound.protection.outlook.com [40.107.3.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54B013A0AA6 for <multipathtcp@ietf.org>; Thu, 11 Jun 2020 09:41:03 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=azE+49Kx/VK6eQp7zVzZhrWwNi4H3yuFQvC75cDXhnGZ3UJgS6yrwRPBlgHDxOUXEy9bywUUYL2CTYAOsmiHMExR7liSQDO9UZUJuoFdV3ITbW2jRFjTqPPI/AEuT35YXtpU83qv0z+V3LAx+HRfEly6vwQNANTDkXw2A0oAahxR2huBWMiI3JfwNJ9jntg5UepifEJQIJ3fOi7NCLjZuDbnkf8hQjUf+4Os43YkpxtxrGjEL32izdisoRmJKGtnF+OsnZHmObzAcQvPqnJVxpj3QY+KG+3C7zLEocaOkV6mBzGaBZWrIzJj2eV1oPqAT8DWvJs/QehnF8TkFc31Gg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=00Usg2R5u3PYGy2ycjtLEeM+5rHRLsuQdCxac74Fctk=; b=CY/Z2AtG8N2kmVWMPIDp5vWum20wylt191GYH0JxDLGOgX8axs9ZIR4le5/dgjzSTwdtcjBdV+qThbY2UMOiDe16VThuJRpZTDMsUSlaSCUoCgo56DMpk5AD58lZbD+Iu7Upgs9jLUkoMswPX6uZq3gpkAR1vh95QSB+JOc10mASdRPmJ/It6otIT3pytDKnJogEUlwidhIoRAWZGcnPzAX1UYa3Q+Zo03n0mCKrxlwL0VatRBmI+PxQfFdeAtcck8+WEQE+yZkvDwZjgU/YOVN5Z1LMQUViiq8BfqFC4WD1XgBnu8pMnSyWcYZELkDZQwfgYSx9oX7jp5xk248Qng==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uclouvain.be; dmarc=pass action=none header.from=uclouvain.be; dkim=pass header.d=uclouvain.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uclouvain.be; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=00Usg2R5u3PYGy2ycjtLEeM+5rHRLsuQdCxac74Fctk=; b=o8cVupq14lxfhiqTAw7/BpaHJ8Ke+R8opVe5l89siC4GMf1J+4HUxBmOf/vEhKTbgddHhWgghi9lOBMvXZ9YFgxIMvUyU4I1sPJChucQ0wnqttRziruliaRfRuCsXVb1AAeHub39aqHKxuCKAyb8oxWAWAFfb135OcfLqVAFPaw=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=uclouvain.be;
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6) by AM7PR03MB6644.eurprd03.prod.outlook.com (2603:10a6:20b:1b6::6) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.18; Thu, 11 Jun 2020 16:41:01 +0000
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::fcc2:e19d:eec3:15e6]) by AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::fcc2:e19d:eec3:15e6%7]) with mapi id 15.20.3088.018; Thu, 11 Jun 2020 16:41:01 +0000
Reply-To: Olivier.Bonaventure@uclouvain.be
To: Toerless Eckert <tte@cs.fau.de>, multipathtcp@ietf.org
References: <20200611162904.GO16371@faui48f.informatik.uni-erlangen.de>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <c3a6428e-7351-fab4-31c7-3cf909bdd6e9@uclouvain.be>
Date: Thu, 11 Jun 2020 18:41:00 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
In-Reply-To: <20200611162904.GO16371@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr-classic
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: AM3PR05CA0097.eurprd05.prod.outlook.com (2603:10a6:207:1::23) To AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from mbpobo-2.local (2a02:2788:484:b4f:ac54:cecb:b45e:db5a) by AM3PR05CA0097.eurprd05.prod.outlook.com (2603:10a6:207:1::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.18 via Frontend Transport; Thu, 11 Jun 2020 16:41:01 +0000
X-Originating-IP: [2a02:2788:484:b4f:ac54:cecb:b45e:db5a]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 858e0985-c59f-48f1-220b-08d80e2639a6
X-MS-TrafficTypeDiagnostic: AM7PR03MB6644:
X-Microsoft-Antispam-PRVS: <AM7PR03MB6644C1EE64432B60628F7CCB86800@AM7PR03MB6644.eurprd03.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:7219;
X-Forefront-PRVS: 0431F981D8
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: sIVVHa5Sc3GzWhV1ng4mc4IQhKfDB7aPYjlNczJEABlBm6ES69Q/Zeb4prcKzwpFUgL470TpMLiyZD2DHGKGyWj2MRXzQAOAoNiOZz0oQT3yElPMHBUeLfhFWhvqgp4P3J3tfGooSWBrX4cnn3wwG7s2Ita566h+vbCix+1oHME3XhZEVSKdYCPs86YCFJZBa/U0t+tEbyNdczDPLAJgO2Gzoc7HxURkWq9en5gEm8oSwraNtV05kcMDbSGPVPTiloojrC+hJukruiEilon65O8RuHN9qcraPjRrC225M/oDKNn40sXbKd9S0Vdr7r4Af1bXu5nxmJY8u/pZUSgzUWeVpL3FW973n49EffMsclomVlhC1mEYqckgAvIMleJw+1fS702kSMONR4sI/7wYeNtCOGIhYX1/aSnA1fA5mQEnk+CD87r4Rd6wBMaaJNGgfGewCJXsPLvQLeNcxfoBvg==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM7PR03MB6642.eurprd03.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(376002)(366004)(39860400002)(136003)(346002)(396003)(6506007)(966005)(66556008)(16526019)(8676002)(5660300002)(52116002)(36756003)(186003)(66476007)(3450700001)(2906002)(478600001)(83380400001)(83080400001)(66946007)(86362001)(31686004)(31696002)(316002)(6512007)(786003)(6486002)(8936002)(2616005)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: PcQ6b1Cvp1d2uE07Q7Yvfw1CYnS65w81vWxBwmqBXtGgTOdgSsGb24kB6GRq4B2dgAsGpbBK0Moyjxn+NJh6QbvvzQjOcPr/2gcX4aVw1zpbz9koiRphetOSc+P3XcKzjc8QRfwglrVgvhVGQSozUL3Z0WHdUmFGPGf1Ymreo8ncBZqqP3lCdSdNyYzdNLgy91IBmiVymvjE5AfIHAI4EwQASYSR3Eyd7L+TNWmp3shSVQJqGMauSiK9vpDSlAf5h3B007oKkN9mhwAJ+40h4dYMGpYmqsKLzK9H+V4d+Ex+9l+t7ypE0xiQOSG504KCTerDEkkSHe4kYOxTO6s98GIJOSgnb1IbQM5s1PcuF95ayKYQosj6q27Ha0cB3r3Fgli2/SdzdX9HQs0wQ4H/A6EwrN/jTS7AQKbweBrEpKtjE+BA8g8kYr7x4MrocCQNf9eD8fqUeCCEwFylT7/3O4nYa17bBVXsJJ/DpgWwQxZpgh3SFsT0fGmKmI7l7VF8nwFiI6eyV2FHxDXLXLjPCGLUKM10woTPUgDK4gtGKT0Y3N5pVvu0DTh6f/NpVbpf
X-OriginatorOrg: uclouvain.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 858e0985-c59f-48f1-220b-08d80e2639a6
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Jun 2020 16:41:01.2655 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 7ab090d4-fa2e-4ecf-bc7c-4127b4d582ec
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: YIMQqFB3ag/N4mzbwRWXj0NynpoUJB15uEExaxAGtpud7+HXQZ9SzkXXLZ1B5q9U/TNV62HMwMf/rTIUgI8dcKSs3yM5v12Fuo0r46npW8DOUeoDWC4thMT+sKalobdC
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR03MB6644
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/y73eMscYB7pRQgsrvYYIvDChpS0>
Subject: Re: [multipathtcp] mptcp quick Q: MP-TCP for address redundancy
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: Thu, 11 Jun 2020 16:41:15 -0000

Hello,

> Could not easily find the answer to the following question:
> 
> Can i effectively use MP-TCP just to overcome possible loss of interfaces ?
> 
> E.g.: server and client each have two interfaces, connection is established
> from client interface 1 address to server interface 1 address, the
> additional addresses are exchanged via MP-TCP. Sometime during life-time
> of both client interface 1 and server interface 1 fail in short order.

Yes, this works.

> Q1: Can MP-TCP survive that ? That being general case of N addresses
> on client/server and N-1 address failures simulateneously.

Since MPTCP exchanges the different addresses, the client can try them 
in sequence to reach the server through the available one.

> Q2: If so, does it require full-mesh of subflows or any other setup
> of subflows ?

A full-mesh would open all subflows. You might need a reactive path 
manager that reacts to changes in subflows to recreate new ones, see 
e.g. chapter 7 of Viet Honag Tran thesis

https://inl.info.ucl.ac.be/publications/measuring-and-extending-multipath-tcp.html



Olivier


From nobody Thu Jun 11 09:53:32 2020
Return-Path: <matthieu.baerts@tessares.net>
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 9FCF03A0ABA for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 09:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tessares-net.20150623.gappssmtp.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 u7cd1CunKsjb for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 09:53:28 -0700 (PDT)
Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (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 6B9313A0AB9 for <multipathtcp@ietf.org>; Thu, 11 Jun 2020 09:53:28 -0700 (PDT)
Received: by mail-ej1-x632.google.com with SMTP id q19so7169864eja.7 for <multipathtcp@ietf.org>; Thu, 11 Jun 2020 09:53:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tessares-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=fNH9Cb5GSr6oddlo6bQbdkPH7zTGlcN60OLK2hFQtzc=; b=DK3YMsuRXkeXILFY8F6YY3NTAOlW7dkbDKQh2qHb35Y5HO0kZInzVByKdmxS13gJ39 gNUb90rqjBDQOQQNqTEFVwuZsJfMxAUtkkUNospZ6yR1y8DJjUx2m5WAcOmUD0BdznTk MPzj6iaIHwKjQI2Ytx5sqhzJTvzYarJalfvLCfC+FW7aTu504HLUMu139IWsEl7184xd Pys977NiI4eDKcHWcDI/YNEOsYmgNTsWdJo0sAg3OKlIVGz8SmOfvGMmZy3I+Ve3OJjA F1iFyS1lm5P9bEmsdWuVgOXSKRtTuREViSFW1w0/aGlVS6Jc/sXN1djQxhuKViFNDFDQ P4yA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fNH9Cb5GSr6oddlo6bQbdkPH7zTGlcN60OLK2hFQtzc=; b=Vy9BcZQTPN0kh2B93JgIjxkoR4mV0y7EGCkvzp4ViqFh84++eGCifQU8fk0u/MpMMS 7h5cQBF4fLrBVC7h4KEay/OA/xj5Bi7gRhvEKwpB2R2huqZiqh9xyReGE7lhHlxtun21 DOOykw3YTETbMlNCrH/arNwYt1J6Per9pznsT+JdX40wm43nBIVf0ecB/0ejg1kq03PG x7e+enMW7iWAdxBfGsTe9UFB/W194uHEYl3pZls6ZbtDFQHebgFbxWBziYJdFQb0x4S9 ZeBgmLBZr7TuBzQre9cVnsV/pRUmqTjTg2zcgwz/nWOV+FZZGlU09OHq2M/xuGulBeH3 sIcw==
X-Gm-Message-State: AOAM532EtftcyhmprcOg/hGfJkzL0/HWi3+jvusdoPRm08WZp7INtmow SElsjgcqoykbXE4D6Aqs8z8FQaoHwAk=
X-Google-Smtp-Source: ABdhPJzC1f7v1wuE4PLM2J5ErOLkiK8YnBkiMr5+W+gRf8ds481CtKhpKK25E0eDbn+IX61a1HZO5Q==
X-Received: by 2002:a17:906:3da1:: with SMTP id y1mr8875959ejh.109.1591894405046;  Thu, 11 Jun 2020 09:53:25 -0700 (PDT)
Received: from tsr-lap-08.nix.tessares.net ([79.132.248.22]) by smtp.gmail.com with ESMTPSA id a13sm2120830eju.59.2020.06.11.09.53.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Jun 2020 09:53:24 -0700 (PDT)
To: Olivier.Bonaventure@uclouvain.be, Toerless Eckert <tte@cs.fau.de>
References: <20200611162904.GO16371@faui48f.informatik.uni-erlangen.de> <c3a6428e-7351-fab4-31c7-3cf909bdd6e9@uclouvain.be>
Cc: multipathtcp@ietf.org
From: Matthieu Baerts <matthieu.baerts@tessares.net>
Message-ID: <5bc57349-c515-afba-1d7d-ee74775875ae@tessares.net>
Date: Thu, 11 Jun 2020 18:53:23 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <c3a6428e-7351-fab4-31c7-3cf909bdd6e9@uclouvain.be>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/_NvjZpgG5Sh1MMABKhnwUbnUu9o>
Subject: Re: [multipathtcp] mptcp quick Q: MP-TCP for address redundancy
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: Thu, 11 Jun 2020 16:53:31 -0000

Hello,

On 11/06/2020 18:41, Olivier Bonaventure wrote:
>> Q2: If so, does it require full-mesh of subflows or any other setup
>> of subflows ?
> 
> A full-mesh would open all subflows. You might need a reactive path 
> manager that reacts to changes in subflows to recreate new ones, see 
> e.g. chapter 7 of Viet Honag Tran thesis
> 
> https://inl.info.ucl.ac.be/publications/measuring-and-extending-multipath-tcp.html

If it is not an issue for you to open subflows but not using them for 
some interfaces, subflows can have the "backup" flag set.

With the out-of-tree Linux kernel, "backup" subflows will only be used 
if there is no other "non-backup" subflow. Maybe this could help you.

http://multipath-tcp.org/pmwiki.php/Users/Tools

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net


From nobody Thu Jun 11 10:48:22 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 08C243A0BEC for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 10:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=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 y498uigqBcHW for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 10:48:17 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 714A53A0B2B for <multipathtcp@ietf.org>; Thu, 11 Jun 2020 10:48:17 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 1F293548011; Thu, 11 Jun 2020 19:48:10 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 16426440043; Thu, 11 Jun 2020 19:48:10 +0200 (CEST)
Date: Thu, 11 Jun 2020 19:48:10 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Cc: multipathtcp@ietf.org
Message-ID: <20200611174810.GR16371@faui48f.informatik.uni-erlangen.de>
References: <20200611162904.GO16371@faui48f.informatik.uni-erlangen.de> <c3a6428e-7351-fab4-31c7-3cf909bdd6e9@uclouvain.be>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c3a6428e-7351-fab4-31c7-3cf909bdd6e9@uclouvain.be>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/IqBIWG5TZcU_9UWlfOe1FA69Hus>
Subject: Re: [multipathtcp] mptcp quick Q: MP-TCP for address redundancy
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: Thu, 11 Jun 2020 17:48:20 -0000

Thanks, Olivier

I am trying to understand what overhead and delay in recovery incurred
when i am using MP-TCP not for what i think it was designed for,
but just to deal with address redundancy in IP.

Aka: Imagine two routers each with N interfaces, but
only one active IGP calculated path between them. In practice,
one always uses a loopback interface address and never the
N physical interface addresses. But that is just operational
practice, i have not seen a comparison in actual RFC text.

Aka: instead of the loopback i do use the N interface addresses,
how best would i characterize the redundancy (speed of recovery
from actively used interface loss) and overhead of MP-TCP.

I guess i can try to go with

"higher complexity and per-connection state
due to handling N^2 addresses and potentially slower recovery
loss of actively used failing remote peer addresses,
and/or overhead of maintaining as many as N^2
sub-flows to minimize loss of any address" ?

Would that be a fair statement - specifically of course for the
case when it is known that there is only one path.

Cheers
    Toerless

On Thu, Jun 11, 2020 at 06:41:00PM +0200, Olivier Bonaventure wrote:
> Hello,
> 
> > Could not easily find the answer to the following question:
> > 
> > Can i effectively use MP-TCP just to overcome possible loss of interfaces ?
> > 
> > E.g.: server and client each have two interfaces, connection is established
> > from client interface 1 address to server interface 1 address, the
> > additional addresses are exchanged via MP-TCP. Sometime during life-time
> > of both client interface 1 and server interface 1 fail in short order.
> 
> Yes, this works.
> 
> > Q1: Can MP-TCP survive that ? That being general case of N addresses
> > on client/server and N-1 address failures simulateneously.
> 
> Since MPTCP exchanges the different addresses, the client can try them in
> sequence to reach the server through the available one.
> 
> > Q2: If so, does it require full-mesh of subflows or any other setup
> > of subflows ?
> 
> A full-mesh would open all subflows. You might need a reactive path manager
> that reacts to changes in subflows to recreate new ones, see e.g. chapter 7
> of Viet Honag Tran thesis
> 
> https://inl.info.ucl.ac.be/publications/measuring-and-extending-multipath-tcp.html
> 
> 
> 
> Olivier


From nobody Thu Jun 11 12:12:31 2020
Return-Path: <olivier.bonaventure@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 69F083A00AD for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 12:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level: 
X-Spam-Status: No, score=-2.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 FGKaYitrruNk for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 12:12:26 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30114.outbound.protection.outlook.com [40.107.3.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FC493A0061 for <multipathtcp@ietf.org>; Thu, 11 Jun 2020 12:12:26 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=K+Myc2BZeJumESvBJ412P/jlfSb533E0xvO3P0j807tk/4j4gmqmXIe7PpfI5tnapAAL/WcHe+coamDMC0q9NxfJ7NfTqaZmnuqroh7z3EOUA2na4FE3ny2kpsFhdBft+hVJwBzsHjRuFVu7Lyq7gQJyxD6o4PSd0kaKWFjCyOWOVO74XE35LbCMLdJ8rYGqQdG2gIwPJ/J/rnJ9RnD1qKk7tkvT4Q3+xxH6e8u09y8pq1UL7XV9pOcEQkgPIDIdROIMr49GeToxq3ywsGvbDg5LCdX0NxdHw+a2YNsp4Ts7e8nH9y2Kujk7oPeHN6eLnwkGxlJJBMgKAguBKHBrXA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=E1mwXDq2Jz1sVzATsMpebd3manIFGZQeI2kXfXGpOXY=; b=S7hKDXKBUALFLm2Cc9ZAP/xwnQPEHqigaWzZf4UAQqfA58VhxnC1iDbjZ22dnvdl2pPbz6yzHl7hTifLuX27l05FGxMFoPy5WDaRN36Fs9XybCXkN76GYSIGuI+UhsVi49b+M0vEKUCh0sBKc4s7rw3oRK81DVuUHQjFtBenGrkIdZBR9Z+gYh6fo8bPV39MEwGYE7zYtH03CY7EAMlb8g8BibXFNaxXfKoSikJb+RuuxORgxhf1+60oZlSTgOKO8E/7Bh+hC1tQGGBTqMRF0otafP3q57VluZ97+tT0NyYcEVGXyL7HKj8b1SIuvrJRl/URMegIrIkHLpsiWApWRA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uclouvain.be; dmarc=pass action=none header.from=uclouvain.be; dkim=pass header.d=uclouvain.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uclouvain.be; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=E1mwXDq2Jz1sVzATsMpebd3manIFGZQeI2kXfXGpOXY=; b=snwYIfkdMT5aUTipXXWJajqUFiFNTwXzpyAYHJym6FwMcQ+RwC7BN9pmUib7aSGyvvL6oox/OeK9BNtwD5IYtBLrTKwBwHoy6AMNHH4zXE74afZ/s5hL3tcpDPtoBUnGn/j6dZhrk6yejGJ+9SQ0TlE5uOJs/15XCO2vh5Cc6PU=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=uclouvain.be;
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6) by AM7PR03MB6168.eurprd03.prod.outlook.com (2603:10a6:20b:140::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.21; Thu, 11 Jun 2020 19:12:23 +0000
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::fcc2:e19d:eec3:15e6]) by AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::fcc2:e19d:eec3:15e6%7]) with mapi id 15.20.3088.018; Thu, 11 Jun 2020 19:12:23 +0000
To: Toerless Eckert <tte@cs.fau.de>
Cc: multipathtcp@ietf.org
References: <20200611162904.GO16371@faui48f.informatik.uni-erlangen.de> <c3a6428e-7351-fab4-31c7-3cf909bdd6e9@uclouvain.be> <20200611174810.GR16371@faui48f.informatik.uni-erlangen.de>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <fbd4fb80-b608-d81a-f292-ef26d41ab665@uclouvain.be>
Date: Thu, 11 Jun 2020 21:12:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
In-Reply-To: <20200611174810.GR16371@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: AM0PR04CA0001.eurprd04.prod.outlook.com (2603:10a6:208:122::14) To AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [IPv6:2a02:2788:484:b4f:d1c9:4168:417c:2fb6] (2a02:2788:484:b4f:d1c9:4168:417c:2fb6) by AM0PR04CA0001.eurprd04.prod.outlook.com (2603:10a6:208:122::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.18 via Frontend Transport; Thu, 11 Jun 2020 19:12:23 +0000
X-Originating-IP: [2a02:2788:484:b4f:d1c9:4168:417c:2fb6]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 701879da-5751-4416-8455-08d80e3b5f15
X-MS-TrafficTypeDiagnostic: AM7PR03MB6168:
X-Microsoft-Antispam-PRVS: <AM7PR03MB6168C0EA58411E9E5CAE346B86800@AM7PR03MB6168.eurprd03.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-Forefront-PRVS: 0431F981D8
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: Dmcj+KXYjTQdDq3GqHRLkyyc5LPXJ6DqX5axUGEPqmwYO9uKnQnHjDtka+p7tDdjgKdWXzqmOHy3pm4afGWuZRoRzLJAwqfbE+EX+Hubq0x0Xxkm7MEsfM86RRiPCVZd9eu0n2gHPxoZgw1tHYA+LAH4xVNzFbHaMkYVzOhK9e/k+9xD6slplg6xUQEwnM23qXSCvYyR1eiItBU8D/uwpx93SScdTnwI1THj5LdXB+nTB6fc3DUbhYXOLlQXGQ97MwQP5QPcVE+JL/NojurE8614X99P8m8m9PI4naR1eZ8T6eaZ9TPEnYz56+ondrlBEFLuwbWxQm6spdgrIIUoDdO2vmdg7KXZRfoqqxETNnT12JtFRISXtnjpoX343OVO
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM7PR03MB6642.eurprd03.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(136003)(39860400002)(346002)(396003)(376002)(366004)(2906002)(316002)(786003)(186003)(31696002)(478600001)(2616005)(52116002)(66476007)(16526019)(6916009)(66556008)(66946007)(4326008)(86362001)(8676002)(31686004)(83380400001)(66574014)(8936002)(6486002)(5660300002)(36756003)(43740500002); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: 9ug+cjOOLz2vasUOQLxYyDDXfwy8gVkcN2uc7E7ejvhgVUCxqTFzMdUWtxXwLME0zWzB1ueo5BDQIVz9pF47BHEB30wwEscg6qqBWppFk2LWWHxEmq7TEekyhOmmYKDkxUCumBWFpPHA9xsKMZ+umz+EpMfEF+D/gAAgRYVMNJiw258bNSjnv/P050Y59byOL8uYSz6/91XMwzvQEiVF6WXvsBWIEFrXk9eQ4I4OFzVBuqh0hPYJqJAO1aI3QzhCajtLFw1COTXJ0B9+Oh0XCU4lXAYRUrHZ1mWadgfcXhPY/e2aUz19Kr9Xs9ZMoQxpBmO3T2PJNhM1PyKpItJFqsb53kNWNcEStUwIONDuzbcSl4ojTUpHx4pJ5ejawZ3dZZ0NW2/Q5AgJ79nMwoEgkQ7JmiVKY2Y1rIrWa6aAYI61dabnpnQ/+YiCOqIBVmeYsVjXmA1unMDoIxTjMcCNScFw0jP4nqsUXpFZsLMtOmUQHsS4MgOVmVe/J71vMedLS+gkgfwvIRCSxl5hD19S3E2TGBb0kykG/0ETida2mGE2OA4a1QyaEZpK2x3s58Wr
X-OriginatorOrg: uclouvain.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 701879da-5751-4416-8455-08d80e3b5f15
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Jun 2020 19:12:23.5424 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 7ab090d4-fa2e-4ecf-bc7c-4127b4d582ec
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: xXQo8s1D52Zd5YfAv4XONfymbiUEA+fGUJQfxlW9BknVhPgvtGVDXLRjTlK4YlP8D1y/RKwdAT1VSoM9OHuHPsyGqnjzTWQlxVyYLhPkeIN5kIPCFvxgixLWNPcDYfL4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR03MB6168
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/AFZaANQy6vCifc-nPxa3-vwbLVQ>
Subject: Re: [multipathtcp] mptcp quick Q: MP-TCP for address redundancy
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: Thu, 11 Jun 2020 19:12:29 -0000

Hello,
> 
> I am trying to understand what overhead and delay in recovery incurred
> when i am using MP-TCP not for what i think it was designed for,
> but just to deal with address redundancy in IP.

This mainly depends on how the path manager is tuned. With MPTCP, you 
can do make before break or break before make. As mentionned by Mathieu, 
you can also use the backup bit to only use one primary subflow and 
leave the other as backups.

> Aka: Imagine two routers each with N interfaces, but
> only one active IGP calculated path between them. In practice,
> one always uses a loopback interface address and never the
> N physical interface addresses. But that is just operational
> practice, i have not seen a comparison in actual RFC text.

Taking the router example, one could run iBGP sessions over MPTCP. The 
session would be established to one of the IP addresses of the routers 
and the others would be learned automatically, enabling a failover in 
case of failure of the initial one. The BGP session could initiate all 
subflows and select the one with the lowest rtt.

> Aka: instead of the loopback i do use the N interface addresses,
> how best would i characterize the redundancy (speed of recovery
> from actively used interface loss) and overhead of MP-TCP.

If there is a second subflow, MPTCP can typically recover from a failure 
within one or a few rtts since it checks for an alternate subflow when 
it retransmits data. This can be tuned and some have proposed schedulers 
that duplicate packets.

> I guess i can try to go with
> 
> "higher complexity and per-connection state
> due to handling N^2 addresses and potentially slower recovery
> loss of actively used failing remote peer addresses,
> and/or overhead of maintaining as many as N^2
> sub-flows to minimize loss of any address" ?

MPTCP does not need to maintain all the NÂ² subflows. It can decide to 
only create a few subflows, say 3 or 4 over very diverse addresses. 
That's a path manager decision.

With MPTCP, once an address fails, it is announced over one subflow 
using rm_addr and all the subflows that use this address fail immediately.

> Would that be a fair statement - specifically of course for the
> case when it is known that there is only one path.

It is possible to tune MPTCP depending on the use case that you have. If 
you want fast failover, it is possible to create some additional 
subflows, use a redundant scheduler to reduce the failover time at the 
expense of more overhead


Olivier


From nobody Thu Jun 11 12:58:32 2020
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 819223A0964 for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 12:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 X5oHtrnfosBb for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 12:58:29 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 209623A0956 for <multipathtcp@ietf.org>; Thu, 11 Jun 2020 12:58:29 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id D6C09548045; Thu, 11 Jun 2020 21:58:23 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id D1113440043; Thu, 11 Jun 2020 21:58:23 +0200 (CEST)
Date: Thu, 11 Jun 2020 21:58:23 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Cc: multipathtcp@ietf.org
Message-ID: <20200611195823.GU16371@faui48f.informatik.uni-erlangen.de>
References: <20200611162904.GO16371@faui48f.informatik.uni-erlangen.de> <c3a6428e-7351-fab4-31c7-3cf909bdd6e9@uclouvain.be> <20200611174810.GR16371@faui48f.informatik.uni-erlangen.de> <fbd4fb80-b608-d81a-f292-ef26d41ab665@uclouvain.be>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <fbd4fb80-b608-d81a-f292-ef26d41ab665@uclouvain.be>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/faH-rtxhZsc9Em5Qccu_uoe1xHg>
Subject: Re: [multipathtcp] mptcp quick Q: MP-TCP for address redundancy
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: Thu, 11 Jun 2020 19:58:32 -0000

Thanks, Olivier,

Not quite sure from your reply what applies to non-backup vs. backup subflows,
you did not say.

Also: Is it necessary to avoid loosing all sub-flows, or does
that only speed up recovery ?

Aka: If i start with one subflow, learn additional addresses, but
not create additional subflows (just announce addresses), and
now one of the peer has an interface failure and this only
sub-flow fails. Would it then still be able to create a new 
subflow from a different address ?

Sorry, even to me these questions sound 101, but really hard to read 
asnwers from the spec to the uninitiated...

Cheers
    Toerless

On Thu, Jun 11, 2020 at 09:12:22PM +0200, Olivier Bonaventure wrote:

> This mainly depends on how the path manager is tuned. With MPTCP, you can do
> make before break or break before make. As mentionned by Mathieu, you can
> also use the backup bit to only use one primary subflow and leave the other
> as backups.
>
> Taking the router example, one could run iBGP sessions over MPTCP. The
> session would be established to one of the IP addresses of the routers and
> the others would be learned automatically, enabling a failover in case of
> failure of the initial one. The BGP session could initiate all subflows and
> select the one with the lowest rtt.
>
> > Aka: instead of the loopback i do use the N interface addresses,
> > how best would i characterize the redundancy (speed of recovery
> > from actively used interface loss) and overhead of MP-TCP.
> 
> If there is a second subflow, MPTCP can typically recover from a failure
> within one or a few rtts since it checks for an alternate subflow when it
> retransmits data. This can be tuned and some have proposed schedulers that
> duplicate packets.
>
> > I guess i can try to go with
> > 
> > "higher complexity and per-connection state
> > due to handling N^2 addresses and potentially slower recovery
> > loss of actively used failing remote peer addresses,
> > and/or overhead of maintaining as many as N^2
> > sub-flows to minimize loss of any address" ?
> 
> MPTCP does not need to maintain all the N² subflows. It can decide to only
> create a few subflows, say 3 or 4 over very diverse addresses. That's a path
> manager decision.
> 
> With MPTCP, once an address fails, it is announced over one subflow using
> rm_addr and all the subflows that use this address fail immediately.
> 
> > Would that be a fair statement - specifically of course for the
> > case when it is known that there is only one path.
> 
> It is possible to tune MPTCP depending on the use case that you have. If you
> want fast failover, it is possible to create some additional subflows, use a
> redundant scheduler to reduce the failover time at the expense of more
> overhead
> 
> 
> Olivier

-- 
---
tte@cs.fau.de


From nobody Thu Jun 11 13:19:26 2020
Return-Path: <olivier.bonaventure@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 D915D3A0CF8 for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 13:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 u3e6DDxdTjBs for <multipathtcp@ietfa.amsl.com>; Thu, 11 Jun 2020 13:19:22 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2131.outbound.protection.outlook.com [40.107.22.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A94A63A0CF3 for <multipathtcp@ietf.org>; Thu, 11 Jun 2020 13:19:21 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Gllcd3XSvPMDQI+riEv8CLmsqoGxwuKN7sl2otX6lyvwc9a/1G+Gv2+tETbELyd75eDp6ZYGgQ9OiMwxWjaC6rhEGWBWh9VLSYzZcXOaZqjFp9+/l7QKRYv3ojyQv20mkI7n54Dh3qXYhiwHVa43D+iKX/r5v/En8RiMBoQsKp1v/rkaMOXWZS1C7DQyIq5DJ743fyaZOllE4DdDkWId1geWb0tJoHwjEdoGaofInyAkbiFEq5KE3X5vvma7nBXNMgyiBYbO6sYw4qgYhTkzljpobPFU47IbflEPVv4UnW3QfFImw+axH/sFHXcoQYh5jwplsk4yHNyxaeb+CaE/vg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L0PPw4xR0ewzuM5ym5zPKM6I+wUXXww6FVbm552vBeA=; b=PPcYnh/jbAnpLD9AqXIPlog8fZuJOcX8Qz0WmItz0iQpapFZtPDxbK1myc1VxnI+unu/YyNFcU+Zulr151sTA4GQrM6G7h/s0EZPgm7pJpakpsa7pSd9ZFLZfqaHvUSUE9lH4IkCabzobjORrAENhzLWEKtI1f66Ns83PRHDLizyt8F6ocVRL+uv5tfKQcRqy+JoIV06IAmKyiWf27vuy6M6G9x4kOuA36mbgX3wNa/SMSXd45RDYjv1U2Rva5rcoD8/MZ5eLUvbHyfbebmdtRlAfQVDmKC0rpWhizwKP/0k4oeNbOb7JCr+uD9spuU0mN7PKv2HENJolEYDuufxyA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uclouvain.be; dmarc=pass action=none header.from=uclouvain.be; dkim=pass header.d=uclouvain.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uclouvain.be; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L0PPw4xR0ewzuM5ym5zPKM6I+wUXXww6FVbm552vBeA=; b=r6NIRsCFdgRMZKlSdtuW7CU8UI2jwGnvzNsI/hS5VdgMlRoT8Fr2SHpcJ1B7gT1UVJTwBC4qzy6wGCq7rsxYINnUzPMambTnlJrP9E36JQttHg/v/OwIbkZ9H3WbhpmHdIEEfUITk5FHJ5vkNRnvN+LyOfnXq71+gLL6F64zQzQ=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=uclouvain.be;
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6) by AM7PR03MB6261.eurprd03.prod.outlook.com (2603:10a6:20b:142::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.18; Thu, 11 Jun 2020 20:19:19 +0000
Received: from AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::fcc2:e19d:eec3:15e6]) by AM7PR03MB6642.eurprd03.prod.outlook.com ([fe80::fcc2:e19d:eec3:15e6%7]) with mapi id 15.20.3088.018; Thu, 11 Jun 2020 20:19:18 +0000
Reply-To: Olivier.Bonaventure@uclouvain.be
To: Toerless Eckert <tte@cs.fau.de>
Cc: multipathtcp@ietf.org
References: <20200611162904.GO16371@faui48f.informatik.uni-erlangen.de> <c3a6428e-7351-fab4-31c7-3cf909bdd6e9@uclouvain.be> <20200611174810.GR16371@faui48f.informatik.uni-erlangen.de> <fbd4fb80-b608-d81a-f292-ef26d41ab665@uclouvain.be> <20200611195823.GU16371@faui48f.informatik.uni-erlangen.de>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <ff9d26fd-56dc-54c2-7ca7-a295d02e855a@uclouvain.be>
Date: Thu, 11 Jun 2020 22:19:17 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
In-Reply-To: <20200611195823.GU16371@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr-classic
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: AM0PR02CA0015.eurprd02.prod.outlook.com (2603:10a6:208:3e::28) To AM7PR03MB6642.eurprd03.prod.outlook.com (2603:10a6:20b:1bf::6)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from mbpobo-2.local (2a02:2788:484:b4f:2583:94b7:2b87:1928) by AM0PR02CA0015.eurprd02.prod.outlook.com (2603:10a6:208:3e::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.19 via Frontend Transport; Thu, 11 Jun 2020 20:19:18 +0000
X-Originating-IP: [2a02:2788:484:b4f:2583:94b7:2b87:1928]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 9ea6a3a2-918f-4e01-1655-08d80e44b85a
X-MS-TrafficTypeDiagnostic: AM7PR03MB6261:
X-Microsoft-Antispam-PRVS: <AM7PR03MB626137D49CA48C43497F5E6686800@AM7PR03MB6261.eurprd03.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-Forefront-PRVS: 0431F981D8
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: y00fZ1Q5xFGtT2taup0AK1CyqK5ajXz81RVcBvfX6MJmUaz++0v3hwOafVyOtJFkhM0Q5CtUguxIT3tWu5B4micCoWgBYVhis3XRzH7cr32zdGKHNZWwJeir2GndCUYRyKBhXKZ2F6hrBtnIhTqPO8s+cBLKFuNv3SGzqqWk+xxTT1Ml15x4oejb7BsPpc4bRJgwGXLSLJyLpDYLjNe2Je7UfFED+mVBflIb5glDT0ALbyIhbJbOIWyJJb7LOib4oVpI1c2YUAjLwhT+bP2z7/qELJrqOY14KaSZp4+EBincxTaU5ZGk1f/QTyCT7v257ug2qQWTUVIzhqXgfmlnvj7iiD19dF93H1LSA8Qm+jSvjx56zflrJHgIQ+YQRApW43hocRMnpfYojKsVuaYrY9JjwLqm3BnjL0WdxIjlyHBPF5ZYJWb2RDC/2zj5NyIcxn5jyItUMZbYqKXExqnV4vG2ylFULJ53GJsk3hbVeEs=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM7PR03MB6642.eurprd03.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(366004)(376002)(136003)(396003)(346002)(39860400002)(2906002)(8936002)(3450700001)(6486002)(52116002)(478600001)(8676002)(186003)(36756003)(16526019)(6506007)(31686004)(83380400001)(19273905006)(66476007)(5660300002)(66946007)(6512007)(66556008)(86362001)(31696002)(6916009)(316002)(966005)(786003)(4326008)(2616005)(43740500002)(563064011); DIR:OUT; SFP:1102; 
X-MS-Exchange-AntiSpam-MessageData: qBp63bwu9YbfHVCqXIQYTFbQvfjQzRa0Pgi4YgpVziI1rxzm5qKF3dVl8B9jqLE0puYJwLd1meYC4KRzaTPkwEiGCUsr69GaJ5IafwLA6+ugMqFAY1O3h01dWPrkylGxJiM0fVU3hZ0FzHPWYyXce5rJ0QT9KZVdEcWaKwmhNidR5zGxRLUnUkwWloQvjGu0BRxD+UcMdUCApGU8rp+F8iaaNp4QALwCsZKgcdID5b/txPZcZUUOre4xyDpjQtPoycjvPwVRnbWEkU+wevx4vbFa1kPob8LzmxDseHOTUY30teL4h1A0red5P7TpfZ2Zde3zvmImuLfV68E/NX57NWDH2oTuChVuUTzrTFBDlfB0yhW70kuMBt7rmfNQppXET3f4/wtG/wgZJj7IhU09DloUWnlIbybPNrqkI4Cn+tjKyI4XGhsvvY4d/wmvahUAlfriCTVOe1kY1XKuh1bex2MscB58W2JrrR8w53r8tz0/PilJYSQ+/WV70JzlzsPXdA+IRh8IOMaGXTciAyvEGIgOr7YQFamvebBTBnSwgk2a8h/IqpThTR5cPuwGOH9/
X-OriginatorOrg: uclouvain.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 9ea6a3a2-918f-4e01-1655-08d80e44b85a
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Jun 2020 20:19:18.7656 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 7ab090d4-fa2e-4ecf-bc7c-4127b4d582ec
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: ZpMw4NvxogSvk7nP1wFWt4/XCldBNXIaqNc6FKph93U6bRbgClIBtRK8BURSKy7a0b5XVThI3AdM5V+ivGBLuXCSBTXWWl1LUs1SC+jflp1XOoVYppgHGGddsxDpCPaQ
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR03MB6261
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/GJsjGOYs8Mbc7eg_anrJhS8gjqI>
Subject: Re: [multipathtcp] mptcp quick Q: MP-TCP for address redundancy
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: Thu, 11 Jun 2020 20:19:25 -0000

Toerless,
> 
> Not quite sure from your reply what applies to non-backup vs. backup subflows,
> you did not say.

MPTCP only uses a backup subflow if there is no available non-backup 
subflow.

> Also: Is it necessary to avoid loosing all sub-flows, or does
> that only speed up recovery ?

That speeds up the recovery but is not required. MPTCP supports both 
make before break and break before make.
> 
> Aka: If i start with one subflow, learn additional addresses, but
> not create additional subflows (just announce addresses), and
> now one of the peer has an interface failure and this only
> sub-flow fails. Would it then still be able to create a new
> subflow from a different address ?

Yes. Subflows can be created at any time from any local address to any 
of the addresses learned from the peer. Note that the client does not 
need to advertise its addresses to be able to use them to reach a 
server. For example, a smartphone has only Wifi enabled and connects to 
a server. It leaves out of reach of the Wifi, the subflow fails. It then 
enables its cellular interface, obtains an IP address and use it to 
create a new subflow to the server.
> 
> Sorry, even to me these questions sound 101, but really hard to read
> asnwers from the spec to the uninitiated...

There are a few tutorials on MPTCP where this is partially discussed:

https://www.usenix.org/publications/login/october-2012-volume-37-number-5/overview-multipath-tcp
https://dl.acm.org/doi/10.1145/2578508.2591369
http://www.sigcomm.org/content/ebook (chapter 2)
https://www.youtube.com/watch?v=PkvLq_kCv4o


Hope this helps


Olivier

