Communication CFT Weekly [2026-03-02]

[LittleHuba]

Participants

@JochenSatETAS
@lurtz
@SebastianGrob
@sahithi-nukala
@Rahul-Sutariya
@mikehaller
@Thomas-Mikhael
@mina-hamdi
@Abhishek2581
@NEOatNHNG
@dasoho
@kalu-an
@bharatGoswami8
@aelabyad
@oeweda
@esrour
@FScholPer
@alexandruiulian10
@esrour99
@LittleHuba

Agenda

1. Communication release 0.1.3
2. Status of GenericSkeleton @NEOatNHNG
3. Who wants to join the SomeipGateway discussions @NEOatNHNG
4. Continuation of CommonAPI discussion
5. PR status @FScholPer
6. Validation rules for configuration @JochenSatETAS

Minutes

to 1.

Release is yanked. Do not use it because of significant quality issues.
We are working on a new release that will go into a 0.6.1

to 2.

• PR is split and the raised version for review is for events only
• Review pending

to 3.

https://sdvworkinggroup.slack.com/archives/C0A9V1EBU1Z

Request to have a regular update in this round to have everybody aware of current progress.

Current status:

• QNX8 support is merged (gateway can be built for QNX8)
• Infrastructure setup ongoing but good progress
• SOCOM proposed to decouple

to 4.

Quick recap from @LittleHuba

Q: Who currently maintains CommonAPI? Security patches, fixes? @FScholPer
A: No actual maintenance in COVESA. Hard fork.

Q: Are there any feature increments from this? @FScholPer
A: To our knowledge no, it is only a discussion of flavor of the API.

Q: Does CommonAPI have a concept of mixed criticality? @LittleHuba
A: No concept in the frontend -> Up to the binder -> Copy-based reception (zero copy via extension with ShareableBuffer)

Q: Who would be interested to have CommonAPI in S-CORE?
A:

1. Valeo (+1, based on proposal)
2. MB (-1, no benefit in regard to the roadmap of S-CORE @FScholPer)
3. BMW (-1, no interest in porting our applications to a different API @LittleHuba)
4. ETAS (-1, preexisting applications use ara::com @NEOatNHNG)

=> Switch to CommonAPI frontend is declined

If binders or API changes are of interest, we are open for contributions.

to 5.

• PRs will be checked within the next days (still stabilizing CI)
• Stale draft PRs must be checked for staleness

to 6.

Rules are derived from projects at BMW.
In case of questions you can also look at ConfigDaemon and our examples.