afrind / moqbof Goto Github PK

Should some of this work go to ART and some of it go to TSV? Or should we have one single effort that takes up both parts of what you're proposing?

There was discussion that the proposal as written assumes its premises, that it presumes the stated use cases are the right ones. You should ask those meta-questions first. It shouldn't be "Is there a protocol that meets these needs?" but rather "Are these the right needs we should be discussing?"

I think this is actually the right thing to do, rather than have me propose further changes to the BOF description on my own.

In a perfect world, we can discuss all of these issues and come to agreement before the BOF, and have a really short BOF, and in a less perfect world, we will know what the contentious issues are, and can focus the BOF agenda on those issues.

I'll do a PR for this, for consideration.

The group that is advancing this appears to be deflecting attempts by other participants to deal with latency. Should that be in scope for this work?

"What practical protocol glue to make stuff (media) work over QUIC is missing?" was a suggested theme.

The true scope we should be considering here is possibly larger than what the proposal currently contains. Back in "the day" when people wanted to do RTP over QUIC, they were told to go away for a while until QUIC was done and fully rolled out. It might be time to re-engage that larger conversation.