search

ietf-wg-webtrans / draft-ietf-webtrans-overview

WebTransport overview draft.
Other
11 stars 4 forks source link

WebTransport stream capabilities and signals #12

Open nidhijaju opened 1 year ago

nidhijaju commented 1 year ago

The W3C spec currently refers to definitions in QUIC (in https://www.w3.org/TR/webtransport/#webtransport-stream) for concepts that should be transport protocol independent. Would it be possible to add these concepts to the overview document, so that we can refer to them without having to specify concepts in terms of QUIC?

vasilvv commented 1 year ago

Most of those already should be in https://ietf-wg-webtrans.github.io/draft-ietf-webtrans-overview/draft-ietf-webtrans-overview.html#name-transport-features -- which ones are missing?

nidhijaju commented 1 year ago

I think the ones that are missing are:

I guess technically "resetting a stream" could refer to Section 4.3-3, and the "flow control" event can refer to Section 4.3-5 but maybe something more explicit might be nice to be able to refer to. What do you think?

vasilvv commented 1 year ago

STOP_SENDING is "abort receive side", and RESET_STREAM is "abort send side" (I believe they were called that way in the API spec at some point). I'm not sure what the spec means by the "flow control event".

ekinnear commented 8 months ago

We've also got DRAIN_WT_SESSION and CLOSE_WT_SESSION (which might want to be renamed as such) in common now, do we need to add those to the list of concepts that should be in the overview? (Even if not referred to by the W3C API)

DavidSchinazi commented 3 months ago

Chair: briefly discussed in slide at IETF 120. No comments from room.