F25-MQ: Yes

Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Historical wake-traffic inventory (cutoff retired)

Rationale

A bounded fresh mutually authenticated QUIC/TLS1.3 exchange plus multipath-21 setup fits the F25 budget with two validated paths. Reserve 16 crypto/handshake datagrams, eight CID/path-control datagrams, four proactively duplicated STREAM datagrams, two closes and four extra padded Initial ACK datagrams, each with UDP payload up to 1,232 bytes. Add 28 small ACK/PATH_ACK-only datagrams and eight ARP frames across both access interfaces. Including IPv4/UDP and Ethernet overhead, the total is at most 50,236 byte-times. Mandatory 1,200-byte Initial/path-probe padding is included. This retained positive witness uses IPv4 only; the exact total is not an IPv6 overhead calculation.

Assessment method

Constructive documentary two-path byte envelope

Source context

QUIC transport/TLS and selected multipath-21 formats

Outstanding qualification

Compact local certificate chains <=2,048 bytes, bounded Hello/transport parameters, two paths, CID <=20 bytes, single-range ACKs and no loss, Retry, version negotiation, ticket/resumption, 0-RTT or key update. Additional Initial-ACK padding is explicitly budgeted; the small-ACK bound does not apply to Initial packets requiring padding. Configure timely acknowledgments and no unrelated PING/rotation/traffic before delivery. Optional proactive copies are counted on both paths. This is one allowed TLS-suite/packetization witness, not a change to K01 or a general certificate/profile bound. No runtime, congestion, energy or interoperability qualification.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

round320-budget.json
round320-sources.json