SVTA_LOGO_FINAL_revised_2022

Open Caching Meeting Minutes
February 12th, 2026 8:00am to 9:00am PT</p

Attendees

Yoav Gressel (Streaming Video Technology Alliance (SME))
Sanjay Mishra (Verizon)
Ben Rosenblum (Vecima Networks)
Alan Arolovitch (2you.io)
Guillaume Bichot (Broadpeak)

Minutes

  • Summary

Yoav discusses the meeting agenda mentioning two items, the Logging spec and OC API Repo discussions. The meeting focused on addressing various technical issues and updates. Yoav reviewed the comments received on the OC API Repo spec. Key points included the need to report a bug regarding the deprecated CDN selection and the FCI multicast delivery, which was found to be missing. The team discussed the importance of updating the response-driven flow in the request routing interface to align with SVTA 2048. They also reviewed the Logging spec, noting the need to clarify how to handle connection resets, suggesting zero bytes and status 499. Additionally, Sanjay Mishra highlighted the importance of submitting drafts for the privacy, triggers, and edge control documents for the upcoming CDNI meeting.

 

 

  • Action Items
  • Coordinate with JT and the group to publish an updated version of the triggers document (apply editorial fixes and publish before March/IETF if possible)
  • Copy/post the current version of the Logging document and mark it ready for review.
  • Request that meeting attendees spend some time to review the Logging document and solicit feedback ahead of the next meeting
  • Ping Alfonso to accelerate review/acknowledgement of the pending pull request related to the spec changes so the PR can be processed.
  • Fix the YAML/spec bug(s) including the missing FCI multicast delivery section and remove or resolve the unused name_private_feature_type object so the YAML and spec are consistent
  • Review and update the selection entries to include the missing Extended Properties and reconcile recent changes in the selection files
  • Verify and add the missing response-driven flow (response-triggered flows, e.g. code 425/425-like sections) into the request routing interface files and ensure the response-driven flow examples are present
  • Share the updated Edge Control draft to Sanjay and the mailing list.
  • Start reviewing the logging document on the mailing list, chipping away section by section and posting comments/edits for iterations
  • Hali to check the website-hosted request routing interface document to verify it is the latest version and investigate website download/serving behavior differences
  • Hali to also check on SVTA2037-2 vs SVTA2037-1 documents on the website.

 

 

  • Antitrust Statement and WG Discussion

Introduction

  • Yoav Gressel introduces the meeting sharing the agenda items; discussing the Logging spec and reviewing comments on the OC API Repo.
  • Yoav shares then OC API Repo feedback and reviews the comments received.

OC API Repo Review

  • Yoav mentions some issues with the SVTA2037-1/SVTA2037-2 documents on the website – Hali to look into this.
  • Yoav Gressel mentions a reference to a deprecated section or object in the CDN selection, noting it is in the spec but not in the YAML.
  • Guillaume Bichot confirms the CDN selection is still present but acknowledges the FCI multicast delivery has disappeared.
  • Yoav Gressel and Guillaume Bichot discuss the multicast delivery issue, confirming it as a bug.
  • Guillaume Bichot mentions no pull request has been processed and that Alfonso needs to review it.

Name Private Feature Type Issue

  • Yoav Gressel points out the name private feature type is not referenced in the file, causing confusion.
  • Guillaume Bichot checks and confirms the issue, noting it is not a big problem but can be solved.
  • Yoav Gressel mentions the protected secret looks good and suggests pinging Alfonso to accelerate the review.
  • Guillaume Bichot and Yoav Gressel discuss the maximum bits issue in the IPv6 mask, confirming it needs to be updated to 128.

Request Routing Interface and Response Driven Flow

  • Yoav Gressel and Alan Arolovitch discuss the request routing interface, noting it misses the response-driven flow per SVTA 2023.
  • Alan Arolovitch clarifies the latest document is SVTA 2048, not 2023.
  • Guillaume Bichot and Alan Arolovitch discuss the response-driven flow, confirming it is missing in the file.
  • Yoav Gressel suggests checking the website for the latest version of the document.
  • Hali to look in the issues with this document.

Trigger and Public Repo Update

  • Alan Arolovitch mentions the trigger issue is not finalized and needs an update.
  • Guillaume Bichot and Alan Arolovitch discuss the need to publish a new document before the IETF meeting.
  • Yoav Gressel reminds the aim is to move forward with the document and make it a public repo.
  • Ben R provides an overview of the spec, noting the need for feedback and reviews.

Open Casting Use Case and Logging Spec Clarification

  • Guillaume Bichot discusses the open casting use case, noting progress and the need to define the workflow.
  • Guillaume Bichot mentions issues with Google Doc access and the use of SharePoint for collaboration.
  • Guillaume Bichot and Yoav Gressel discuss the logging spec, noting the need to clarify how to handle connection resets.
  • Guillaume Bichot suggests writing zero bytes and status 499 in the logging record for connection resets.

CDNI Call and Open Items

  • Sanjay Mishra from Verizon discusses the upcoming CDNI meeting, noting the need for material submission.
  • Sanjay Mishra mentions open items such as privacy, triggers, and edge control, seeking updates from authors.
  • Guillaume Bichot confirms he has the necessary materials for the edge control draft.
  • Sanjay Mishra plans to review the metadata draft and the logging document, requesting time on the agenda for discussion.

 

 

 

Next Meeting:  Thursday, February 26, 2026 8am PST

 

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.