Communication CFT Weekly [2025-11-03]

[LittleHuba]

Participants

@LittleHuba
@darkwisebear
@arsibo
Haller Mike
Abhishek Goyal
@lurtz
@SebastianGrob
@JochenSatETAS
@ZoranCutura
@dasoho
Taenzer Michael
Mittag Andreas
@crimson11

Agenda

• Adaptations necessary for Release 0.5 (raised by Mittag Andreas)
• IAM (raised by Mittag Andreas)
• completion of functionality e.g. methods (raised by Mittag Andreas)
• How do we handle feature modifications Cross-VM IPC (#916) #1371 (raised by @FScholPer)
• Contributions for Architecture Workshop

Meeting Minutes

Contributions for Architecture Workshop

#1571

Aumovio/Elektrobit

https://github.com/Elektrobit/inc_gateway

Qorix

eclipse-score/inc_someip_gateway#1

ETAS

Contribution is not yet published

Adaptations necessary for Release 0.5

• Reference integration is set up now but outdated (uses old git hashes for modules)
• Integration team will reach out if they need further help when updating

IAM

Motivating discussion: eclipse-score/communication#74

No support to forbid a process from offering specific services

• Usecase: DOS attack prevention
• Feature modification driven by @JochenSatETAS

Restrict accessibility of service interface to only parts of the offered communication elements

• This is not easily feasible with the communication pattern of LoLa
• Smells like a wrong cut on the service interface, so we vote against supporting this feature

Completion of functionality e.g. methods

https://github.com/orgs/eclipse-score/discussions/1948#discussioncomment-14855543
Feel free to comment in above discussion or open a new discussion in the module

Other feature gaps will be closed with v1.0

Other open features can be seen here: https://github.com/eclipse-score/score/issues?q=is%3Aissue%20state%3Aopen%20label%3Aft%3Acommunication

How do we handle feature modifications

Process documentation:

https://eclipse-score.github.io/process_description/main/process_areas/change_management/guidance/change_management_guideline.html#gd_guidl__change_change_request

https://eclipse-score.github.io/process_description/main/process_areas/change_management/change_management_getstrt.html#general-workflow

Basic steps (please verify in process documentation):

• Search the existing feature request/component request

• Open a PR on the this existing request

• Describe your modification in the request (including background, use case)

• In the PR description include further background that should not go into the request but helps with reviews

• Request review on the PR from the codeowners

• Codeowners will review PR and either request changes or approve or close

• Once PR is merged, tickets will be created or call for contribution will be started to close the feature gap

Rust API meeting

Next meeting scheduled for next week
Agenda to be published by @darkwisebear
If interested, reach out to @darkwisebear via Slack or a comment below this discussion