Liaison statement
Response to "LS on ATSSS Phase 2 Requirements to IETF QUIC Working Group"

Additional information about IETF liaison relationships is available on the IETF webpage and the Internet Architecture Board liaison webpage.
State Posted
Submitted Date 2020-10-11
From Group quic
From Contact Lars Eggert
To Group 3GPP-TSGSA-SA2
To Contacts georg.mayer.huawei@gmx.com
3GPPLiaison@etsi.org
Cc Magnus Westerlund <magnus.westerlund@ericsson.com>
Lars Eggert <lars@eggert.org>
QUIC Discussion List <quic@ietf.org>
Mark Nottingham <mnot@mnot.net>
Lucas Pardue <lucaspardue.24.7@gmail.com>
Martin Duke <martin.h.duke@gmail.com>
Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Response Contact Mark Nottingham <mnot@mnot.net>
Lars Eggert <lars@eggert.org>
Lucas Pardue <lucaspardue.24.7@gmail.com>
Purpose In response
Attachments (None)
Liaisons referred by this one LS on ATSSS Phase 2 Requirements to IETF QUIC Working Group
Body 
Thank you for the update on your progress and your questions. Please find our
responses below.

On Qn-1: The future of multipath support for QUIC is currently under active
discussion in the IETF QUIC working group. While it was part of the original
charter due to being under active investigation for the pre-IETF "Google QUIC"
protocol, several participants have argued during the last year that QUIC's
connection migration support is sufficient for the majority of our use cases,
and that full-blown support for multipath QUIC should consequently be abandoned
as a WG deliverable. Other WG participants remain of the opinion that multipath
support for QUIC is very important. Due to this active ongoing discussion, we do
not have an estimate at this time whether WG drafts for multipath QUIC will be
available in 1Q2021.

On Qn-2: The QUIC WG is chartered to provide an encrypted transport protocol.
An option to disable encryption will hence not be standardized.

Kind regards,
Mark Nottingham, Lucas Pardue and Lars Eggert, QUIC Working Group chairs