Skip to content

Commit c43c771

Browse files
committed
Fix grammar and add clarification.
1 parent 64dfdcb commit c43c771

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2025-04-04-quic-china.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ Therefore, this encryption does not protect confidentiality; still, censors need
8181
QUIC's choice of UDP over TCP also affects how censors deal with QUIC.
8282
For TCP-based protocols, censors can inject TCP Reset packets to the peers to tear down connections.
8383
In UDP, there is no generic connection close mechanism.
84-
Instead, censors may need to drop packets to stop or tear down active QUIC connections&nbsp;<d-cite key="rfc9000,elmenhorst_QuickLookQUIC_2022"/>.
84+
Instead, it has been suggested that censors may need to drop packets to stop or tear down active QUIC connections&nbsp;<d-cite key="rfc9000,elmenhorst_QuickLookQUIC_2022"/>.
8585

8686
QUIC can be used as a transport for different protocols, most notably HTTP/3.
8787
Before attempting to connect via HTTP/3 over QUIC, browsers determine whether the destination supports QUIC.
@@ -231,7 +231,7 @@ It takes a moment for residual censorship to start---usually less than 500ms.
231231

232232
#### 4-Tuple Residual Censorship with Additional Ports
233233

234-
In 37% of connection attempts, follow-up packets dropped on the 4-tuple of the trigger packet, but not on the complete 3-tuple.
234+
In 37% of connection attempts, follow-up packets were dropped on the 4-tuple of the trigger packet, but not on the complete 3-tuple.
235235
In this case, the time frame is also 3 minutes. After the time frame, packet loss returns to normal.
236236

237237
Besides 4-tuple residual censorship, we observed unusual behavior in this case:

0 commit comments

Comments
 (0)