QUIC File Transfer Service, a CLI and srv for transferring large files
1–10 of 20 posts
Re: QUIC File Transfer Service, a CLI and srv for transferring large files
#2The File Transfer Service utilizes the quic-go implementation of the quic Protocol, built on top of UDP. Since quic allows for multiplexing of streams on a single connection, the service takes advantage of this to attempt to speed up file transfers by processing and writing the file from the remote host (the server) to the destination (the client) concurrently
Re: QUIC File Transfer Service, a CLI and srv for transferring large files
#3[deleted]
Re: QUIC File Transfer Service, a CLI and srv for transferring large files
#4Is it time to move QUIC past UDP yet? Does QUIC deserve it's own Protocol number? There's only one byte in IP for protocol number, so it makes sense to limit the number of applications, but I believe QUIC has reached that level.
https://www.iana.org/assignments/protocol-numbers/protocol-n...
Re: QUIC File Transfer Service, a CLI and srv for transferring large files
#5Is it time to move QUIC past UDP yet? Does QUIC deserve it's own Protocol number? There's only one byte in IP for protocol number, so it makes sense to limit the number of applications, but I believe QUIC has reached that level. https://www.iana.org/assignments/protocol-numbers/protocol-n...
Hm. Wikipedia tells me that a UDP headers has 4 parts: Source port, dest port, length, and checksum.
I suppose with a new protocol you could ditch the length and checksum, which (I don't know much about networking) might be redundant with the IP header and with TLS respectively. That would save you 4 bytes per packet. Nothing huge.
The reason it uses UDP is that the Internet is full of middleboxes built 10 years ago that won't get any firmware updates for another 10 years, and those boxes love TCP and we're lucky if they even pass UDP and ICMP packets. Anything else might just get dropped, and then you have to fall back. Is UDP underneath QUIC really hurting much?
Re: QUIC File Transfer Service, a CLI and srv for transferring large files
#6The File Transfer Service utilizes the quic-go implementation of the quic Protocol, built on top of UDP. Since quic allows for multiplexing of streams on a single connection, the service takes advantage of this to attempt to speed up file transfers by processing and writing the file from the remote host (the server) to the destination (the client) concurrently
That's clever. I'd wondered how you can transfer files with "any order, as long as the entire file completes as fast as possible" semantics, that is, without head-of-line blocking, without incurring a lot of overhead. I guess the answer is to use lots of big chunks and lots of streams, instead of lots of tiny packet-sized chunks in 1 stream.
Re: QUIC File Transfer Service, a CLI and srv for transferring large files
#7The File Transfer Service utilizes the quic-go implementation of the quic Protocol, built on top of UDP. Since quic allows for multiplexing of streams on a single connection, the service takes advantage of this to attempt to speed up file transfers by processing and writing the file from the remote host (the server) to the destination (the client) concurrently
That's clever. I'd wondered how you can transfer files with "any order, as long as the entire file completes as fast as possible" semantics, that is, without head-of-line blocking, without incurring a lot of overhead. I guess the answer is to use lots of big chunks and lots of streams, instead of lots of tiny packet-sized chunks in 1 stream.
it's exactly the way torrents have worked for decades, so it's pretty well tested.
Re: QUIC File Transfer Service, a CLI and srv for transferring large files
#8Is it time to move QUIC past UDP yet? Does QUIC deserve it's own Protocol number? There's only one byte in IP for protocol number, so it makes sense to limit the number of applications, but I believe QUIC has reached that level. https://www.iana.org/assignments/protocol-numbers/protocol-n...
I'm under the impression that UDP is what makes QUIC valuable, by keeping it compatible with the world's existing network hardware and firewall configurations.
If that issue didn't exist, SCTP would surely see a lot more use.
Re: QUIC File Transfer Service, a CLI and srv for transferring large files
#9How does QUIC compare to the proprietary Aspera protocol?
Re: QUIC File Transfer Service, a CLI and srv for transferring large files
#10The File Transfer Service utilizes the quic-go implementation of the quic Protocol, built on top of UDP. Since quic allows for multiplexing of streams on a single connection, the service takes advantage of this to attempt to speed up file transfers by processing and writing the file from the remote host (the server) to the destination (the client) concurrently
[deleted]