SVTA_LOGO_FINAL_revised_2022

Security Meeting Minutes
April 1st, 2026 9:00am to 10:00am PT</p

Attendees

Kei Foo (Charter Communications)
Brian Paxton (Kingsmead Security)
Pete Galt (Irdeto)
Laurent Piron (Nagra Kudelski)
Tom Southall (Warner Bros Discovery)
Erik Pena (DoveRunner)
Lisa Robinson (Comcast/NBCUniversal)
Mark Nakano (Warner Bros Discovery)
Rodrigo Fernandes (Irdeto)

Minutes

  • Summary

The meeting focused on a review of CDN log schema feedback. Brian presented Gemini’s AI-generated feedback on the CDN log schema, which included suggestions for terminology changes, data type specifications, and structural reorganization. The team reviewed various recommendations from Gemini, including switching to snake_case naming conventions and potentially adding data types, though they decided to table some major structural changes pending further validation with CDN providers.

 

  • Action Items
  1. Brian: Add a column for data types in the CDN log schema document and begin populating it; ask for help from the group if needed.
  2. Kei: Mention to Glenn (and/or Open Caching group) the preference for snake_case naming convention and consider alignment across SVTA standards.
  3. Brian/Kei: Check with CDN providers (e.g., Akamai, CloudFront) to determine if log fields such as cache status (hit/miss/refresh/still/bypass) and timing precision (milliseconds vs. microseconds/nanoseconds) are supported or standard in current CDN logs.
  4. Kei: Ask internally and with CDN providers about the relevance and usage of Trace ID/Traceparent versus Request ID in CDN logs for fraud detection purposes.
  5. Brian: Soft trim and clarify the list of references in the CDN log schema document, focusing on the most relevant standards and removing less relevant cybersecurity/framework entries.
  6. Kei: Share the results of the workshop survey in the next call once compilation is complete.

 

  • Antitrust Statement & WG Discussion

Introduction

  • Kei provided an update on the antitrust policy and mentioned that threat models were reviewed by Glenn using AI, with results to be shared in the next call.
  • Brian presented findings from Gemini’s analysis of the CDN log schema, which included suggestions for additional sections on implementation guidance, privacy, and compliance, as well as considerations for log aggregation across multiple CDNs.
  • The team debated whether to incorporate these suggestions into the document or keep it focused solely as a data model schema.

CDN Logging Document Updates

  • The team discussed two main topics regarding a CDN logging document.
  • They decided to table the implementation guide portion as it was deemed out of scope, particularly regarding GDPR and CCPA compliance, which were already noted as not addressed.
  • The team agreed to switch field naming conventions to snake_case (lowercase with underscores) rather than kebab case (hyphens) to improve copy-paste functionality and align with common data storage conventions.
  • Regarding data types, while the SVT open caching Logging spec includes format specifications, the team was torn between adding data type specifications to make the document more useful versus avoiding additional work, with no final decision reached.

Documentation Restructuring and Data Specifications

  • The team discussed adding data type specifications to their documentation, with Brian volunteering to implement this change.
  • They debated how to handle null values and data types, particularly for timestamps, with Erik suggesting that having data type hints would be beneficial for external systems.
  • The group also discussed a significant restructuring of their documentation from five sections (request logs, response logs, performance logs, network logs, and geographic logs) into four new categories: protocol metadata, data volume metrics, timing metrics, cache and origin metadata, and client and network context, which would better align with IETF and SVTA specifications.

CDN Logging Specification Discussion

  • The team discussed comparing their CDN logging specification with the Open Caching specification, but decided to table the comparison due to concerns about terminology differences and potential confusion.
  • They agreed to investigate current industry practices by examining logs from CDNs like Akamai and CloudFront to determine whether to use milliseconds or microseconds for timing specifications.
  • The team also considered expanding cache status categories from simple hit/miss to the five categories defined in the Open Caching spec, though this was left as an open question requiring further investigation.

CDN Log Schema Enhancements Discussion

  • The team discussed potential additions to their CDN log schema, reviewing suggestions from Gemini’s research.
  • They decided to add transport protocol information but rejected several other proposed additions including TLS extension data, watermarking IDs, and request disposition fields, determining these would provide too much detail or not be helpful for fraud identification across CDNs.
  • The team also discussed the Trace ID concept but agreed to consult CDN providers before making decisions about incorporating it into their schema.
  • Regarding external references, they decided to keep a few relevant references like OpenTelemetry but agreed to trim down the extensive list of external standards and frameworks that Gemini had suggested.

 

Next Meeting: Tuesday, April 21, 2026 8am 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.