Notes during the meeting:
Architecture Diagram to start with:https://confluence.automotivelinux.org/pages/resumedraft.action?draftId=9404429&draftShareId=03363209-aee5-4d35-9e96-cd70b5b1ffea&#
session manager able to configure dsp?
one client per each ALSA device in case of hardware mixing
open/ proprietary networkmanager separate!
external (zephyr/autosar) devices reserve/create ressource
Gateway/Portal handling ressource/ACL management. Returning ressource URI (socket or network endpoint) ?
George: original idea is to create and configure the pipewire socket; more discussion needed
Potentially desired mechanism for content protection:
1) client connects using (no / invalid) token
2) service reacts with refusal and ID/Link to authority
3) client connects to authority
4) authority grants token
5) client connects to service w/ new token
6) service checks token with authority
7) authority verifies token
8) access granted
→ similar / equal to oauth/openID mechanism
TODO: Session Manager first.
nodes appearing inside pipewire, representing the devices and the clients
client connected to alsa device through DSP and using a filter plugin in the middle
gateway in session manager ?
hardware device graph, somewhere else in the car
wireplumber internal design
Talking points for WED: