Re: Re: [Fwd: New Liaison Statement, "LS on need for Multi-Path QU IC for ATSSS"]

[Qing An <[e-mail]>]

>We can leverage all the work done with MPTCP. QUIC simplifies the problem because we do not need to take care of any kind of middlebox interference. Many research papers have tried to maximise >throughput because this fits well in lab environments, but deployments have different objectives :
>- on smartphones, deployments try to minimise the utilisation of the cellular network when the Wi-Fi is good enough (with different definitions of good enough depending on the application)
>- in hybrid access networks that combine xDSL and 4G, deployments try to only use the 4G network when the DSL is full  
>
>These objectives are reached by using packet schedulers and path managers that are specific to each use case but have not been standardised within the IETF. Concerning the packet schedulers, we >started to document them in a generic manner in 
>https://tools.ietf.org/html/draft-bonaventure-iccrg-schedulers-00
>and planned to present the draft in Vancouver

https://datatracker.ietf.org/doc/draft-an-multipath-quic-traffic-distribution/ describes several key components for Multipath QUIC traffic distribution. 


            >>This sort of general purpose usage is the most difficult without having a good set assumptions backing the work.
            >>If this is truly desirable, I would suggest that some of those companies listed as supporting the liaison statement could send some people to feed in requirements, refine the scope, make 
            >>proposals, and work on solutions.  The IETF is unlikely to magically create something that will meet 3GPP needs and the speed of interaction via liaison statement isn't conducive to working 
            >>through this.

>I’m ready to work on such a document. Feel free to contact me if you’d like to participate.
I'd like to participate and co-work on this document. 


Qing