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

Relax the object role persistence requirement across reboots. #64

Open
cristian-recoseanu opened this issue Nov 20, 2024 · 0 comments
Open

Comments

@cristian-recoseanu
Copy link
Contributor

Objects in MS-05-02 currently have a requirement to persist their role across device reboots.

This requirements is mentioned once in the NcObject document:

The `role` is a structural identifier which MUST be persisted across restarts.

And again in the context of a role path within a nested block hierarchy in the Blocks document:

An object in a hierarchy of nested blocks MUST be uniquely identified by its role path which MUST be persisted across device reboots.

The feedback from vendors is that this requirement should only apply for the same software version of that device. In other words vendors should be allowed to make structural changes when they upgrade their device to a new software version.

This would require those two sentences to be further qualified to only apply the requirement within the same software version/device revision.

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