The meeting focused on planning the next steps for the SVTA foundation document and survey distribution. The group discussed converting the reviewed document into a survey format, with Yoav agreeing to contact JT for assistance. Alan, Yoav, and Sanjay reviewed the foundation document and identified key areas for further development, including request routing, orchestration, and security considerations. The team agreed to draft problem statements for each topic before the upcoming meeting in Las Vegas. They also discussed the need to present the foundation document and encourage survey participation during the upcoming sessions. The conversation ended with the assignment of specific topics for discussion at the next meeting, including request routing by tenant, orchestration, and data exposure.
- Alan: Finish review and edits of the survey document by Monday and send out for review
- Yoav: Send message to JT about converting the survey document into an actionable survey format and request his guidance/help
- Alan: Present the foundation document highlights at the Wednesday session
- All participants: Review the foundation document and fill out the survey during next week's session
- Alan: Draft problem statement for orchestration topic before Thursday
- Sanjay: Draft problem statement for request routing by tenant topic
- Chris: Draft problem statement for security topic
- Yoav: Schedule/organize 2.5 hour session on March 5th for "what next" discussion
- All participants: Define detailed problem statements for their assigned topics before next week's meeting
- Glenn: Discuss content publisher/CDN relationships and data flow during next week's meeting
- Antitrust Statement & Survey Review and Agenda Planning
- The meeting focused on two main topics: reviewing a survey document and planning the agenda for the upcoming week's meeting.
- Yoav noted that while they have approximately 5 hours of discussion time, they haven't yet defined specific agenda items.
- He suggested sending out the survey before the meeting and including a session to explain the foundation document to wider membership.
- Jason, who was previously silent, mentioned he would need to register for remote attendance due to budget constraints.
Security Workshop and Planning Alignment
- Glenn discussed the upcoming security workshop and emphasized the need to plan for the year ahead, considering key meetings and timelines.
- He highlighted the importance of the SVTA meetings in Berlin and Rennes, and suggested scheduling a mid-year checkpoint session to align on progress.
- Alan noted the swift progress on the foundation specification but expressed uncertainty about the next steps, particularly regarding feedback and priorities.
- The group discussed the need for input on technology focus areas and considered whether to wait for a survey or take decisive action based on their own assessments.
Survey Strategy and Framework Alignment
- The team discussed the importance of proceeding with their survey despite its limitations as an indicator rather than a decisive tool.
- Alan suggested filling out the survey themselves to gain orientation, and Yoav agreed, emphasizing the need to address core elements like request routing and open caching.
- Glenn proposed having participants complete the survey during the next meeting, while Yoav recommended focusing on foundational tasks outlined in the framework document.
- The group agreed to start with these foundational areas regardless of the survey results.
Project Tracks and Document Strategy
- The team discussed three main tracks for their project: request routing, orchestration, and security.
- Alan outlined two versions of request routing, one involving the HSP hosting service provider and another for tenants, while Glenn emphasized the need for minimal capabilities and a unified approach.
- Chris was identified as the expert leader for security concerns.
- Glenn raised a question about whether to approach the next round of work with large or small documents, expressing a preference for smaller, focused documents over large comprehensive ones.
Document Management and Security Review
- The team discussed document management and revision processes, with Chris and Glenn agreeing that it's acceptable to revise published documents, even if it means updating them multiple times.
- They proposed creating a master guide document to serve as a catalog of all EDGE documents, allowing for easier tracking and updates.
- Alan raised concerns about network security policies and tenant interactions, particularly regarding DDoS detection mechanisms and the balance between tenant autonomy and network operator control.
- The team agreed to start by defining the scope of security issues that need immediate attention.
Security Documentation Strategy Discussion
- The team discussed security considerations for their documentation approach.
- Chris explained there are three main aspects of security: advice for individuals, prescriptive guidelines for relationships, and how security practices between parties affect their relationships.
- Glenn suggested creating a separate, smaller document for security issues related to each topic, similar to how Unix was documented decades ago through a series of articles rather than one large document.
Security Implementation Strategy Discussion
- The group discussed the importance of security considerations in their document development process, with Sanjay emphasizing the need for implementation plans before security measures can be addressed.
- Alan highlighted the need to focus on core implementation barriers, such as orchestration and network visibility, before tackling less contentious aspects like telemetry and monitoring.
- Yoav agreed on this approach but suggested giving some flexibility to vendors in the orchestration layer for innovation.
- The team decided to use the next meeting to present the foundation document, with Glenn tasked to secure a brief introduction from JT to attract more participants.
Foundation Survey Conversion Planning
- The team discussed the survey related to the foundation document and its conversion into a fillable format.
- Yoav and Alan agreed to finish reviewing the document, with Yoav taking the lead on merging the changes and pushing it out to JT for conversion into a survey.
- Glenn suggested giving JT a heads-up about the format to start thinking about the conversion process.
- The team acknowledged bandwidth limitations for the coming week and agreed to prioritize progress over perfection in the survey creation process.
Survey Preparation for Plenary Session
- Yoav and Glenn discussed the preparation of a survey based on a foundation document, aiming for it to be ready by Monday for presentation at a plenary session.
- Alan agreed to review and edit the document by Monday, with JT set to handle the survey creation and distribution.
- They planned to present the foundation document in 30 minutes, followed by a survey completion session, potentially utilizing an additional slot on March 5th.
- Yoav noted the challenges of the late session time for him and others, emphasizing the importance of the "what next" discussion to move forward.
Refining Request Routing Problem Statement
- The team discussed creating a focused problem statement for request routing specifications, distinct from the existing foundation document.
- Alan proposed drafting a brief paragraph for each of the five key topics before Thursday's meeting, with team members taking turns to lead each section.
- They agreed to address how tenant request routing interacts with network policies, and whether existing specifications like Open Caching IITF could be reused.
- The group also briefly discussed a July IETF meeting and Glenn suggested they should plan ahead for this opportunity.
Content Publisher Decision-Making Strategies
- The team discussed topic assignments for their meeting, with Alan taking orchestration and Sanjay taking request routing.
- Glenn suggested that for larger platforms, content publishers play a more active role in decision-making compared to smaller platforms, particularly in multi-CDN scenarios where they control player-side decisions.
- The team agreed to discuss this topic further next week, and Glenn offered to schedule a checkpoint meeting with the core team to review progress.
Next Meeting: Â Thursday, March 11, 2026 9am PST