The meeting focused on finalizing updates to the PQC threat model document, with Srikanth leading the review of recent changes and seeking group approval to share the document externally with SOC chipset vendors and device manufacturers for feedback. The team discussed addressing specific comments from members including David, Thierry, and Prashant, with Srikanth clarifying that solution space recommendations would be handled in a follow-up implementation document rather than the current threat model document. Kei raised the topic of potential collaboration with ACE for information sharing, but Glenn and JT expressed concerns about liability risks, leading to a discussion about the need to first define what constitutes sensitive data before proceeding with any information sharing initiatives. The group also clarified the role separation between the DASH-IF WG, which maintains authority over specs for high-frequency key rotation, and SVTA's Security WG, which will create best practice guidelines for implementation once the specs are finalized.
- Kei to reach out to Niranjan to see if he is available to lead the next discussion on what information to share and define sensitive data.
- Kei to facilitate the next PQC session in Srikanth's absence.
- Srikanth to reach out to Glenn and JT to get approval before sharing the PQC threat model document with external partners.
- Srikanth to share the PQC threat model document as a PDF with SOC chipset vendors and device manufacturers for early feedback after getting approval.
- Prashant to review the updated section in the PQC threat model document regarding certificate and key sizes and resolve the comment.
- Antitrust Statement and WG Discussion
PQC Threat Model Doc Finalization
- The team discussed finalizing the PQC threat model document, with Srikanth having made recent changes and expecting additional updates from Prashant.
- They agreed to review these changes and consider sharing the document externally with SVTA to gather feedback.
- Once feedback is addressed, the team plans to begin working on implementation guidelines and documentation as the next phase.
Risk Assessment and Solutions Discussion
- The team discussed risk assessments and solutions, with Srikanth clarifying that while risks were well captured, solutioning would be addressed in a subsequent guidelines document rather than the current document.
- Thierry experienced audio issues but confirmed they were okay with proceeding.
- The group also discussed concerns about certificate and key size challenges, which Srikanth noted had been captured in the preconditions and vulnerabilities section of the document.
Document Review and Updates
- Srikanth discussed recent changes to the document, including the removal of Section 9 on vulnerabilities and preconditions since threat sections already contained their own vulnerability information.
- Srikanth also mentioned incorporating Lars's comment into the conclusion section after being unable to identify the commenter during a previous review.
- Prashant apologized for missing a relevant section and agreed to review the document to address any potential redundancy in their comments.
Document Sharing with Partners
- Srikanth discussed plans to share a document with external partners, including SOC chipset vendors and device manufacturers, for feedback.
- Kei suggested including Glenn Deen in the review process and confirmed there were no objections to the approach.
- Srikanth mentioned plans to invite chipset companies and device manufacturers to join the working group, with the process taking a few weeks.
- Jorge requested the document's URL for review.
- The group discussed sharing a document with external companies, with Srikanth agreeing to reach out to JT and Glenn for approval before proceeding.
- Kei updated the group on potential collaboration with ACE, explaining that while Glenn indicated there could be liability risks, the Alliance is not ready to handle such risks due to budget constraints.
- The group decided to wait for any alternative suggestions from Nicolas before approaching Glenn and JT again about collaboration with ACE.
SVTA Information Sharing and Sensitive Data Definition Discussion
- The group discussed whether SVTA should be the appropriate place to organize information sharing, particularly for sensitive data.
- While Glenn expressed concerns about liability and external collaboration, the team acknowledged that the organization is still exploring ways for members to share sensitive information at the board level.
- Srikanth clarified that the focus should be on understanding what information members are willing to share and ensuring it is not sensitive before proceeding with any sharing mechanism.
- The team discussed the need to define what constitutes sensitive data before proceeding with the proposal.
- Nicolas emphasized the importance of agreeing on a consistent set of actionable signals that can reasonably identify attackers in logs.
- Srikanth noted that beyond sensitive data definitions, member or customer-related information with high privacy protection also needs consideration.
- The group acknowledged they are still in early discussions and waiting for Niranjan to provide more direction on moving forward with the proposal.
DASH-IF Specification Authority Clarification
- Kei clarified that DASH-IF WG remains the authority for defining specifications on high-frequency key rotation, while SVTA's Security WG will create best practice guidelines for implementation once the specifications are complete.
- Laurent confirmed this understanding, noting that DASH-IF WG handles the DASH aspect while Apple leads on HLS.
- The group agreed that these roles prevent duplication of efforts between the working groups.
Next Meeting: Â Tuesday, November 10, 2026 8am PST