Re:HTTP/3 spin bit [pdf]
by KaiserPro on Tuesday September 17, 2019 @05:07AM
(#20993113)
But each packet is numbered, why can't one use the ACK of the numbered packet instead?
[ Parent
| on HN ]
Re:HTTP/3 spin bit [pdf]
by tialaramex on Tuesday September 17, 2019 @06:56AM
(#20993592)
You understand this is an encrypted protocol right?
A router or other node in the network that's just moving these packets can't decrypt them, so it can't tell the "ACK of the numbered packet". The spin bit lets such a node estimate the round trip time anyway because it will "spin" between set and unset on each round trip.
Re:HTTP/3 spin bit [pdf]
by SellingMyself on Tuesday September 17, 2019 @07:18AM
(#20993696)
Why does an intermediate node (ie. not the endpoint) need to know the RTT?
Re:HTTP/3 spin bit [pdf]
by tialaramex on Tuesday September 17, 2019 @07:46AM
(#20993845)
Troubleshooting seems to be an especially popular reason to want this, but I understand some traffic management strategies want to measure RTT also under normal use.
I was thinking the same thing, though maybe QUIC doesn't send acknowledgements on every packet?
I think you get this information for free as part of TCP.
That's the answer, almost all of QUIC is encrypted for privacy and protection against meddling middleboxes and protocol evolution. ACKs can be done in many ways which should enough reason for them to be protected so middleboxes doesn't stop protocol evolution.