Original text:
The REGISTER_DATAGRAM_CONTEXT capsule (see iana-types for the value of the capsule type) allows an endpoint to inform its peer of the encoding and semantics of datagrams associated with a given context <del> ID.  Its Capsule Data field consists of: </del>  The context ID to register. value of the capsule type) allows a client to inform the server that datagram contexts will not be used with this stream.  It also informs the server of the encoding and semantics of datagrams associated with <del> this stream.  Its Capsule Data field consists of: </del>  A variable-length integer that defines the semantics and encoding of the HTTP Datagram Payload field of datagrams, see datagram- The CLOSE_DATAGRAM_CONTEXT capsule (see iana-types for the value of the capsule type) allows an endpoint to inform its peer that it will no longer send or parse received datagrams associated with a given <del> context ID.  Its Capsule Data field consists of: </del>  The context ID to close. The DATAGRAM capsule (see iana-types for the value of the capsule type) allows an endpoint to send a datagram frame over an HTTP stream.  This is particularly useful when using a version of HTTP <del> that does not support QUIC DATAGRAM frames.  Its Capsule Data field consists of: </del>  A variable-length integer indicating the context ID of the datagram (see datagram-contexts).  Whether or not this field is

Reviewer comments:
The thing that sucks here is that the diagram won't auto expand , so we can't easily ref the section. Manually referring to the section is a maintenance pain. So instead just state the actual type in the text an the diagram. I have a feeling you were linking to the section to avoid the maintenance hassle of updating type codes in multiple place. But I'm quite happy to take that burden because I find it more pleasant to read this way.
Perfectly reasonable
QUIC and HTTP/3 style is to define the general format and then in each instance define the object including all of its fields. This would look like This can later be updated with the actual type value once things settle down
Fine by me.
There's a disparity between the largest flow ID that can be carried in the DATAGRAM frame and the largest that we can express in Datagram-Flow-Id. Draft 00 prevents a flow ID allocation of >= 10^15-1 but doesn't seem to address the case where a DATAGRAM frame contains that value. This is clearly an error, and I'd suggest that it is a connection error; probably or some new codepoint if we really wanted.
I don't think that needs to be an error, we can simply treat this like any other unknown flow ID?
IMO this is clearly a situation that shouldn't happen and indicates the sending endpoint probably has some bug. I'm not sure on what being silent on the matter helps.
This issue is no longer relevant now that we have merged , closing.

Revised text:
The REGISTER_DATAGRAM_CONTEXT capsule (see iana-types for the value of the capsule type) allows an endpoint to inform its peer of the encoding and semantics of datagrams associated with a given context  <ins> ID. </ins> The context ID to register. value of the capsule type) allows a client to inform the server that datagram contexts will not be used with this stream.  It also informs the server of the encoding and semantics of datagrams associated with  <ins> this stream. </ins> A variable-length integer that defines the semantics and encoding of the HTTP Datagram Payload field of datagrams, see datagram- The CLOSE_DATAGRAM_CONTEXT capsule (see iana-types for the value of the capsule type) allows an endpoint to inform its peer that it will no longer send or parse received datagrams associated with a given  <ins> context ID. </ins> The context ID to close. The DATAGRAM capsule (see iana-types for the value of the capsule type) allows an endpoint to send a datagram frame over an HTTP stream.  This is particularly useful when using a version of HTTP  <ins> that does not support QUIC DATAGRAM frames. </ins> A variable-length integer indicating the context ID of the datagram (see datagram-contexts).  Whether or not this field is