Skip to content

API functionality: ambiguity of 'maximum downstream media bit rate' assertion #41

Description

@Kevsy

Problem description

Querying the network for 'maximum downstream media bit rate' could be interpreted as:

  1. the network bandwidth (maximum achievable throughput) for that device connection.
  2. the network throughput to that device connection at the time of the request
  3. the network throughput to that device connection estimated for the next DASH/HLS segment (e.g. 4-second forecast). Note that DASH calculates the next sequence representation one-at-a-time, not for the whole manifest in one go.
  4. the network throughput to that device connection estimated for the entire video session (namely the value of the mediaPresentationDuration in the manifest, e.g. a 30 second or 5 minute forecast)

Expected action

Clarify which of the four is the correct definition in the description, and clarify the name 'maximum downstream media bit rate' as required (e.g. `Current maximum downstream media bit rate')

Additional context

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions