F24-MQ: No
Rationale
QUIC max_idle_timeout bounds idle connection lifetime; PING can keep state alive. Neither defines when a sleeping receiver will listen or requires the sender to deliver in known wake opportunities. The selected multipath-21 path-status preferences do not specify a wake schedule; backup-path use may resume when other paths fail.
Assessment method
Primary documentary reassessment; no runtime or energy test
Source context
Selected name-routing and transport/control specifications
Outstanding qualification
This assessment considers the delivery benefit, not only the absence of a negotiation message. No scheduled access binding, coordinating custodian or application wake scheduler is selected. Flow control, retransmission and retained connection state alone do not meet F24. Such services could be added; their absence here is not a claim that QUIC-capable devices cannot sleep.
Public sources
- https://www.rfc-editor.org/rfc/rfc9000.html#section-10.1
- https://www.ietf.org/archive/id/draft-ietf-quic-multipath-21.txt
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round492.html
- round492-sources.json