Re: [quicwg/base-drafts] Clean up text on Maximum Table Size. (#2115)

[Bence Béky <[e-mail]>]

bencebeky commented on this pull request.



> @@ -768,9 +781,7 @@ end of a stream, it generates a Stream Cancellation instruction on the decoder
 stream.  Similarly, when an endpoint abandons reading of a stream it needs to
 signal this using the Stream Cancellation instruction.  This signals to the
 encoder that all references to the dynamic table on that stream are no longer
-outstanding.  A decoder with a maximum dynamic table size equal to zero (see

I think there is a race here for 0-RTT connections.  Assume the remembered value for SETTINGS_MAXIMUM_DYNAMIC_TABLE_CAPACITY is non-zero.  An endpoint can send a SETTINGS frame with zero SETTINGS_MAXIMUM_DYNAMIC_TABLE_CAPACITY, then send a request and cancel it.  Since the decoder's maximum dynamic table capacity is zero, it does not have to send a Stream Cancellation.  However, the peer might receive the request and send a response using the remembered value of SETTINGS_MAXIMUM_DYNAMIC_TABLE_CAPACITY, inserting entries to the dynamic table.  Those references will never be cleared.

This isssue is intertwined with the one above on the initial value of maximum table capacity on 0-RTT connections.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2115#pullrequestreview-186160080