Mercurial > hg > nginx

comparison README @ 8389:2b580ac17a47 quic

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
README: Retry support, protocol error messages implemented.
author Sergey Kandaurov <pluknet@nginx.com>
date Thu, 14 May 2020 16:33:46 +0300
parents 796b5b6c43cd
children 70dbd7d0e466
comparison
equal deleted inserted replaced
8388:a9cc1627cf1c 8389:2b580ac17a47
41 41
42 + The handshake completes successfully 42 + The handshake completes successfully
43 + One endpoint can update keys and its peer responds correctly 43 + One endpoint can update keys and its peer responds correctly
44 + 00-RTT data is being received and acted on 44 + 00-RTT data is being received and acted on
45 + Connection is established using TLS Resume Ticket 45 + Connection is established using TLS Resume Ticket
46 + A handshake that includes a Retry packet completes successfully
46 + Stream data is being exchanged and ACK'ed 47 + Stream data is being exchanged and ACK'ed
47 + An H3 transaction succeeded 48 + An H3 transaction succeeded
48 + One or both endpoints insert entries into dynamic table and 49 + One or both endpoints insert entries into dynamic table and
49 subsequently reference them from header blocks 50 subsequently reference them from header blocks
50 51
51 Not (yet) supported features: 52 Not (yet) supported features:
52 53
53 - Version negotiation 54 - Version negotiation
54 - Stateless Retry
55 - ECN, Congestion control and friends as specified in quic-recovery [5] 55 - ECN, Congestion control and friends as specified in quic-recovery [5]
56 - A connection with the spin bit succeeds and the bit is spinning 56 - A connection with the spin bit succeeds and the bit is spinning
57 - Structured Logging 57 - Structured Logging
58 - QUIC recovery (proper congestion and flow control) 58 - QUIC recovery (proper congestion and flow control)
59 - NAT Rebinding 59 - NAT Rebinding
61 - Server push 61 - Server push
62 - HTTP/3 trailers 62 - HTTP/3 trailers
63 63
64 Since the code is experimental and still under development, 64 Since the code is experimental and still under development,
65 a lot of things may not work as expected, for example: 65 a lot of things may not work as expected, for example:
66
67 - Protocol error messages are not implemented, in case of error connection
68 closes silently for peer
69 66
70 - ACK handling is basic: every received ack-eliciting packet 67 - ACK handling is basic: every received ack-eliciting packet
71 is acknowledged, no ack ranges are used 68 is acknowledged, no ack ranges are used
72 69
73 - Flow control mechanism is basic and intended to avoid CPU hog and make 70 - Flow control mechanism is basic and intended to avoid CPU hog and make