Check: HTTP/3 and protocol selection

Knowledge check · self-test
Check: HTTP/3 and protocol selection
Review setup energy, stream loss, and device and network constraints.
Review setup energy, stream loss, and device and network constraints.
Checkpoint: mobile HTTP/3 {.depth-l0}
You now know:
- QUIC 0-RTT lets resumed HTTP/3 sessions send encrypted data immediately instead of waiting through the TCP and TLS setup path.
- With 96 wakes per day, 100 ms RTT, 300mA radio draw, and 3.7V supply, the chapter's arithmetic reduces connection overhead from 37.3J/day to 10.7J/day.
- Independent QUIC streams keep telemetry moving when a firmware stream waits for retransmission.
:::::: {.callout-tip}
##
Checkpoint: selection constraints {.depth-l0}
You now know:
- Under ~32 KB RAM the practical answer is usually CoAP or MQTT; 32–128 KB typically fits HTTP/2 gateways; >128 KB leaves room for HTTP/3 on mobile or lossy links — rules of thumb; check your library.
- Verify the actual secured stack, buffers and stream count on the target hardware.
- UDP blocking turns an otherwise attractive HTTP/3 design back into an HTTP/2-over-TCP deployment.
:::Back to Modern HTTP: HTTP/2, HTTP/3, and Selection: Back to HTTP/2 and HTTP/3