SVCB and HTTPS record types are the new DNS records on the block, acting as a dual purpose redirector and all-in-one record type. SVCB is the generic one, while HTTPS is dedicated to the https protocol.
I wanted to try it out on my self hosted setup,
so I turned on the seeting in chrome
chrome://flags/#use-dns-https-svcb-alpn,
set alpn
to http/1.1,h2,
and promptly discovered nothing changed.
Upon closer inspection, I think the chrome flag only uses it for HTTP3 and not HTTP2, which is an issue, since I'm testing it with envoyproxy/gateway, and implementation of Gateway API, and that doesn't yet (transparently) support HTTP3, even if envoy itself does.