[multipathtcp] FW: New Version Notification for draft-amend-mptcp-robe-01.txt

<Markus.Amend@telekom.de> Tue, 05 November 2019 07:02 UTC

Return-Path: <Markus.Amend@telekom.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 5056D120020 for <multipathtcp@ietfa.amsl.com>; Mon, 4 Nov 2019 23:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level:
X-Spam-Status: No, score=-4.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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=telekom.de
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 ufsDpxzDn3DC for <multipathtcp@ietfa.amsl.com>; Mon, 4 Nov 2019 23:02:46 -0800 (PST)
Received: from mailout21.telekom.de (mailout21.telekom.de [194.25.225.215]) (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 0C538120013 for <multipathtcp@ietf.org>; Mon, 4 Nov 2019 23:02:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1572937282; x=1604473282; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=D2fy5v4o5K6FRUPJu3Zhu7NteJO8RGia658YcLwNGro=; b=a0rNna/LPWqGvVv6fJVanKN7PVN5PLAoKIiDq3sqwdc8vzaz7dAAxhzw Ws60AtBH+K6ymtqa7sYxG9KvGG+NPhn8cLWoZ/Kiub7zsWzpelqeyUk9e 0SALlABsJ2g2cwqeAUyFQDNCfLsewwCYTPREkOoBf53X1S6IouMsIx/e4 wYTkGQtxq1uTfvbIlSgM5wcC5rhrI432VUoWiSxrkHG867vyVp/jy85S2 wnkwOYgFVB5zQWEfKZfXXk16RcDSBHy7a3naqw1b4NEJTzccPttn9iOu+ /avni3J6L4sIPqK4IhyOobFNm/zPT/1ELpoJCcmKgw8SYDzJYGxseVEUj w==;
IronPort-SDR: 2F/B36I5dO7MIAvkOzQWv+ZRK1f5VMSgmY399jFcR5AZJlCysAAnwYGDZQ/QWqmJcOe8am1FGH 02MSnW40bv5w==
Received: from qdec94.de.t-internal.com ([10.171.255.41]) by MAILOUT21.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Nov 2019 08:01:20 +0100
X-IronPort-AV: E=Sophos;i="5.68,270,1569276000"; d="scan'208";a="534887281"
X-MGA-submission: =?us-ascii?q?MDGfLUbJccSkSmBY1InxHdGiiZ4C/tO011YuTj?= =?us-ascii?q?kFZM7fhbvQLjVAhjuLnbSPnYnHXunuMbLUR2/kpEcpy7HChQBxwESQ84?= =?us-ascii?q?dBryGdIMtu0pVMJSRg0G4noOY04GVeX4t0s8yO/9zmxKjXxLWQkaeJKJ?= =?us-ascii?q?u0ZWhF6jaNyRWy4HSUyPhv3g=3D=3D?=
Received: from he199745.emea1.cds.t-internal.com ([10.169.119.53]) by QDEC97.de.t-internal.com with ESMTP/TLS/AES256-SHA; 05 Nov 2019 08:02:43 +0100
Received: from HE199743.EMEA1.cds.t-internal.com (10.169.119.51) by HE199745.emea1.cds.t-internal.com (10.169.119.53) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 5 Nov 2019 08:02:42 +0100
Received: from HE100181.emea1.cds.t-internal.com (10.171.40.15) by HE199743.EMEA1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 5 Nov 2019 08:02:42 +0100
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.15) by O365mail02.telekom.de (172.30.0.235) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 5 Nov 2019 08:02:42 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZKRuXgR5ajMbVHAt5zd8knXujtZV/8rCw9Ta45yBkPuxWD7gPnmUYXErw12/oRkKYmEfbIkOCw6u7TS6OpkfDqCqr0N9SyW6SxSK+TJAgNHQ+3BHQNzCK9sbY3jWTOyGtGn2/BhswkzHULf0oWELB3bRKcylNxF4ql6pOKbRYy4YX+V8nNcyIK08O9lFj6oDdGEAUyaL7DUKp3upoDJ98htUTQbjOGbeKrHZK+6p8eTmWCwxnocEoRlRLUGo4RFqH5bbnRjCMzRaiRbcTvT5yNC6w76OJNjq+5IG5VPk6Ym3irXAPWEr3gLKA9K/pKzpaiXT4FZLXJe8sVB4gHIrng==
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=D2fy5v4o5K6FRUPJu3Zhu7NteJO8RGia658YcLwNGro=; b=H+fP1JfVLApMoRLL3YLFWLsYinwbeiR/TaWJuv0E7ThNCTFq3lSHoH4bJqFfBjOmvQqvY9C3Nvwbx7H+9gqQmKX9FRuO+fGy18buG9JXzr/xuwhIoD9WpSQASt15O+wvbJYavl/qUe+8jeaRWWrsDIXzleAh232rEjQ/ew8DDOy1qrmlevl2z/n3bM4L+KDGo6tKtNrASvH0MLJIrcGFvBieuHIB29c8iGof4tEZRddFIdmS5AIHQ5pnN0i+2NSuj+B8gnn6ybWJ18+0pHlHx/QaLEild7zgf54BGIwkLcephJAT2iGR/7rza4PtPn/Fav2guM4Gdq7Ehr0psOjk9A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.21) by FRAPR01MB0324.DEUPRD01.PROD.OUTLOOK.DE (10.158.132.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Tue, 5 Nov 2019 07:02:42 +0000
Received: from FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE ([fe80::91e0:b45b:8926:2686]) by FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE ([fe80::91e0:b45b:8926:2686%8]) with mapi id 15.20.2408.024; Tue, 5 Nov 2019 07:02:42 +0000
From: <Markus.Amend@telekom.de>
To: <multipathtcp@ietf.org>, <kangjiao@huawei.com>
Thread-Topic: New Version Notification for draft-amend-mptcp-robe-01.txt
Thread-Index: AQHVk1DaYiz33a6mZUahYIHjVSPX5ad8HNbQ
Date: Tue, 5 Nov 2019 07:02:41 +0000
Message-ID: <FRAPR01MB11709C71DC3E184AE12975F7FA7E0@FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE>
References: <157290035048.13916.17837551480038897219.idtracker@ietfa.amsl.com>
In-Reply-To: <157290035048.13916.17837551480038897219.idtracker@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Markus.Amend@telekom.de;
x-originating-ip: [212.201.104.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d41e4b14-c5cc-4ecf-8b07-08d761be26f5
x-ms-traffictypediagnostic: FRAPR01MB0324:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <FRAPR01MB0324BBFEDEBFB5049369572DFA7E0@FRAPR01MB0324.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 0212BDE3BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(366004)(396003)(346002)(376002)(39860400002)(189003)(199004)(13464003)(186003)(2906002)(966005)(81166006)(413944005)(55016002)(316002)(53546011)(66556008)(7696005)(7736002)(110136005)(14444005)(102836004)(66446008)(76116006)(71190400001)(8936002)(66946007)(64756008)(66476007)(71200400001)(305945005)(76176011)(6116002)(81156014)(8676002)(86362001)(446003)(11346002)(256004)(14454004)(486006)(33656002)(5660300002)(66066001)(15650500001)(229853002)(6306002)(9686003)(2473003)(478600001)(3846002)(26005)(476003)(66574012); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0324; H:FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: sM8e0mdugdajOYRN4E8u0AKoSEyweKYyrXOv6MUV8RRmcG9X6FLOiUv6LCpVua12oXUzS+RlNu3j1HJ2jLk80PShIcawyDrnO0XGzbwVtWD6GWQic5ZePpcJJvOdpuZOcC6pAEESgbHzk3ik3SkRdr4rhHi6V1StKfTHtALqcauHsF+v17eFEBBMjbK6lOSsmX/F/740xAWXsp/3eu80/IwpE9nevZfCPfaA0wTA0cooU7wnoEBx9wHYzprje36/lbGM0Cvjb7tJqbCZJgL9T36oqGtVpmMbvk32cPjr8Ykg7jkafVOVnlEJImSN1IL/G5KyVtA3r7R6XfAPrRA++ss2be/jyZ7qmONteWkYpJFBV6piiCj6n06Sth5HMv2MUyUo6UoMn/1zCdhvBlp3ckyXsWbUDe540o54MWLmSkWnYX8RstUPG96IotFPdvjn5KtTlyUe5CqAPgtwkkSNvAfixxO7vnK1CvJffw+/vUU=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d41e4b14-c5cc-4ecf-8b07-08d761be26f5
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Nov 2019 07:02:41.8790 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: bL/bgRLUMJHHRngohGrQqXR31t/lYSl1+VSrNHICzOf8vxWmCUQzSyMiLHIL9BGdI0PQ3RzJX2XnYNRff/jL5A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB0324
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/XW1KAMxlQ8CtpLe_G-2LWPMzbiE>
Subject: [multipathtcp] FW: New Version Notification for draft-amend-mptcp-robe-01.txt
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: Tue, 05 Nov 2019 07:02:54 -0000

Dear all,


I'm happy to announce the availability of a significantly improved next RobE draft version emerging from the previous draft and draft-kang-mptcp-initial-path-selection.

This time, the document gives a much more complete overview on solutions to redcuce the probability that MPTCP fails at connection establishment. By differentiating the solutions between RFC6824(bis) compatible and requiring protocol modifications, a clear structure is introduced.

BR

Markus


> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> Sent: Montag, 4. November 2019 21:46
> To: Amend, Markus <Markus.Amend@telekom.de>de>; Amend, Markus
> <Markus.Amend@telekom.de>de>; Jiao Kang <kangjiao@huawei.com>
> Subject: New Version Notification for draft-amend-mptcp-robe-01.txt
> 
> 
> A new version of I-D, draft-amend-mptcp-robe-01.txt has been successfully
> submitted by Markus Amend and posted to the IETF repository.
> 
> Name:		draft-amend-mptcp-robe
> Revision:	01
> Title:		Multipath TCP Extension for Robust Session Establishment
> Document date:	2019-11-04
> Group:		Individual Submission
> Pages:		27
> URL:            https://www.ietf.org/internet-drafts/draft-amend-mptcp-robe-
> 01.txt
> Status:         https://datatracker.ietf.org/doc/draft-amend-mptcp-robe/
> Htmlized:       https://tools.ietf.org/html/draft-amend-mptcp-robe-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-amend-mptcp-robe
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-amend-mptcp-robe-01
> 
> Abstract:
>    Multipath TCP extends the plain, single-path limited, TCP towards the
>    capability of multipath transmission.  This greatly improves the
>    reliability and performance of TCP communication.  For backwards
>    compatibility reasons the Multipath TCP was designed to setup
>    successfully an initial path first, after which subsequent paths can
>    be added for multipath transmission.  For that reason the Multipath
>    TCP has the same limitations as the plain TCP during connection
>    setup, in case the selected path is not functional.
> 
>    This document proposes a set of implementations and possible
>    combinations thereof, that provide a more Robust Establishment (RobE)
>    of MPTCP sessions.  It includes RobE_TIMER, RobE_SIM, RobE_eSIM and
>    RobE_IPS.
> 
>    RobE_TIMER is designed to stay close to MPTCP in that standard
>    functionality is used wherever possible.  Resiliency against network
>    outages is achieved by modifying the SYN retransmission timer: If one
>    path is defective, another path is used.
> 
>    RobE_SIM and RobE_eSIM provides the ability to simultaneously use
>    multiple paths for connection setup.  They ensure connectivity if at
>    least one functional path out of a bunch of paths is given and offers
>    beside that the opportunity to significantly improve loading times of
>    Internet services.
> 
>    RobE_IPS provides a heuristic to select properly an initial path for
>    connection establishment with a remote host based on empirical data
>    derived from previous connection information.
> 
>    In practice, these independent solutions can be complementary used.
>    This document also presents the design and protocol procedure for
>    those combinations in addition to the respective stand-alone
>    solutions.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat