Edge Meeting Minutes
June 4th, 2026 9:00am to 10:00am PT</p
The meeting focused on discussing orchestration for edge computing architecture. Alan presented a plan outlining six key deliverables (D1-D6) for orchestration, including basic authentication, role management, compute inventory, provisioning APIs, and MCP integration capabilities. The group debated implementation approaches, with Glenn advocating for focusing on information exchange rather than specific transport mechanisms to enable interoperability across different hosting providers and caching technologies. Yoav raised important questions about workload interfaces and DNS resolution requirements, prompting discussion about the need for end-to-end architecture documentation. The team agreed to move forward with putting basic specifications on paper, starting with core orchestration elements, rather than waiting for full participation from all members. Sanjay mentioned that Oracle had expressed interest in joining the forum through a former Amazon Prime Video engineer.
Glenn updated the team on his work on messaging and proposed incorporating agentic AI components into the MCP infrastructure to enable integration with AI-controlled workflow environments and analytics frameworks. He explained that the architecture should evolve towards sharing useful information and enabling agentic workflows to make analytics-driven decision-making, rather than relying solely on traditional API-based approaches. Glenn suggested that in the future, they would need to add hooks to their current system to support these new agentic capabilities.
Glenn discussed refining an MCP Enablement Framework for Edge Orchestration based on previous feedback, with plans to potentially create a parallel document outlining the framework’s components and implementation details. Glenn mentioned the development process is taking time as he’s learning about the evolving technology and sorting through available tools. Alan suggested viewing the framework as core services with additional capabilities, emphasizing the need to establish basic engineering scaffolding quickly using new tools available.
Alan presented a new architecture definition focusing on two main tracks: request routing and orchestration. He outlined a phased approach (D1-D6) for implementing basic capabilities including authentication, role management, compute inventory, and provisioning APIs across different hosting providers. Glenn suggested adding a note about enabling agentic workflows and integrating with MCP, though this was left as a future discussion topic. Alan emphasized the goal of making each hosting provider function like a region in a public cloud, allowing tenants to interact with multiple providers in a standardized way.
Alan expressed interest in starting work on specifying APIs between the tenant control plane and HSP, but raised concerns about needing a sparring partner for detailed review to avoid issues that arose from previous solo specification work. Yoav asked clarifying questions about interfaces between workloads and HSP services, particularly regarding DNS resolution and observability features. Alan acknowledged that additional components like DNS discovery and observability might be necessary, and suggested creating an end-to-end architecture document to address these questions rather than focusing solely on the orchestration piece.
The team discussed the approach for defining specifications for edge caching systems, focusing on request routing and orchestration across different implementations. Glenn and Alan debated whether to focus on generic behavioral specifications or implementation-specific details, with Glenn advocating for focusing on information exchange rather than specific transport mechanisms. The group agreed to move forward by putting basic request routing specifications on paper, starting with a smaller subset of features rather than attempting all elements in Phase 1. Yoav raised concerns about limited forum participation and the need for more companies to assign resources to the work, while Sanjay mentioned potential interest from Oracle through a former Amazon Prime Video engineer.
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.