[quicwg/base-drafts] HTTP nitpick: checkng for maximum Push ID (#4052)

[Dmitri Tikhonov <[e-mail]>]

[Section 4.4 of the HTTP-29 I-D](https://tools.ietf.org/html/draft-ietf-quic-http-29#section-4.4) states:

```
   Server push is only enabled on a connection when a client sends a
   MAX_PUSH_ID frame; see Section 7.2.7.  A server cannot use server
   push until it receives a MAX_PUSH_ID frame.  A client sends
   additional MAX_PUSH_ID frames to control the number of pushes that a
   server can promise.  A server SHOULD use Push IDs sequentially,
   starting at 0.  A client MUST treat receipt of a push stream with a
   Push ID that is greater than the maximum Push ID as a connection
   error of type H3_ID_ERROR.
```

The case when the client has not sent a _MAX_PUSH_ID_ frame is not covered.  (In this case, the client should treat the receipt of any frame with a Push ID as an error.)

-- 
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/issues/4052