Instructing a player on where to publish QoE or log data

[wilaw]

One of the benefits of a bidirectional protocol such as MOQT is that a player can publish QOE and logging data directly back to the delivery system that is feeding it media, rather than beaconing it to a 3rd party location.

How can we use the catalog to instruct the player to publish tracks? we need to indicate the destinaiton as well as the format of the track.

We can introduce a new PUBLISH catalog item, which holds an array of track definitions. For each track, we specify the namespace, name, track type and token that it should use.

 "publish": [
    {
      "name": "cmcdv2-%playerID%",
      "namespace": "datacollection.com/qoe",
      "packaging": "eventtimeline",
      "eventTimelineType": "org.cta.wave.cmcd.v2",
      "c4m":"%token1%"
    },
    {
      "name": "logging-%playerID%",
      "namespace": "central-log-collector.com/ingest",
      "packaging": "eventtimeline",
      "eventTimelineType": "org.ietf.moq.moqt.logging"
      "c4m":"%token2%
    } ]

[suhasHere]

I can take a stab at this