D382: validate reconnect echo budget with real TLS and modelled TCP handshake #488

Open
opened 2026-11-10 15:23:46 +00:00 by kayg · 0 comments
Owner

Follow-up to D382 and #478, split out of J448c round 2 as requested. Preserve forced-drop to first resumed marker echo painted as the measurement endpoint. Run WSS behind real TLS with TCP handshake latency represented on the shaped link. Update the network-change target, report and docs to the resume budget plus one echo RTT: 5 RTT + 50 ms (1550 ms at nominal 300 ms RTT; 1700 ms at a 330 ms bound). Rerun the required sample count and retain every timeout/failure as FAIL. Existing plain-WS loopback results do not establish this deployment budget. No auth or input-ordering optimization is authorized by this follow-up.

Follow-up to D382 and #478, split out of J448c round 2 as requested. Preserve forced-drop to first resumed marker echo painted as the measurement endpoint. Run WSS behind real TLS with TCP handshake latency represented on the shaped link. Update the network-change target, report and docs to the resume budget plus one echo RTT: 5 RTT + 50 ms (1550 ms at nominal 300 ms RTT; 1700 ms at a 330 ms bound). Rerun the required sample count and retain every timeout/failure as FAIL. Existing plain-WS loopback results do not establish this deployment budget. No auth or input-ordering optimization is authorized by this follow-up.
Sign in to join this conversation.
No labels
launch-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/infraternal#488
No description provided.