Communication CFT Weekly [2026-02-16]

[LittleHuba]

Participants

@SebastianGrob
@mikehaller
@Abhishek2581
@sahithi-nukala
@Tejveerpratap2803
Vadim Selinger (Qualcomm)
@bharatGoswami8
@darkwisebear
@Rahul-Sutariya
@NEOatNHNG
@alexandruiulian10
@LittleHuba

Agenda

1. Missing requirements for components @SebastianGrob
2. Request for sparring partner to create benchmarks @SebastianGrob
3. Sparring session refactoring of runtime configuration @SebastianGrob
4. Request for presentation of CommonAPI @mina-hamdi
5. Generic skeleton status update @mikehaller
6. Interest to support IEEE1722 @mikehaller

Meeting Minutes

to 1.

Component requirements are available here: https://github.com/eclipse-score/communication/tree/main/score/mw/com/requirements/component_requirements

These requirements are written in TRLC. For more information please contact @hoe-jo

to 2.

Benchmarks created for comparison with other communication framework.
Request to discuss/review the benchmark to validate the implementation.
Overall goal: Investigation whether some concepts from the other framework would benefit mw::com/LoLa
Meeting to be set up with @SebastianGrob and George

to 3.

Current status: Investigation ogoing to find all validation rules to clean up/simplify the validation phase.
Meeting to be set up to discuss the current findings.
@LittleHuba to reach out to @SebastianGrob

to 4.

Interested participants: @mikehaller @Abhishek2581 @Tejveerpratap2803 @Rahul-Sutariya @alexandruiulian10 @sahithi-nukala Ahmed ElAbyad @LittleHuba

Meeting will be set up by @LittleHuba next week

to 5.

Discussion requiring input from Maintainer side:
eclipse-score/communication#140 (comment)
@LittleHuba to set up meeting to discuss in person

Abhishek2581 to resolve conversations that are finished to have a clearer picture of open discussions.

Request to separate feature into event and field support. Split pending investigation on whether above discussion has impact.
If no impact directly split and raise PR for event support.

SomeIP Gateway currently blocked on this PR. Event support would unblock them (@NEOatNHNG)

to 6.

Company representatives take this topic with them and clarify whether an implementation in S-CORE is of interest.
Feedback by next Monday.