Re: What to do about multipath in QUIC
Mirja Kuehlewind <mirja.kuehlewind@ericsson.com> Thu, 12 November 2020 20:17 UTC
Return-Path: <mirja.kuehlewind@ericsson.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 204A33A047D for <quic@ietfa.amsl.com>; Thu, 12 Nov 2020 12:17:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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=ericsson.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 lb4xpROKKuIK for <quic@ietfa.amsl.com>; Thu, 12 Nov 2020 12:17:15 -0800 (PST)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on2080.outbound.protection.outlook.com [40.107.21.80]) (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 F24613A046A for <quic@ietf.org>; Thu, 12 Nov 2020 12:17:14 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Lry9H0UD/YzK5gfFS2fs+PebNHAQGwNra/l9A5UzoqkyOnA1oWJKHiLYohx7xiGkVztX3RKpxYYEO2osMhh1gXHG2eB9KhCLXpfNNcXBi2jZytIHjtLLX62J9Q4y/chfUYjdTaN/vOldShUigPrvQr54G1Tzo6Hb8r0Of7QckZkD+FjqeuUijvNgNuA2ps3L7nbsltx2C7ywOWyZjtKIG7TRTlabapmbr/W6EoF2wxabG+endhr0zsx6W7hsStfLbYNUnV4oOYmNthyO1pRSD/wY/0urYxoSmUr1YOm8mq8cp9dX9di3Gqtt/RM541HsE8wkF3pwWosxNpCzp6m5WA==
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=DS0xu13QjE/oFez1UdlpbbVtFo37/IbWnPZ3OX7kZww=; b=NKpugrD7bpc0UvLg+jUr+kKFdkA8KmnLesJuQiBEt+geJq/++HvZmlLzJWImHozopRw5bUTZWWZwDzu9vspWLuut3jyldQNb3uWcZjZaunYBV1P+24V8zGOTUJT9FijbsfurkOhcEpxHIa2toe8w/FtmD8NrNz7HMqFFLU0F9BlWiccRlcxOfkOP7bGraxaAxSDJjRPk90N8Y+i0Q0fvV2sp/T06mm4fWQ+8bkJ3WgNFdMbN1bMVJYauXTBAoJf07Piwuu43S7QrZUJBlQJLegAcmnphMEIVrdPggtjuO3KwkJwrlY/rGy4xJGQZzsCIc63AHVjCTBcuP2GjesKP2A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DS0xu13QjE/oFez1UdlpbbVtFo37/IbWnPZ3OX7kZww=; b=M25EgwxpaHII0T0t3HY7XEIvrV+74BnAgusd/Kx+CDa+FwPvXc0IMAbUhuc4MVwCXgpYbAxqgX8LQ1ue2Rpwz8cnWl45WDPLdDdt+CdYqYC5kIAy6FyT73RVXg6MFwrJ1n6RO5RND+BsPs1nm2+6S1Mgo5LNqxkfm9gBDpVNIgQ=
Received: from AM0PR07MB3939.eurprd07.prod.outlook.com (2603:10a6:208:40::14) by AM9PR07MB7681.eurprd07.prod.outlook.com (2603:10a6:20b:2c2::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3564.14; Thu, 12 Nov 2020 20:17:12 +0000
Received: from AM0PR07MB3939.eurprd07.prod.outlook.com ([fe80::50e6:68f7:3047:3cf0]) by AM0PR07MB3939.eurprd07.prod.outlook.com ([fe80::50e6:68f7:3047:3cf0%3]) with mapi id 15.20.3564.024; Thu, 12 Nov 2020 20:17:12 +0000
From: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
CC: Christian Huitema <huitema@huitema.net>, "Ma, Yunfei" <yunfei.ma@alibaba-inc.com>, "Liu, Hongqiang(洪强)" <hongqiang.liu@alibaba-inc.com>, healing4d <healing4d@gmail.com>, Yanmei Liu <miaoji.lym@alibaba-inc.com>, Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, quic <quic@ietf.org>, "安勍(莳逸)" <anqing.aq@alibaba-inc.com>
Subject: Re: What to do about multipath in QUIC
Thread-Topic: What to do about multipath in QUIC
Thread-Index: AQHWuOFoz6occovgqEO/gQcOu1mLhqnEVzkAgABisICAABdPgIAAJv2A///1TQCAABMZgA==
Date: Thu, 12 Nov 2020 20:17:12 +0000
Message-ID: <782AA749-A169-4E2B-9BD0-65EB5541444A@ericsson.com>
References: <538215d1-3b9e-4784-920d-03be4c3a503a.miaoji.lym@alibaba-inc.com> <CAN1APddB4JDo281L0USsU7FSiQxRNi-LaB8ZS0a9kLAgeNJwrw@mail.gmail.com> <54510017-fa91-555f-0219-0859d6686b74@huitema.net> <CAKKJt-c-zGGcWTHHUQS52hxhgLAmmWpr6ZuGz2TsmRVUSxQwrw@mail.gmail.com> <F3839CC0-B2A3-4DF6-AA16-E4FDBE450098@ericsson.com> <CAKKJt-d5CxVgmcBQ142VgG5ENgj6X1g3K+nGCprDh34kJGOZKQ@mail.gmail.com>
In-Reply-To: <CAKKJt-d5CxVgmcBQ142VgG5ENgj6X1g3K+nGCprDh34kJGOZKQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.42.20101102
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2003:de:e707:b600:1410:61c1:79aa:d33d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a41a9678-9b57-448f-ca92-08d88747f0b4
x-ms-traffictypediagnostic: AM9PR07MB7681:
x-microsoft-antispam-prvs: <AM9PR07MB7681C52F5C4C408B43C746B5F4E70@AM9PR07MB7681.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: PI6Pe21yFU5aJPjTW29PHOhAdBk2ecasI49oRPDBiXrRkpZ/KMTVt8mg7LmgkvVLBVOeJAuQWKTkzIWYYdSn9dpEkyM/WCl0ddi5+Dt1Ff45ICDCk+/FlA7D/BymfgM6mwuT2l1sjqZcOD0NrBOV73C+hg0bYio8oS9bYox0Q81fve8LohJY69JoED8x2lPgovTUWjcFjfx3ALRvvrJCcxChlqryl5eVVjpwslTTYp+jvhlK9VOXEsMop4BMLepZJwKBm/8R2H0FljvGjJv1N6ncrm6IOrvGiSWydh+BfCtNPcw90pTUweb/COE9XCnMhPVv222rWBYmvMwjtrNexnmnj2diskjGfa4mYMln7URj14DUSDD1jn4z6awU/5pAB7UEUc/5rDtRTaLeuy9u6g==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR07MB3939.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(396003)(376002)(136003)(346002)(366004)(478600001)(2906002)(4326008)(316002)(966005)(2616005)(66946007)(54906003)(66446008)(66556008)(64756008)(86362001)(5660300002)(8936002)(33656002)(8676002)(6506007)(76116006)(53546011)(6512007)(44832011)(166002)(66476007)(6916009)(186003)(6486002)(71200400001)(36756003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: t5YGTkU8e42uUMovNXk5WON2fK7ejf6FFK2aCINGsYJ7l3KpZsB2FobA3l8YG7OWDxFX2SGBzHON4E6iJ5GG7HexBXSgWv/eM2oR2QAhGGmNSThTUQlmDcYjeAS6bc11sowRtbHy+MCahzsRLD4O45zWxuR/Sbh1s74QjcADlhTJ6gF2d6CX7XYvGVu5y7TSIm1Rl5dMVRG7xsF79u/i/Davk68BAWU7x+C0BCRM3LqYEI3KRVP/ccltqvsbo98mnEuMNMO3kYDYBpUkKbf26Py4XN46uiXfYtISoeinUYoZ8UQ9rywg7nN909jFnmeWP0nm9PWSrUKlClYow/X1iC3jvjSyL60glzGOrTtyMEAtvAc95dlm7aOK+k3sgUAkrW8gBz7nETrz75vg+gBNkr71dgOQ6CLHw4JQIRQ3jtkmUZE2vt0RgZrfIbC+lzgDgDb4BygwrWEZ1cRBzB693eZf5AUtaYi7klB9XAUuOsfTgM0iNiuJJaPdE8rhk++cnAGUuBkiI7nBD700CI+qqrYPRw3Kp0KvYbjE1ZR8Wmwq/SRti9XBgRddRNlMqm0UoUuhq+2NHUXERST9IubyuyDBcPjuc2gjzhkcgmN3aS86Cmw+MlS6Gs3NSaInFegvf6Zt5zhdjIFyn6YrIrfMn2DYmCpOpnDNHcC1yK9wdxqVKd3Z0d0JQQa3rfRwJR736yiNhNksmzTQpLsUHYllrA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_782AA749A1694E2B9BD065EB5541444Aericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR07MB3939.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a41a9678-9b57-448f-ca92-08d88747f0b4
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Nov 2020 20:17:12.2343 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: fZXw8koW4KFB4FaPA4d6ad78zfGS1oqpll88j1sLHnsQhqLB1UwE5vIuZqIkOro5wfhy678HaLcxejSPJPhRKlHlO3YrvY6MyqersEYovmk=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM9PR07MB7681
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YA9GmVp0-tkGTxMqs-2Okn7FjGI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2020 20:17:17 -0000
See below. From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Date: Thursday, 12. November 2020 at 21:09 To: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com> Cc: Christian Huitema <huitema@huitema.net>, "Ma, Yunfei" <yunfei.ma@alibaba-inc.com>, "Liu, Hongqiang(洪强)" <hongqiang.liu@alibaba-inc.com>, healing4d <healing4d@gmail.com>, Yanmei Liu <miaoji.lym@alibaba-inc.com>, Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, quic <quic@ietf.org>, "安勍(莳逸)" <anqing.aq@alibaba-inc.com> Subject: Re: What to do about multipath in QUIC Hi, Mirja, On Thu, Nov 12, 2020 at 1:47 PM Mirja Kuehlewind <mirja.kuehlewind@ericsson.com<mailto:mirja.kuehlewind@ericsson.com>> wrote: There is already work on this in ICCRG: https://tools.ietf.org/html/draft-bonaventure-iccrg-schedulers-00 Right, and the datatracker shows there's a -01. I know the authors are still active on it as well. My goal was to characterize what's being talked about in the QUIC context, but the two efforts are definitely related, and will need to connect at an appropriate time. They are definitely more than connected as the question about scheduling and the respective interface to the higher layer is really independent of any questions on how multipath support is signaled and realized on the wire. So any experience we have from MPTCP on scheduling is directly applicable to any other multipath capable protocol as well. That’s also why ICCRG is a good place to discuss these things. Mirja I'm assuming that Jana will tell me when that time is, since he's chairing ICCRG :-) Best, Spencer
- What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Martin Duke
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Jana Iyengar
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Behcet Sarikaya
- Re: What to do about multipath in QUIC Lucas Pardue
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Lucas Pardue
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Christian Huitema
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Behcet Sarikaya
- Re: What to do about multipath in QUIC Lucas Pardue
- Re: What to do about multipath in QUIC Behcet Sarikaya
- Re: What to do about multipath in QUIC Olivier Bonaventure
- Re: What to do about multipath in QUIC Behcet Sarikaya
- Re: What to do about multipath in QUIC Lucas Pardue
- Re: What to do about multipath in QUIC Behcet Sarikaya
- Re: What to do about multipath in QUIC Roberto Peon
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Kazuho Oku
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Lars Eggert
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Lars Eggert
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Roberto Peon
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Martin Thomson
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Yanmei Liu
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Terminology for multipath QUIC (was Re: What to d… Lucas Pardue
- Re: Terminology for multipath QUIC (was Re: What … Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Christian Huitema
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Mirja Kuehlewind
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Re: What to do about multipath in QUIC Mirja Kuehlewind
- Re: What to do about multipath in QUIC Behcet Sarikaya
- Re: What to do about multipath in QUIC Yanmei Liu
- Re: What to do about multipath in QUIC Kazuho Oku
- Re: Re: What to do about multipath in QUIC Ma, Yunfei
- Re: What to do about multipath in QUIC Yunfei Ma
- Re: What to do about multipath in QUIC Kazuho Oku
- Re: What to do about multipath in QUIC Florentin Rochet
- Re: What to do about multipath in QUIC Christian Huitema
- Re: What to do about multipath in QUIC Kazuho Oku
- Re: What to do about multipath in QUIC Christian Huitema
- Re: What to do about multipath in QUIC Kazuho Oku
- Re: What to do about multipath in QUIC Christian Huitema
- Re: What to do about multipath in QUIC Kazuho Oku
- Re: What to do about multipath in QUIC Christian Huitema
- Re: What to do about multipath in QUIC Kazuho Oku
- Re: What to do about multipath in QUIC Christian Huitema
- Re: What to do about multipath in QUIC Spencer Dawkins at IETF
- Packet number spaces in multipath (was Re: What t… Jana Iyengar
- RE: Packet number spaces in multipath (was Re: Wh… Markus.Amend
- Re: Packet number spaces in multipath (was Re: Wh… Christian Huitema
- RE: Packet number spaces in multipath (was Re: Wh… Markus.Amend
- RE: Packet number spaces in multipath (was Re: Wh… Mikkel Fahnøe Jørgensen
- RE: Packet number spaces in multipath (was Re: Wh… Mikkel Fahnøe Jørgensen
- Re: Packet number spaces in multipath (was Re: Wh… Roberto Peon
- RE: Packet number spaces in multipath (was Re: Wh… Markus.Amend
- Re: Packet number spaces in multipath (was Re: Wh… Mirja Kuehlewind
- Re: Packet number spaces in multipath (was Re: Wh… Jana Iyengar
- Re: Packet number spaces in multipath (was Re: Wh… Quentin De Coninck
- Re: Packet number spaces in multipath (was Re: Wh… Mikkel Fahnøe Jørgensen
- Re: Packet number spaces in multipath (was Re: Wh… Kazuho Oku
- Re: Packet number spaces in multipath (was Re: Wh… Quentin De Coninck
- Re: Packet number spaces in multipath (was Re: Wh… Martin Thomson
- Re: Packet number spaces in multipath (was Re: Wh… Kazuho Oku
- RE: Packet number spaces in multipath (was Re: Wh… Mike Bishop
- Re: What to do about multipath in QUIC Yanmei Liu
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen
- Re: What to do about multipath in QUIC Christian Huitema
- Re: What to do about multipath in QUIC Mikkel Fahnøe Jørgensen