Evaluate need for describing the generic requirements for any streaming format that would use MOQ-T #107
Description
@fiestajetsam and I are starting with the scenarios from https://datatracker.ietf.org/doc/html/draft-nandakumar-moq-scenarios-00. The title of that draft indicates that it also explores the data model, but version -00 doesn't seem to contain much, if any, of the data model.
We note that https://github.com/moq-wg/warp-streaming-format defines a specific data model, but does not describe the data model in a generic way, that would allow a protocol designer to define a different streaming format that would also exploit MoQ Transport.
If the MOQ working group is determined to support multiple streaming formats, the description of a generic streaming format probably belongs in the requirements section of the (use cases and) requirements draft. The questions that occur to us are:
- Two or more viable competing streaming formats have traction in the working group ("hello, RUSH? Hello, LOC? Are you there?")
- A better understanding of why we need two or more competing streaming formats - what does https://github.com/moq-wg/warp-streaming-format not support?