Need a mechanism to indicate that a token should be applied to a track

[wilaw]

An MSF player will be given a URL to a catalog and also a token. Upon parsing a catalog, receives a list a tracks. One option is that the player can blindly pass the token in all track subscriptions. Or we can create a catalog track key to indicate that this track requires a subscription.

Possible solution shown below using "requiresToken".

One question is - what if the player is given two or more more tokens? Is this a use-case we need to solve for?

{
  "version": 1,
  "generatedAt": 1746104606044,
  "tracks": [
    {
      "name": "1080p-video",
      "namespace": "conference.example.com/conference123/alice",
      "packaging": "loc",
      "isLive": true,
       "requiresToken": true,
      "targetLatency": 2000,
      "role": "video",
      "renderGroup": 1,
      "codec":"av01.0.08M.10.0.110.09",
      "width":1920,
      "height":1080,
      "framerate":30,
      "bitrate":1500000
    },
    {
      "name": "audio",
      "namespace": "conference.example.com/conference123/alice",
      "packaging": "loc",
      "isLive": true,
      "targetLatency": 2000,
      "role": "audio",
      "renderGroup": 1,
      "codec":"opus",
      "samplerate":48000,
      "channelConfig":"2",
      "bitrate":32000
    }
   ]
}

[gwendalsimon]

An MSF player will be given a URL to a catalog and also a token. Upon parsing a catalog, receives a list a tracks. One option is that the player can blindly pass the token in all track subscriptions. Or we can create a catalog track key to indicate that this track requires a subscription.

The catalog could indicate the method to pass the token. It can be passed during the connection setup with the traditional auth token parameter. Another possible implementation is to include the token in the namespace or in the track name, similarly to the "token in URL path" we have in HLS/DASH.

Example, the catalog could indicate that the name of the track is "1080p-video%token". The MOQ subscriber with token abc123 would subscribe to "1080p-video%abc123" while the subscriber with token def456 would go for "1080p-video%def456".

The fact that the namespace and track names are sequences of bytes, makes the definition of such an insertion quite complicated. I don't know how to do it.

One question is - what if the player is given two or more more tokens? Is this a use-case we need to solve for?

Example: the 1080p video track requires "token_auth" while the ad decisioning track requires "ad_id_token" and the 4k video track requires "premium_token" and "waternark_token".

If the MSF player sent a set of tokens when it connected to the catalog publisher, then the "requiresToken" value could be the token alias that is required for each specific track. Or the list of token aliases.

Two limitations:

• It requires the catalog publisher to get all token aliases
• If players have different aliases, it means that the catalog becomes individual, no more caching

[gwendalsimon]

An MSF player will be given a URL to a catalog and also a token. Upon parsing a catalog, receives a list a tracks. One option is that the player can blindly pass the token in all track subscriptions. Or we can create a catalog track key to indicate that this track requires a subscription.

The catalog could indicate the method to pass the token. It can be passed during the connection setup with the traditional auth token parameter. Another possible implementation is to include the token in the namespace or in the track name, similarly to the "token in URL path" we have in HLS/DASH.

Example, the catalog could indicate that the name of the track is "1080p-video%token". The MOQ subscriber with token abc123 would subscribe to "1080p-video%abc123" while the subscriber with token def456 would go for "1080p-video%def456".

The fact that the namespace and track names are sequences of bytes, makes the definition of such an insertion quite complicated. I don't know how to do it.

This part of my comment is nicely captured in #75