Condsider adding an HTTP/3 column

[LPardue]

There is an HTTP/2 column and since people are making progress on IETF QUIC & HTTP/3 interoperability it seems it might be useful to add an HTTP/3 column.

There is an argument to be made for a QUIC column too but that will likely proliferate to needing to disambiguate between gQUIC and IETF QUIC. So for simplicity sake I'd recommend not presenting that.

[igrigorik]

Agreed, adding H/3 columns makes sense to me. Willing to pull together a PR? I guess the tricky bit here would be to (ideally) canvas and gather current state on our own, prior to publishing — not a strict blocker though.

[LPardue]

Let me take a crack...

[LPardue]

It should probably be a WIP PR until such a time as HTTP/3 is finalized - then it can reflect whether an implementation has mainline support for the singular RFC version.

[igrigorik]

👍

…

On Mon, Jan 6, 2020, 7:48 AM Lucas Pardue ***@***.***> wrote: It should probably be a WIP PR until such a time as HTTP/3 is finalized - then it can reflect whether an implementation has mainline support for the singular RFC version. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#203?email_source=notifications&email_token=AAACTHBA3VHSJRNXFLTMYVDQ4NHGVA5CNFSM4KDEXMO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIF26BA#issuecomment-571191044>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAACTHEPJJQCOT4R4EEPOCLQ4NHGVANCNFSM4KDEXMOQ> .

[tunetheweb]

I literally came here to suggest (and/or do) this! Great minds think alike @LPardue 😀