I was disappointed to realize that quic-http has two normative references (httpbis-cache and https-semantics) that are not even in WGLC.
This suggests that there will be significant delay (best case, months) between QUIC and HTTP/3 finalizing as RFCs. How are we to handle deployment of this? Will there be endpoints operating QUICv1 with h3-29 or h3-32? Or have the chairs cooked up a maneuver to avoid this problem? Martin
