@mnot was there a reason to remove this multiplicity requirement? Can we track that as a separate issue?

This is still a bit imprecise. suggest ```suggestion HTTP/3 datagrams MUST only be sent with an association to a stream whose HTTP semantics explicitly supports HTTP Datagrams (usually, in conjunction with the extension that invokes the use of HTTP Datagrams. For example, existing HTTP ``` Also, these requirements seem general to all HTTP datagrams, but are placed against "HTTP/3 datagrams"

In the abstract, you propose the addition of the text "Both are intended for use by HTTP extensions, not applications." do you think we need to, similarly, avoid using the term application here?

This are actually streams of datagrams ```suggestion conveying multiplexed, bidirectional datagrams streams inside a HTTP connection, with each datagram stream represented by an HTTP conversation. They ```

Would be nice to be a litte more specific here: ```suggestion extension. To enable seamless transfer of HTTP Datagrams in in HTTP/2 and HTTP/1.1, this document also defines the Capsule Protocol, a more general convention for conveying reliable message streams over HTTP. ```