Multipath QUIC for Vehicle Communications
Yunfei Ma <yfmascgy@gmail.com> Tue, 15 August 2023 04:34 UTC
Return-Path: <yfmascgy@gmail.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 4EB5BC15106E for <quic@ietfa.amsl.com>; Mon, 14 Aug 2023 21:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IQC-3eKzrEFB for <quic@ietfa.amsl.com>; Mon, 14 Aug 2023 21:34:22 -0700 (PDT)
Received: from mail-oa1-x2c.google.com (mail-oa1-x2c.google.com [IPv6:2001:4860:4864:20::2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 028D9C15153D for <quic@ietf.org>; Mon, 14 Aug 2023 21:34:21 -0700 (PDT)
Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-1a28de15c8aso3914139fac.2 for <quic@ietf.org>; Mon, 14 Aug 2023 21:34:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692074061; x=1692678861; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=TPrzWZ0W9LB2MKgC31n7sy46rSCgW64l823tyDtGbTA=; b=HhVuACbKU+/1TOnlr0QJ8VvR12ztIpE+DK/3cJSCeAhKI4RQ6RTCIXzhT4t1VJ+YxF 7lORY47QmM3cWsJGz2qjy49RUkgOmLXb/DlX9qLKdo1lUT9YGRKkX6UlzQh8E+h9XPhu EcLFWFxTW88JzmaUZW9ee5yiufbVS6XxMQYrGyrj84p9w/oodRvuSrXcqAsThhmMa30I n7J4EmeKyVhOQchy8x1rhD9x8SUA45GRPSZKDMqoReUOFHfZFYYg1Fad+dTux44nilFC C3uPfIjn6/baf8WTOpVoTFjnLWPbM7tRmdgMZSEJ81VlP/TaLL1fY4ylni6M2oGEIw+s 4Zbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692074061; x=1692678861; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=TPrzWZ0W9LB2MKgC31n7sy46rSCgW64l823tyDtGbTA=; b=DstbX+KT8TD4kRSf/PwIuUlLSVVbwOgf4vZU/e6a/BPox1/Tqa2s+pD/T06v1xGVSA JqRCen9LKDPqmwYMBe/tToNyV4zucwIN8MJyuAjWSos+wppsVHMTnN70ebipefIvGQU9 p0Ca7A1bsDVtoJQ89sHGD+JdOv/8LWj1qiijowTCfytRRUpo8zWlNrpCAe3J4sH6WEZt wxL7AeX8Qv+N/IeCDnujPA3xgw8syhdkHKxjDUExR3Qle43fBsaB7iVoeXHzirLNDOwN 6mZmug9AbRe0o8RJwPlxpVxulUwrnVHcLJmpcmNpsOWltKvXULgfaxrkeB0nyIR5LDyA U0Zw==
X-Gm-Message-State: AOJu0Yxve82NNg0fvL5Vl6fGm1kkiwol0ZZU1AizuYfCKFy+7HXY+DQa yxNSvhE9julNhe5xz+rZOW4TaTtgj67bl5Bg6dCj1UZTA/ESyQ==
X-Google-Smtp-Source: AGHT+IEMw+7koormWAX/HszE/PV+YGcH2qh80i3seq8nv27nwnqrWut5iTveXJekXdYOSaUqTLFt7JTgghxMC/SCam8=
X-Received: by 2002:a05:6870:424b:b0:1b0:17f2:6518 with SMTP id v11-20020a056870424b00b001b017f26518mr12654323oac.42.1692074057330; Mon, 14 Aug 2023 21:34:17 -0700 (PDT)
MIME-Version: 1.0
From: Yunfei Ma <yfmascgy@gmail.com>
Date: Mon, 14 Aug 2023 21:33:39 -0700
Message-ID: <CAHgerOFqb+QXYzyi9W7NSO-mSGjeUGwHxZw_2g3WGr+pMpwzEA@mail.gmail.com>
Subject: Multipath QUIC for Vehicle Communications
To: QUIC <quic@ietf.org>
Content-Type: multipart/mixed; boundary="00000000000021d5e90602eeb1aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8hGsdilfSVlggu3uexNjRXy0we4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 15 Aug 2023 04:34:37 -0000
Hello Multipath QUIC Enthusiasts, Hope this finds you well! We've completed our experiment on using multipath QUIC to boost vehicle communications. If this sounds up your alley, do take a moment to go through our SIGCOMM’23 paper attached. As we see more electric and autonomous cars on the roads, it's becoming a bit like having smartphones on wheels out there. Getting these vehicles reliably connected to the internet is a challenge we're taking head-on. Our exploration with multipath QUIC is showing promise in making those connections smoother. Enter "CellFusion". It's our solution to fuse together four cellular networks into one solid cloud connection. After testing this setup with self-driving cars for over six months, we're pretty optimistic about the results! We've based our work on the foundational principles from the multipath QUIC draft and the QUIC Datagram draft. A big thank you to the IETF QUIC working group for setting the stage. Here's what we gleaned from our work with CellFusion: - Multipath QUIC might just be the game-changer for vehicle communication. - Going beyond two concurrent paths? Seems like a good idea. - Sustaining longer connections in multipath QUIC is an area worth delving into. - We're also looking at enhancing multipath QUIC with some advanced network coding features. We'll be sharing all about it at SIGCOMM 2023 on Wednesday, Sept. 13th ( https://conferences.sigcomm.org/sigcomm/2023/program.html). They've even got a whole session dedicated to multipath! If you have questions or just want to chat about it, drop me an email or join us for the presentation. Best, Yunfei