SVTA_LOGO_FINAL_revised_2022

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

Attendees

Laurent Piron (Nagra Kudelski)
Pete Galt (Irdeto)
Feras Aldahlawi (Google)
Anthony Stansbridge ()
Rodrigo Fernandes (Irdeto)
Kei Foo (Charter Communications)
Nicolas Weil (Amazon)
Richelle Morgan (Irdeto)
Xiaohan Wang (Google)
Erik Pena (DoveRunner)

Minutes

  • Summary

The meeting focused on Pete’s presentation on high-frequency key cycling (HFKC) for DRM systems. Pete demonstrated a solution that leverages existing Widevine and PlayReady functionality to return multiple keys in single license requests, significantly reducing the number of license requests while maintaining security. The group discussed implementation details, device capacity limitations, and compared this approach with early signaling methods.

 

  • Action Items
  1. Laurent: Consider adding a high-level note to the relevant DASH-IF document describing the possibility of including multiple keys in a license as a short-term solution.

 

  • Antitrust Statement & High-Frequency Key Cycling Solution Presentation
  • Pete presented a solution for high-frequency key cycling (HFKC) that leverages existing technology in Widevine and PlayReady to improve efficiency by a factor of 100 while rotating keys every 10 seconds.
  • The solution returns multiple future keys in a single license request and creates device groups to stagger key distribution, using existing PSSH in media segments or manifests. There is no impact on packagers.
  • When asked about stream cutoff capabilities, Pete explained that while pre-delivered licenses cannot be revoked, they implement allow and deny lists for devices to manage access, particularly for secure devices like L1 and SL3000 models.

HFKC Multiple Keys Implementation Demo

  • Pete demonstrated a new implementation of HFKC that returns multiple keys per license request instead of the traditional single key approach.
  • The system updates the CDM with 4 usable keys for both audio and video, allowing for more efficient key management and reducing the frequency of license requests from every 8 seconds to every 48 seconds in the example.
  • Xiaohan asked about the server-side implementation and was confirmed that the DRM system manages the distribution of keys based on device groups, staggering the return of end keys to achieve uniform distribution.

DASH-IF Specifications Implementation Discussion

  • Laurent and Pete discussed the implementation of DASH-IF specifications, with Pete confirming that no changes to the existing packager CPIX exchange are needed.
  • They addressed concerns about CDM key storage limitations, with Rodrigo noting that Microsoft and Google feedback suggests most devices should support up to 100 keys.
  • The discussion concluded with a comparison between their approach and Apple’s upcoming mechanism for handling multiple keys, where Nicolas suggested their method could remain unchanged while still supporting Apple’s approach.

DASH-IF Security Key Rotation Plan

  • The group discussed a key rotation approach for DASH-IF security, with Laurent and Rodrigo explaining that the solution would address vulnerable devices while maintaining a smooth curve of key requests.
  • Nicolas expressed support for this approach, noting its flexibility and feasibility compared to other proposed solutions, particularly regarding player implementation challenges.
  • While Laurent confirmed that their team had already implemented a similar approach, Kei suggested that DASH-IF security should continue to explore improvements to stay ahead of potential circumvention techniques by pirates.

Key Rotation Technical Discussion

  • Xiaohan raised technical questions about a key rotation approach, comparing it to early signaling and randomization methods, particularly regarding peak load reduction and server-side complexity.
  • Laurent explained that while the approach does shift complexity to the server, it centralizes the changes rather than distributing them across multiple companies.
  • Rodrigo clarified that the system automatically generates future keys and handles device grouping.
  • The discussion concluded with Xiaohan considering whether additional randomization could further flatten the load curve, though no final decision was made on this point.

Key Rotation for Sports Events

  • The team discussed a proposed solution for key rotation in live sports events, where Laurent explained that the current requirement is to change keys at the beginning of events and at least once during the event, rather than every 10 seconds.
  • Pete noted that operators would need to make their own decisions about channel rotation frequency, particularly balancing studio requirements with customer needs.
  • While the group agreed the current approach could work for sports events, they acknowledged uncertainty about whether it would be sufficient for all use cases, and Xiaohan raised concerns about early signaling for live streams with low latency requirements.

Next Meeting: Tuesday, April 21, 2026 7am PDT

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.