That's my fault. Should have checked in advance, copied values from the
old Ali-Baba draft instead. I will do a pass with my colleagues at
Ali-Baba to fix this class of issues.
-- Christian Huitema
On 12/13/2020 12:41 PM, Lucas Pardue wrote:
Hi Christian,
Thanks for sharing this work. I note that the I-D proposes a Transport
Paramater of 0x40 but this collides with an existing entry listed on
https://github.com/quicwg/base-drafts/wiki/Temporary-IANA-Registry
<https://github.com/quicwg/base-drafts/wiki/Temporary-IANA-Registry>
Is that intentional? I think its worth a bit of coordination ahead of
experimention (either ongoing or planned) to make sure the different
multipath deployments don't adversely affect each other.
Cheers
Lucas
On Sun, 13 Dec 2020, 19:46 Spencer Dawkins at IETF,
<[email protected] <mailto:[email protected]>>
wrote:
Hi, Christian,
On Fri, Dec 11, 2020 at 1:47 PM Christian Huitema
<[email protected] <mailto:[email protected]>> wrote:
I have been working with Yanmei Liu , Yunfei Ma, Zhenyu Li and
Qing An on this new draft, which merges input from the
multipath experience of Ali-Baba and design suggestions on
this list and in private conversations. One key design choice
is to re-use as much as possible the mechanisms of connection
migration of QUIC-v1.
This is excellent news! One question below.
-- Christian Huitema
-------- Forwarded Message --------
Subject: New Version Notification for
draft-liu-multipath-quic-00.txt
Date: Fri, 11 Dec 2020 11:26:20 -0800
From: [email protected] <mailto:[email protected]>
To: Christian Huitema <[email protected]>
<mailto:[email protected]>, Zhenyu Li <[email protected]>
<mailto:[email protected]>, Yunfei Ma <[email protected]>
<mailto:[email protected]>, Yanmei Liu
<[email protected]>
<mailto:[email protected]>, Qing An
<[email protected]> <mailto:[email protected]>
A new version of I-D, draft-liu-multipath-quic-00.txt
has been successfully submitted by Yanmei Liu and posted to the
IETF repository.
Name: draft-liu-multipath-quic
Revision: 00
Title: Multipath Extension for QUIC
Document date: 2020-12-11
Group: Individual Submission
Pages: 22
URL:
https://www.ietf.org/archive/id/draft-liu-multipath-quic-00.txt
<https://www.ietf.org/archive/id/draft-liu-multipath-quic-00.txt>
Status:
https://datatracker.ietf.org/doc/draft-liu-multipath-quic/
<https://datatracker.ietf.org/doc/draft-liu-multipath-quic/>
Html:
https://www.ietf.org/archive/id/draft-liu-multipath-quic-00.html
<https://www.ietf.org/archive/id/draft-liu-multipath-quic-00.html>
Htmlized:
https://tools.ietf.org/html/draft-liu-multipath-quic-00
<https://tools.ietf.org/html/draft-liu-multipath-quic-00>
Abstract:
This document specifies multipath extension for the QUIC
protocol to
enable the simultaneous usage of multiple paths for a single
connection. The extension is compliant with the single-path QUIC
design. The design principle is to support multipath by adding
limited extension to [QUIC-TRANSPORT].
Discussion Venues
This note is to be removed before publishing as an RFC.
Source for this draft and an issue tracker can be found at
https://github.com/yfmascgy/Multipath-QUIC-IETF-Draft
<https://github.com/yfmascgy/Multipath-QUIC-IETF-Draft>.
I talked with the Alibaba team about putting their work in Github,
and they were agreeable, but I'm getting a 404 on this URL. Do you
folks know when it will be created?
Best,
Spencer
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 <http://tools.ietf.org>.
The IETF Secretariat
