QUIC: Make sure the some of the quic configs get set into the quiche impl.

[brbzull0]

Just passing them into the quche lib.

ts:
  quic:
    no_activity_timeout_in: 1000
    initial_max_data_in: 60000
    initial_max_stream_data_bidi_local_in: 1000
    initial_max_stream_data_bidi_remote_in: 1000
    initial_max_stream_data_uni_in: 4000

values are advertised correctly:

I00000018 0x65b8963682593300 cry remote transport_parameters initial_max_stream_data_bidi_local=1000
I00000018 0x65b8963682593300 cry remote transport_parameters initial_max_stream_data_bidi_remote=1000
I00000018 0x65b8963682593300 cry remote transport_parameters initial_max_stream_data_uni=4000
I00000018 0x65b8963682593300 cry remote transport_parameters max_idle_timeout=1000
I00000018 0x65b8963682593300 cry remote transport_parameters initial_max_data=60000

curl seems to be getting it:

...
* ngtcp2_conn_handle_expiry returned error: ERR_IDLE_CLOSE
* Connection #0 to host 127.0.0.1 left intact
...

[brbzull0]

@maskit is ts.quic.no_activity_timeout_in the right field to be used for the max_idle_timeout set by quiche_config_set_max_idle_timeout?

[brbzull0]

[approve ci autest]

[maskit]

is ts.quic.no_activity_timeout_in the right field to be used for the max_idle_timeout set by quiche_config_set_max_idle_timeout?

Yes, it is. I'm wondering if the setting should take milliseconds. It's millisecond on the spec but we use seconds for most of ATS settings. proxy.config.http.accept_no_activity_timeout for example.

[brbzull0]

is ts.quic.no_activity_timeout_in the right field to be used for the max_idle_timeout set by quiche_config_set_max_idle_timeout?

Yes, it is. I'm wondering if the setting should take milliseconds. It's millisecond on the spec but we use seconds for most of ATS settings. proxy.config.http.accept_no_activity_timeout for example.

I think we can do something for this, and instead of be tight to a particular unit we can actually support multipliers like we do for other units like M,K,G

so eventually we can say:

ts:
  quic:
    no_activity_timeout_in: 1s

[brbzull0]

[approve ci autest]

[maskit]

Hmm, I like the idea but I'm not sure if that works for timeouts. It's kinda obvious that we cannot set 500 milli-bytes nor 8.3 bytes as a file/buffer size. Its minimum unit is obviously byte. On the other hand, 125 milliseconds can make sense for some timeout, but users don't know the actual internal precision unless the documentation says it.

I found the setting currently takes millisecond. I guess I used the unit which the spec use without thinking about it much. Let's keep this PR simple and think about the unit specifier at somewhere else.

[brbzull0]

Let's keep this PR simple and think about the unit specifier at somewhere else.

sure.
Thanks.

[brbzull0]

[approve ci clang-analyzer]

[SolidWallOfCode]

Thinking about the unit specifier here - #9485