Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process when one service removed pairing/registration #2

Open
DerAndereAndi opened this issue May 29, 2023 · 0 comments
Open

Process when one service removed pairing/registration #2

DerAndereAndi opened this issue May 29, 2023 · 0 comments

Comments

@DerAndereAndi
Copy link
Member

DerAndereAndi commented May 29, 2023

Assume two services both successfully paired/registrated with each other. Now service 2 removes this pairing/registration, as service 1 still has that information it will immediately re-connect. Service 2 is still able to accept the pairing/registration request and will stay in state Hello_Pending_Listen.

Service 1 can't know if trust was removed or if there was some other kind of error, e.g. WIFI connection loss.

Is this the desired behavior or should this be different. I can't find any reference to this scenario in the spec.

@DerAndereAndi DerAndereAndi transferred this issue from enbility/eebus-go Jan 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant