SVTA_LOGO_FINAL_revised_2022

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

Attendees

Tony Stott (Streaming Video Technology Alliance (SME))
Joan Treveset (Castlabs)
Jun Heider (Streaming Video Technology Alliance (SME))
Kyle Faber (Hydrolix)
Casey Occhialini (Paramount)

Minutes

  • Summary

The QoE WG Call focused on updating error codes for better standardization. Tony Stott presented changes to the error code structure, moving from a string-based system to a more uniform integer format. The new system uses a three- or four-digit code, with the digit(s) in the thousands column indicating the error domain and the last three specifying the issue. The team discussed the extensibility of the system, reserving space for future error categories. Casey Occhialini and Kyle Faber supported the proposal, emphasizing the need for standardization to improve error reporting and collaboration. Joan Treveset inquired about using illustrations from the document for marketing purposes, which Hali Morek will confirm.

 

 

  • Action Items
  • Update and polish the error-code document: apply the new 3- or 4-digit integer structure, correct examples and tables (including replacing old example codes), clarify category/index wording, and finalize the document for review
  • Start importing selected standardized error codes into the Common Media Library to make them available for reporting and reuse
  • Talk to JT and arrange for Tony Stott to be set up as a SVTA subject matter expert, and prepare the agreement required to formalize that role
  • Hali to check with JT whether the document illustrations can be used in a marketing blog and report back to Joan with permission and any usage conditions

 

 

  • Antitrust Statement and WG Discussion

Introduction to Error Codes and Document Updates

  • Tony Stott initiates the main discussion by addressing the changes in error codes, emphasizing the importance of the recent proposed update.
  • Tony presents the updated document (v0.2) with the new integer-based error code structure.
  • Tony details the proposed changes to the error code structure, including: dropping the initial zero from the code, adding an extra digit for the error index and changing the unknown error from 0000 to 999.

Detailed Explanation of Error Code Structure

  • Tony elaborates on the new error code structure, explaining how engineers can easily filter errors using the 1000s column for the error domain.
  • The last three digits specify the specific issue within the category, and Tony suggests a simple way to filter errors using modulo 1000.
  • Tony reserves the first error code (999) for unknown errors, making it easy to filter out three-digit codes.
  • The discussion includes the extensibility of the error code system, with plans to increase to five places if more error categories are needed in future.

Feedback and Adjustments to Error Code Structure

  • Jun Heider requests Tony to scroll back to the previous page to ensure the old error codes are updated.
  • Tony and Joan discuss the need to separate the error code structure to avoid confusion, with a comment clarifying the category zero (999) error code.
  • The team agrees on the new structure, with Tony making the necessary adjustments to the document.
  • Tony confirms the changes, including the removal of leading zeros and the use of a consistent error index format.
  • Casey Occhialini joins the meeting and Tony provides a quick overview of the changes made to the error code structure.
  • Casey suggests a correction to the example error code format, which Tony agrees to update.
  • Tony emphasizes the importance of the new structure, which makes the error codes more uniform and easier to understand.
  • The team discusses the potential for future updates and the need for consistent implementation of the new error code structure.

Final Adjustments and Feedback

  • Tony asks for feedback on the new error code structure, ensuring everyone is happy with the changes.
  • The team agrees that the new approach is an improvement over the previous one, with more structured and uniform error codes.
  • Tony plans to update the document and examples, ensuring all changes are reflected accurately.
  • The team discusses the potential for further feedback and adjustments, with Tony encouraging ongoing input and collaboration.

Marketing and Document Permissions

  • Joan Treveset (Castlabs) asks about the use of illustrations from the document for a marketing blog post.
  • Tony refers Joan to Hali Morek for permission, who will check with JT and get back to Joan.
  • Hali informs Tony about the process of being set up as a subject matter expert at SVTA, which Tony agrees to.

Conclusion and Next Steps

  • Tony thanks everyone for their input and contributions to the error code structure update.
  • The team discusses the next steps, with Tony planning to update the document and examples based on the feedback received.
  • Tony mentions he might miss the next meeting due to a trip, but plans to be back for the following meeting.

 

 

Next Meeting:  Wednesday, February 11, 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.