The Security WG meeting focused on finalizing the Q1 workshop agenda and discussing the CDN log schema paper. Kei reminded participants to update their presentations and upload them to Google Drive by the end of the day. Brian discussed the CDN log schema, emphasizing the need for consistent terminology and precision, such as using milliseconds for time measurements. The group debated the inclusion of specific log fields like cache performance metrics and geographic information, ultimately deciding to verify their relevance with CDN providers. They also discussed the use of custom fields and the potential for a post-workshop survey and informal meetups.
- Submit your workshop presentations with title to Kei.
- Provide/distribute the WhatsApp group link/QR code so attendees can join and coordinate ad-hoc meetups
- Do one final check of the threat model paper and then submit to JT to start the rectification process.
- Follow up offline with Lee to finalize details and agenda responsibilities for the CDN Leeching segment
- Use the term ‘URI’ (not URL) in the CDN log document and adopt that naming in the draft
- Update the cache-hit field in the CDN log draft to use 0/1 encoding (remove true/false)
- Remove the ADN gateway field from the CDN log draft (accepted deletion)
- Change all performance timing units in the CDN log draft to milliseconds to match CMCD and update examples accordingly
- Delete the duplicate ‘time taken’ field from the CDN log draft
- Consolidate detailed backend timing fields into a single origin/backend latency metric (update description to ‘origin latency’) in the CDN log draft
- Antitrust Statement and WG Discussion
Workshop Agenda and CDN Log Schema Review
- Kei outlines the agenda for the meeting, including a review of the workshop agenda and discussing the CDN log schema paper.
- Kei shares the screen to discuss the schedule and reminds participants to update their presentations and upload them to the shared Google Drive.
- David requests more time to complete his presentation and Kei agrees to extend the deadline.
CDN Log Schema Discussion
- Brian Paxton begins discussing the CDN log schema, starting with the request URL and whether to use URI or URL.
- Glenn Deen suggests using URI for consistency within SVTA, and Brian agrees to use URI.
- Brian discusses the response headers, including the cache status code, and decides to use 01 for cache hit/miss.
- The group debates the precision of time measurements, deciding to use milliseconds for consistency with CMCD.
Performance Logs and Network Logs
- Brian reviews the performance logs, including prewrite time, read time, and total time, and discusses the need for consistent terminology.
- David suggests tying the performance logs to CMCD, which uses milliseconds, and Brian agrees to change the document to milliseconds.
- Brian discusses the network logs, including total bytes in and out, and decides to remove duplicate entries.
- The group debates the usefulness of various network log fields, such as first byte served and last byte served, and decides to remove them.
Geographic Fields and Custom Fields
- Brian reviews the geographic fields, including ASN, ISP, city, and country, and discusses their relevance to CDN logs.
- David explains that these fields come from the common access token (CAT) and should be consistent with the CAT document.
- The group discusses the importance of custom fields in CDN logs and decides to include them in the schema.
- Brian suggests reaching out to CDN providers for feedback on the schema fields and their relevance.
Final Adjustments and Next Steps
- Brian reviews the final sections of the CDN log schema, including cache performance fields and non-common CDN log fields.
- The group decides to remove some fields that are too specific or not relevant to the CDN log schema.
- Kei suggests reaching out to CDN providers for feedback on the schema fields and their relevance.
- The meeting concludes with a plan to review the schema again on-site and make final adjustments based on provider feedback.
Next Meeting: Tuesday, March 10, 2026 8am PST