Suggestions for server-timing/

[foolip]

• Add @cvazac and any other interested implementers to OWNERS
• Test invalid production of https://w3c.github.io/server-timing/#the-server-timing-header-field, for example if metric-value starts with a 0. Does any deviation from the ABNF have the same effect? If not, this needs to somehow be accounted for in the spec.
• Test what happens when there are two headers with different values. First wins, last wins, or error?

[cvazac]

I'm trying to land a change to the ABNF which allows for a duration of ".5" (no leading "0").

What invalid production of the header do you have in mind?

[foolip]

A missing leading zero was the first that came to mind, but anything that might plausibly differ in a generated parser and a hand-written one would be good to cover. For example, leading, trailing and extra semicolons, i.e. permutations of "Server-Timing: ;metric1=1.2;;document;"

And names that aren't valid productions of token in https://tools.ietf.org/html/rfc7230

[foolip]

@cvazac I see that you did #13789 last year, does that cover the suggestions in this issue?