Dear all,


I also support the adoption of the proposed draft into the QUIC WG.  It
represents a good solid basis addressing various use cases.

Thank you.

-Florin Baboescu





*From:* QUIC [mailto:[email protected]] *On Behalf Of *Lucas Pardue
*Sent:* Thursday, January 13, 2022 7:14 AM
*To:* QUIC WG <[email protected]>
*Cc:* QUIC WG Chairs <[email protected]>
*Subject:* Call for adoption: Multipath Extension for QUIC



Greeting QUIC WG members,



During IETF 113 Mirja presented [1] about the unified multipath QUIC
proposal in draft-lmbdhk-quic-multipath [2]. There was a strong feeling in
the room that this draft was a good basis for adoption into the QUIC WG. So
we'd like to start an adoption call.



The adoption call will run for 2 weeks, ending on February 27 2021
(anywhere on earth). Please reply to this email with any comments.



As a reminder, the draft contains two approaches to using packet numbers.
The feeling in the room at IETF 113 was that it is suitable to adopt the
documents in this state and select a single approach as part of the regular
consensus process.



Since this is a draft that unifies different proposals, the chairs are
suggesting that should the WG agree to adopt draft-lmbdhk-quic-multipath,
the current author group be split into three editors (Mirja, Quentin,
Yanmei) and three authors (Chrisian, Olivier, Yunfei).



Kinds regards,

Matt & Lucas

QUIC WG Chairs



[1] -
https://datatracker.ietf.org/doc/slides-112-quic-unified-multipath-quic-extension/

[2] - https://datatracker.ietf.org/doc/draft-lmbdhk-quic-multipath/

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to