Second Screen WG/CG - TPAC 2026 agenda

[anssiko]

Important

This is a Living Agenda. Meeting slots to be confirmed.

W3C TPAC 2026: Second Screen WG/CG F2F

Logistics

• ✅ Registration: will open on 2026-07-08 (deadline TBA)
• 🏨 Venue: Clayton Hotel Burlington Road, Dublin, Ireland in-person & remote

• 📞 Remote joining instructions: see Invite > Joining Instructions (1 wk prior)
• ✍️ IRC web client: #webscreens
• 🗓️ Invite: 30 October 2026, 09:45–11:00 Greenwich Mean Time
• ✍️ Minutes: TBA

Agenda

The agenda is split across the two selected slots. Final ordering and slot assignment to be confirmed.

▶️ 09:45 (GMT) Meeting start

👋 Welcome

• Intros
• Agenda bashing

📘 Charter orientation

Tip

Working Group home | charter | Community Group home

• WG and CG interplay
• Current scopes, future aspirations
• WG PAG report: https://www.w3.org/2025/06/secondscreen-pag/report.html
• Rechartering: new deliverables, coordination with other groups

📺 Presentation API

Tip

Presentation API spec | explainer | open issues

• TBA Key topics to be selected as planning commences

🪟 Window Management

Tip

Window Management spec | explainer | open issues

• TBA Key topics to be selected as planning commences

• Include the concept of WindowMode to ScreenDetailed window-management#152

⏯️ Remote Playback API

Tip

Remote Playback API spec | explainer | open issues

• TBA Key topics to be selected as planning commences

🏞️ Local casting and screen/media presentation landscape

How do we make local casting and screen/media presentation concrete, interoperable, secure, and acceptable to browser implementers and security reviewers? #15 (comment)

🌐 Open Screen Network Protocol

Tip

Open Screen Protocol spec | explainer | open issues

• TBA Key topics to be selected as planning commences

📲 Open Screen Application Protocol

Tip

Open Screen Protocol spec | explainer | open issues

• TBA Key topics to be selected as planning commences

🧩 Other Deliverables & Incubations

• Local Peer-to-Peer API incubation to inform the Open Screen Network Protocol design
• TBA Key topics to be selected as planning commences

🔍 Privacy & Security

• TBA Privacy & Security topic to be confirmed
• TBA Related cross-group sessions to be confirmed

🫶 Wrap up

• Synthesis of key outcomes, next steps

[backkem]

Hopefully useful input for the Open Screen Network/Application Protocol and Privacy & Security agenda items:

There seem to be a few active or semi-active experiments around the same core use case: reliable, secure, local-network media presentation and casting between a sender and receiver.

Relevant adjacent work includes:

• recent Chromium/OpenScreen work around WebTransport, DataChannels, and standalone sender/receiver integration, e.g. CLs by @tsyoum
• openscreen-rs by @kaidokert, an experimental Rust implementation of the W3C OpenScreen Protocol
• experiments around Open Screen Protocol / WICG Local Peer-to-Peer interop, including https://github.com/backkem/go-lp2p/tree/main/openscreen-go
• related IETF SETTLE work around secure contexts for local-network resources. cc @michaelrsweet

The common thread, from a Second Screen perspective, seems to be: how do we make local casting and screen/media presentation concrete, interoperable, secure, and acceptable to browser implementers and security reviewers?

Potential TPAC discussion topics:

• What minimal video/casting demos would best illustrate demand?
• What sender/receiver interop tests would help validate the Network/Application Protocol split?
• Is WebTransport/DataChannel-style plumbing a useful direction for future Open Screen transport work?
• Which security pieces belong naturally in W3C specs vs IETF work, especially around local secure contexts, naming, authentication, and transport?
• How can the protocol/API surface stay focused on casting and presentation while not painting itself into a corner for adjacent local-network use cases?

A side note: WICG Local Peer-to-Peer API had a topic in a previous agenda, but does not seem to be listed this time. I realize the general-LAN-transport direction is a broader and trickier design space than Open Screen’s core casting/media use cases, but it may still be worth briefly acknowledging as related design pressure when discussing the future shape of the Open Screen Network Protocol.

Tagging @kaidokert and @tsyoum as FYI since their recent/previous work seems directly adjacent.

[anssiko]

@backkem, thank you for your suggestions. Your proposed topics would be great discussion starters for Session 2, added. Also invited are any folks who have done related experiments and would like to share their learnings.

I also added the Local Peer-to-Peer API incubation to the agenda.