- What are out critical outcomes ?
- What are the most critical areas to document ?
- Discussion on Architecture and Requirements
- Timelines / Milestones ?
- What needs to be ported, who and when ?
Notes during the meeting:
- Topics to discuss:
- Architecture discussion
- specialized HW
- special controls
- Sound from remote devices
- tcp/ip
- can connect
- Architecture discussion
Architecture Diagram to start with:
session manager able to configure dsp?
open/ proprietary networkmanager separate!
external (zephyr/autosar) devices reserve/create ressource
Gateway/Portal handling ressource/ACL management. Returning ressource URI (socket or network endpoint)
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
Summary #1:
- In a car we have (proprietary) network managers. The pipewire session manager needs to communicate with these and provide an API.
- Similar for copy protection mechanisms.
- Thus session manager cannot (shouldn't try) to abstract all of these.
- System management might be on external hardware
- Security provided by a gateway/portal that handles ressource managment and authoriztion.
- Need to take HDCP/content protection in mind (e.g. videvine)
TODO: Session Manager first.
Issues:
- static and/or default config vs dynamic configuration at runtime
- handle device removal
- graph inplemented in HW level
