SVTA_LOGO_FINAL_revised_2022

DASH-IF IOP Content Protection and Security Meeting Minutes
April 21st, 2026 7:00am to 8:00am PT</p

Attendees

Laurent Piron (Nagra Kudelski)
Moshi Elad (Synamedia)
Pete Galt (Irdeto)
Kei Foo (Charter Communications)
Xiaohan Wang (Google)

Minutes

  • Summary

The meeting focused on key rotation and early announcement strategies for streaming content security. Laurent and Pete discussed a proposed solution involving providing future keys in advance to reduce license request spikes during key rotations. Moshi suggested an alternative approach where the license server could proactively provide metadata about upcoming keys to players, allowing for more granular license requests. The group debated the benefits and challenges of different implementation approaches, including the potential impact on latency for live events. They also discussed the need for player modifications to support proactive license requests and the importance of balancing security requirements with scalability concerns.

 

  • Action Items
  1. Kei – Share security-related client/player topics (e.g., AppSec risks) with the client/player group for their consideration.
  2. Kei and Laurent: Coordinate and schedule a 2-hour joint DASH-IF Security and SVTA Security working group call before summer, inviting key stakeholders from client, packager, and DRM vendor communities to discuss long-term key rotation efficiency and early announcement approaches.
  • Antitrust Statement & Key Rotation Strategy Discussion
  • The team discussed key rotation and early announcement strategies, with Moshi sharing insights from the previous meeting.
  • They explored the concept of providing future keys to devices, particularly for secure devices, to reduce license server load.
  • Pete clarified that the 10-second key rotation period was used for demonstration purposes and could be configurable based on different content needs.
  • The discussion also touched on the potential for selective key distribution to known secure devices, and Pete noted that player modifications would only be needed at the JavaScript level, not at the CDM or EME level.

Proactive License Request Implementation

  • The team discussed implementing proactive license requests to smooth out key distribution patterns during live events.
  • Moshi proposed allowing applications to request keys in advance rather than waiting for manifest signaling, which could help distribute load more evenly and reduce spikes in traffic.
  • Pete agreed this approach could help spread out smaller spikes across a key rotation period, though he noted optimization would be needed based on real-world event durations.
  • Xiaohan raised concerns about latency during live events, questioning whether the timing of license requests might cause playback glitches without early signaling, particularly for time-sensitive content.

License Request Optimization with early announcement

  • Pete and Xiaohan discussed the impact of video player buffer size and round-trip times on license requests, noting that while current ABR streaming with 1-2 segment caching may not face significant issues, future ultra-low latency requirements could present challenges.
  • Moshi proposed an “early announcement by license server” mechanism that would allow players to proactively request licenses based on metadata provided in the license response, including PSSH and key timing information.
  • While both agreed this approach could help smooth license request patterns in the long term, they acknowledged implementation challenges including support for proactive license requests and the server’s knowledge of future key timing, suggesting these would need to be addressed in future iterations rather than immediate solutions.

License Server Implementation Discussion

  • The team discussed implementing a license server system that would provide early signals about upcoming key rotations to players.
  • Moshi explained that while this approach isn’t currently standardized, it could be implemented with existing tools and would allow for smoother key management.
  • Kei suggested organizing a meeting with client players like Google’s Shaka and Apple to discuss long-term solutions and explore the pros and cons of different approaches.
  • Moshi noted that while a comprehensive standard might take 5 years to develop, the building blocks for early license announcements are already available, particularly through CPIX 2.4 which allows specifying key period indices and timing information.

Key Rotation Requirements Discussion

  • Laurent discussed the current state of key rotation requirements, noting that while the basic DRM server, key server, and player setup is working, there are potential issues with expired licenses on some devices.
  • The group debated how to address content owner requirements for key rotation every two hours, with Laurent suggesting that if operators need multiple keys in advance, the key server would need to rotate every 30 minutes.
  • Pete clarified that studio requirements should be part of the operator’s agreement with content owners, and Moshi proposed a potential solution where only L1 devices would receive keys in advance while L3 devices would receive keys on a more immediate basis.
  • The team discussed key rotation requirements and challenges, with Laurent emphasizing the need for realistic values and early announcements about upcoming changes.
  • Kei requested more information about Apple’s HLS early announcement solution, which Laurent confirmed is available on YouTube along with a full day of recorded sessions including presentations and Q&A.

Next Meeting: Wednesday, April 29, 2026 9am PDT

 

Chat Record:

  • Moshi shares: I think the idea of providing future keys by the server is great, but the parameters of a) max time in the future for delivering keys, and b) the key period – need to be established based on security requirements, and not based on scaling requirements.

To solve this –

Since it is assumed the server knows the key rotation schedule, it is possible to send to the client, together with the license response, the time of the next key that is not delivered in the license and the PSSH needed to get it. With this, the client would be able to do time randomization and proactively request the next license. We can call this – early announcement by license server.

 

All – Feel free to comment and discuss.

 

Pete shares: https://www.youtube.com/watch?v=tpLKcVdMUaQ&t=16123s

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.