IETF Logo Mail Archive

[tsvwg] Time slot request for the new topic around MP-DCCP

<Markus.Amend@telekom.de> Tue, 12 March 2019 11:05 UTC

Return-Path: <Markus.Amend@telekom.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBA0612F19D for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2019 04:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 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, 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 RigN_rqPcYHy for <tsvwg@ietfa.amsl.com>; Tue, 12 Mar 2019 04:05:31 -0700 (PDT)
Received: from mailout11.telekom.de (MAILOUT11.telekom.de [194.25.225.207]) (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 4172F126E5C for <tsvwg@ietf.org>; Tue, 12 Mar 2019 04:05:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1552388731; x=1583924731; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=X9xH1BB3GDLbB2rZJmVVOS3X9mIZdWLZeppJrv8Qp2Q=; b=JkmLtdQqULkx4bdE5rHexWlW/3C8oGLtEL129Y2iY9RHn8l55vd1aBMD RRHIvQnHlvKiW9wFCBpWe3ZqJC/VlbHkX5zoGC70OFdQwod8ZA6LFZOHa uzVAkItkUYoEQW5ZWzdXqYO22/Jdgr3OyL0DF63yu6jTn3ihqddC2NYQ1 OvP6D72SI5hMy5lT+XjWSzrGFA313rIYIQZYrtDZNt14wH1GiiLtaj9Vr BAJgRzv5QeRcvXcUB9araS9D/6H2NlQL08j1q0V+hwv1ZHPLZ2uBABH4O mzW2Lpb6i+sCIGXUYW4LvBN/7yQ/Ej/PXHP7nbnh0SnKA+tkzUx4fPYKG w==;
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by MAILOUT11.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Mar 2019 12:05:27 +0100
X-IronPort-AV: E=Sophos;i="5.58,471,1544482800"; d="scan'208";a="243925501"
Received: from he199745.emea1.cds.t-internal.com ([10.169.119.53]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/AES256-SHA; 12 Mar 2019 12:04:25 +0100
Received: from HE106138.EMEA1.cds.t-internal.com (10.169.119.71) by HE199745.emea1.cds.t-internal.com (10.169.119.53) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 12 Mar 2019 12:04:14 +0100
Received: from HE104162.emea1.cds.t-internal.com (10.171.40.37) by HE106138.EMEA1.cds.t-internal.com (10.169.119.71) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 12 Mar 2019 12:04:13 +0100
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.22) by O365mail04.telekom.de (172.30.0.231) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 12 Mar 2019 12:04:14 +0100
Received: from FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.21) by FRAPR01MB0916.DEUPRD01.PROD.OUTLOOK.DE (10.158.136.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.19; Tue, 12 Mar 2019 11:04:13 +0000
Received: from FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE ([fe80::51bb:6941:3ad1:4a7]) by FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE ([fe80::51bb:6941:3ad1:4a7%5]) with mapi id 15.20.1686.021; Tue, 12 Mar 2019 11:04:13 +0000
From: Markus.Amend@telekom.de
To: tsvwg@ietf.org
Thread-Topic: [tsvwg] Time slot request for the new topic around MP-DCCP
Thread-Index: AdTYwykn83HP7GV0TgqFivwEWqJNtQ==
Date: Tue, 12 Mar 2019 11:04:13 +0000
Message-ID: <FRAPR01MB1170ECD397C0971E40C8A56EFA490@FRAPR01MB1170.DEUPRD01.PROD.OUTLOOK.DE>
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: 8e67dba1-1fb7-4965-84bf-08d6a6da7606
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:FRAPR01MB0916;
x-ms-traffictypediagnostic: FRAPR01MB0916:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <FRAPR01MB0916FE8169FB78CE41D02EBFFA490@FRAPR01MB0916.DEUPRD01.PROD.OUTLOOK.DE>
x-forefront-prvs: 09749A275C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(346002)(376002)(396003)(366004)(136003)(189003)(199004)(102836004)(86362001)(53936002)(476003)(486006)(478600001)(5640700003)(8936002)(1730700003)(9686003)(74482002)(52396003)(33656002)(8676002)(55016002)(6116002)(2501003)(81166006)(6306002)(316002)(3846002)(256004)(68736007)(305945005)(66066001)(75402003)(186003)(7736002)(106356001)(81156014)(6916009)(5660300002)(72206003)(14444005)(2351001)(7696005)(71190400001)(2906002)(26005)(105586002)(71200400001)(14454004)(966005)(413944005)(97736004)(19623455009); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0916; 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-microsoft-exchange-diagnostics: 1; FRAPR01MB0916; 23:i5qmgGzpKfxNmVKGh0698S/teGKVrXOj/Mezm09HcZmaQo6DJbgY6Bn542lzWDlHumdsqBiGLaKYe2IF8B9TXe71U0tjBOBHsnb96PE3NDeR1/7TwgmUr0sKU1Qi1lmyK5pywcE4idUa1fFt6VCxGaBZWoZDwPyIFU8pKfcw8fX2Cw3SIlrpDiv3BdVPzVc4jiy+OtQI+iH6VWH+GAwLcCPYaFJripTzSfI9PsdrAFbAp5L0qmLaMzSymecQh4cRcay8dpl/ErVm0F7AoPX+NLjJSxl83DQqgJ2GpUHkDNZJopdnsfX70dtRJA2eE8UoPxqHq1rn6lNxF02E+3S4W7Ki4/myevzyy4keU9MVJNL4HEYL2fkyFhzTf9w7UOqmxZOKhPU9Y0s0sxIDz7BYO176BrhPagCNK0baSJshyf5XXcvuyQYrjf16BCT8WXiQUrPWJ81mZJgHvbcCRbVIzKwJhvT/+NLfXLc5KMlsW+zieWHQSDiuYTb5y15gNxoptMclTgXvHjiHHRDmuJeu06vKhmN7NUO6dXZb62f1JcqkrJQ1UbNHnRKjCzO/+X2vl8VSAdI9tp/DXwl2ZVEGcTGdJXK9E+ROg5yoxpLIIJ4cB2t02nLUQ0YiwHl8SneTiPQtr40uDm0+EpQcfRy1sT+q923g2ERZT8viA8J2JKOgkD847xsfNvGLC6ix1WaChqcP8c+4XIJ4FsXAIxOpaIbEZjqdMpiQFOMxoZbEnv1NTyDt+RUuruFavLclJFMMRNHtycjYWsGp4wYJZCpMyci4uYwnTidb7EI+sS/SVx5PZv81FC4bD1vOl0bD/IgDMqwaTFwtuyZ7p+8/SwEHmt1/8vWuoJxmBvWmN/WPNZ9F/PmE3w14D7Rufxzh2SZP8hEF2ddGe82yYiwe2hISnjsOKjQRpF8F/tOvWMhdZAeh23PqK7+mvNJ/aJ9mNREpZ1y1wOlJBQSSfCvKlhoBPWWl0MtKYlZ6BIPuOb32YA/49FIJV9W2zFvIZhlMpObUWs2+yZN5z0Gt41D05hPSeh/0lIzysR7/c8iNHwyA5YLC2JZ08M3PyUVROcsFUX6a2TEcoc8fVI4VZ2CPQJ1Zl6ot25iE9rLJyEAT/20kST6wcX6SnGEsfx/Ku6tCb/ExUucC0RGVXc26tTMJ85jmnfm0CCCoBLYhho/9MtgliyLfDp4Q5OFS9chKUZJFD2L6ZbZc9l/am6SQN391T1mMsA==
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 4cN/G3ksA28G6AUnAnZDfkc5JHAYhyriv4+xlTP1cv09LdIKBT56EbkUYhF4c/+SrZAY12GhW3OhTfyud2xnTcQiWiomO46+RwC5fbjLngynr20i0N8Z0aD4qqUwLSrnuyzy25xP+opcZvw39sm9/F1F54byG0RIp0FalvWL8mYZOs9KasBdpDxsWjWbZjI0Sj+dxtH0SnditfZZyhhDJLL/f6jO9XReSDzB3VZ27hrPr/sMwdb5zxqDuTU5Vs5xPUgHQ5XfXbqMVX+J4qr3Ll3QrDeL07NdfH26YHZ3FCzc4W+XogFNxVFLijMY4t6sBQ3jzeypEmvtCvuWWSdGP9+4PD5KGyCF428SmOiMMPKjtKXuTj8iis/NSWS/pW+wI7ZaFi8vMX9i/c9KJoCBClH+LjsEbrQbDk7/kneo2Vs=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8e67dba1-1fb7-4965-84bf-08d6a6da7606
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Mar 2019 11:04:13.1522 (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-Transport-CrossTenantHeadersStamped: FRAPR01MB0916
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/8AwQUiVNugrYlaZ9_mp7HoHqxy8>
Subject: [tsvwg] Time slot request for the new topic around MP-DCCP
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2019 11:05:35 -0000

Dear all,

I want to make you aware about three drafts, submitted recently, for enabling multipath transfer of UDP and IP traffic over multiple data paths. In particular this becomes challenging in heterogeneous networks with volatile path or access characteristics. For that reason it is a hot, respectively a not yet standardized topic in the area of Hybrid Access and also for the ongoing standardization of 3GPP Access Traffic Steering Switching Splitting (ATSSS). Hybrid access defines multi-connectivity for residential scenarios extending a traditional fixed line CPE by cellular access. ATSSS specifies multi-connectivity between a mobile device (UE) and the 5G core over cellular access and Wi-Fi. The specification for the latter can be found at http://www.3gpp.org/ftp//Specs/archive/23_series/23.793/23793-g00.zip and identifies a gap at least for transferring non-TCP traffic over multiple data paths. Since MP-TCP was agreed as an option for splitting TCP traffic within the ATSSS framework, an option for at least UDP or even IP is missing. The same also holds true for Hybrid Access, where MP-TCP is an option but does not cover the increasing share of UDP traffic, which is mainly driven by QUIC. When HTTP/3 over QUIC becomes applied, this could be the point where UDP might overtake the traditional dominating TCP in ISP networks.

In respect to multipath transmission for UDP and IP traffic

https://datatracker.ietf.org/doc/draft-amend-tsvwg-multipath-framework-mpdccp/ 

proposes an IP compatible multipath architecture applicable i.a. for Hybrid Access and ATSSS, based on the MP-DCCP network protocol

https://datatracker.ietf.org/doc/draft-amend-tsvwg-multipath-dccp/

which extends the standardized DCCP protocol by multipath capabilities. MP-DCCP is an appropriate measure for serving services with no reliability demands on transportation (e.g. UDP). However, DCCP feedbacks the path conditions considered required for efficient traffic distribution schemes across volatile paths. Since the DCCP struggles with traversing todays middle-boxes (chicken-egg), U-DCCP in

https://datatracker.ietf.org/doc/draft-amend-tsvwg-dccp-udp-header-conversion/

specifies a lossless and overhead free DCCP to UDP conversion, which is more efficient than traditional encapsulation solutions.


To give you deeper insights in our motivation and the opportunity to discuss our ideas, I want to ask the tsvwg chairs for a time slot in one of the tsvwg sessions at IETF 104.


BR

Markus

v2.23.0 | Report a Bug | By Email