SVTA_LOGO_FINAL_revised_2022

Measurement/QoE Meeting Minutes
January 14th, 2026 8:00am to 9:00am PT</p

Attendees

Tony Stott (Streaming Video Technology Alliance (SME))
Joan Treveset (Castlabs)
Mohammad Saud Syed (Interra Systems)
Jun Heider (Streaming Video Technology Alliance (SME))
Slavik Lozben ()
Casey Occhialini (Paramount)

Minutes

  • Summary

The QoE WG Call focused on refining the error code structure for media playback. The team proposed moving completely to an integer code, rather than embodying error codes as numerical strings. This is to make the proposal simpler to work with and more efficient to store and filter on. The changes involve removing the first zero from the code which was largely superfluous, using the thousands column to denote the error category and the last three the error index, and changing the unknown code from 0000 to 999. The meeting concluded with plans to update the specification and revisit the changes in the next meeting.

 

 

  • Action Items
  • Prepare an updated version of the error-code proposal using the integer format, add it to the specification document, and circulate the updated doc to the working group for review prior to the next meeting
  • Send an interim update and coordinate collection of feedback from working group members on the updated error-code proposal so any objections can be raised before the next meeting

 

 

  • Antitrust Statement and WG Discussion

Error Code Structure Discussion

  • Tony Stott initiates the meeting, wishing everyone a good new year and outlining the agenda, focusing on error codes.
  • Tony shares his screen to review the current error code structure, explaining the existing four-digit format with two digits for error categories and two for the index.
  • Tony discusses the potential inclusion of externally defined error codes and the need to revisit the error code structure.
  • Tony presents various options for the error code structure, including fixed width, internal vs. external error classification, and extensibility.

Proposed Changes to Error Code Structure

  • Tony reviews various options to improve the error code structure, using integers instead of strings.
  • The team opt for a four-digit code, dropping the initial zero. This is extensible for error categories – there is space for 2 more categories before the code length increases to 5; and extensible for the error index which now has 3 digits to represent it.
  • To determine the error category from the code just divide by a thousand, and use modulo 1000 to get the error index.
  • Casey Occhialini and Jun Heider discuss the benefits of using integers, including easier parsing and the ability to expand the error code space.
  • The group agrees that using integers would make the error code system more flexible and efficient.

Handling Unknown and Custom Error Codes

  • The group discusses how to handle unknown and custom error codes, with Tony suggesting that unknown codes should be clearly defined.
  • Joan Treveset recommends switching the unknown error code from “0000” to “999” because four zeros does not fit in with the new integer approach. Joan recommends not using a single “0” either since there would be on clear way of differentiating an unknown error from a an non-initialized or corrupt error code.
  • Unknowns could be quickly found by viewing the set of codes <1,000.

Finalizing the Error Code Structure

  • The group discusses the potential for collisions between internally defined error codes and externally defined codes, such as HTTP status codes or VAST errors that are not in our control.
  • Casey and Jun suggest limiting the space for internally defined error codes to avoid collisions with externally defined codes.
  • The group agrees that the new error code structure would provide more flexibility and efficiency, and they plan to review the updated version in the next meeting.

 

 

 

Next Meeting:  Wednesday, January 28, 2026 8am PST

Have A Question ABout Membership?

Schedule A Meeting

[hfcm id="18"]

Send An Email

Don’t want to schedule a face-to-face meeting just now? No problem. Simply send your membership question to info@streamingvideoalliance.org or fill out the form below and someone will get back to you as soon as possible.