Similar to #3420, thought I'd ask about names if we're making it clear that the DATA and FINAL_DATA capsules represent TCP stream data that can be combined and split.
Would it make sense to name them:
TCP_DATA and TCP_FINAL_DATASTREAM_DATA and FINAL_STREAM_DATA / STREAM_FINAL_DATA
The latter seems nicer if we're saying that merging and splitting is a generic property of any stream, not just TCP. The former seems nicer if we're saying that merging and splitting can be done only in the context of connect-tcp.
This would also help to distinguish them from the HTTP/2 and HTTP/3 DATA frames that they are carried within.
If we keep the existing names, can we add an editorial note for implementors that they should not confuse them with the HTTP/2 and HTTP/3 frames of the same name?
Similar to #3420, thought I'd ask about names if we're making it clear that the
DATAandFINAL_DATAcapsules represent TCP stream data that can be combined and split.Would it make sense to name them:
TCP_DATAandTCP_FINAL_DATASTREAM_DATAandFINAL_STREAM_DATA/STREAM_FINAL_DATAThe latter seems nicer if we're saying that merging and splitting is a generic property of any stream, not just TCP. The former seems nicer if we're saying that merging and splitting can be done only in the context of
connect-tcp.This would also help to distinguish them from the HTTP/2 and HTTP/3
DATAframes that they are carried within.If we keep the existing names, can we add an editorial note for implementors that they should not confuse them with the HTTP/2 and HTTP/3 frames of the same name?