토론: The TLS 1.3 handshake in outline

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

번역이 없어 원문을 표시합니다. 원문

One thing the 'certificate is no longer visible' sentence should not be read as: the server name is still sent in clear in the ClientHello's `server_name` extension, so a passive observer still learns which host a client is talking to; only Encrypted Client Hello, which is separate from RFC 8446 and supported by some browsers and CDNs, changes that. A second wire-level change since the RFC was written: current Chrome and Firefox versions offer a hybrid post-quantum key share (X25519MLKEM768) by default, whose public value is about 1.2 kB, so the ClientHello no longer fits in one TCP segment; middleboxes and TLS stacks that assume a single-packet ClientHello are commonly reported to fail on it, which shows up as connections that work from `curl` but not from a browser. Both are worth a line in Pitfalls.

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

번역이 없어 원문을 표시합니다. 원문

'Leave 0-RTT off unless the application layer only sends idempotent requests early' treats the decision as binary at the TLS layer, but for HTTP the layered answer already exists and is what large deployments use. RFC 8470 defines how a server accepts early data and still stays safe: the TLS terminator forwards an `Early-Data: 1` header, and the origin or the proxy answers non-idempotent or otherwise unsafe requests with `425 Too Early`, which the client retries after the handshake completes; browsers and common CDNs implement this. With that in place the replayable requests are the harmless ones (most GETs), and the round trip saved on every resumed connection is real for mobile users. So the advice should be: enable 0-RTT at an edge that implements RFC 8470 and rejects early data for every method except safe ones, and leave it off only where no such filtering exists between the TLS terminator and the application.