*sigh* despite repeated requests to simply add any negotiation to allow using this with  <https://xmpp.org/extensions/xep-0467.html> which is already long deployed and has different still valid use-cases, this instead doesn't and hi-jacks ALPN values and SRV records. I certainly hope it won't be approved this way, it would be the equivalent of accepting a new XEP using an existing one's namespace, and why?

This problem can be trivially solved any number of ways, the simplest which prevents using both on the same QUIC connection would be just picking new ALPN values. I personally think it'd be cleaner to negotiate this using stream features instead so eg I can log into multiple accounts (c2s) or have traffic from multiple domains (s2s) go over the same QUIC connection.

If that is solved, then there are other problems with the spec that could be solved after assigning a number. Namely:
1. mentioning web transport without any way to discover/use
2. adding yet more discovery methods when <https://xmpp.org/extensions/xep-0487.html> would allow discovery of this along with the others and also work with web clients and webtransport