search

moq-wg / moq-transport

draft-ietf-moq-transport
Other
79 stars 18 forks source link

Remove MAX_SUBSCRIBE_ID parameter #511

Open vasilvv opened 2 weeks ago

vasilvv commented 2 weeks ago

It is 100% redundant, since one can just send a MAX_SUBSCRIBE_ID control message immediately after the SETUP.

ianswett commented 2 weeks ago

I have no strong opinion on this, what do others think?

QUIC has a transport param for max streams, WebTransport does not as two different examples. Both appear to work well.

vasilvv commented 2 weeks ago

QUIC needs it to be a transport param in the ClientHello, because otherwise it would have to wait one RTT to send client's MAX_STREAMS.

ianswett commented 2 weeks ago

That brings up the question of how 0-RTT works with MoQ. If the client is the subscriber and one was using MoQ over raw QUIC, it could remember the values from the previous MoQ session similar to how we remember SETTINGs in HTTP/3 if we wanted to?

That would allow a complete 0-RTT SUBSCRIBE, if we want that. We can also think about this more later when we're trying to optimize the handshake latency.