Using "connectStart", "secureConnectionStart" and "connectEnd" with HTTP/3 flows about navigation-timing HOT 5 CLOSED

The time connectStart represents is set in Fetch's create a connection.
connectEnd and secureConnectionStart are defined in record connection timing info, slightly less strictly. As such, it's not 100% clear (to me, at least) what they should be for H3.

@noamr - thoughts? Should this issue be migrated to Fetch?

from navigation-timing.

The time connectStart represents is set in Fetch's create a connection. connectEnd and secureConnectionStart are defined in record connection timing info, slightly less strictly. As such, it's not 100% clear (to me, at least) what they should be for H3.

@noamr - thoughts? Should this issue be migrated to Fetch?

The problem is that those measurement points are not defined in Fetch, but rather in the HTTP, TLS & DNS specs (+ other specs in that layer). That's why they're only loosely defined. and they need to be separately defined for each HTTP version etc., which is something that's beyond the scope of Fetch.

from navigation-timing.

Understood. At the same time, I do see that Fetch has some considerations (and flags) indicating H3. Would it be possible to add prose indicating what those values should be for H3?

from navigation-timing.

Understood. At the same time, I do see that Fetch has some considerations (and flags) indicating H3. Would it be possible to add prose indicating what those values should be for H3?

Sure, that's doable.

from navigation-timing.

This got resolved by whatwg/fetch@583986a.

from navigation-timing.