Skip to content

Clarify that RSH3h isn't meant to re-initialise the device#494

Open
lawrence-forooghian wants to merge 1 commit into
mainfrom
clarify-RSH3h-conditional-initialization
Open

Clarify that RSH3h isn't meant to re-initialise the device#494
lawrence-forooghian wants to merge 1 commit into
mainfrom
clarify-RSH3h-conditional-initialization

Conversation

@lawrence-forooghian

Copy link
Copy Markdown
Collaborator

RSH8a says "The LocalDevice is initialised when first required" but it doesn't say "only when first required"; Marat pointed out that RSH3h could arguably be interpreted as meaning "perform this initialisation process again". (I'm on the fence and think that "initialisation" implies a one-off thing, but no harm in clarifying.)

RSH8a says "The LocalDevice is initialised when first required" but it
doesn't say "only when first required"; Marat pointed out that RSH3h
could arguably be interpreted as meaning "perform this initialisation
process again". (I'm on the fence and think that "initialisation"
implies a one-off thing, but no harm in clarifying.)

@maratal maratal left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RSH8a says "The LocalDevice is initialised when first required" but it doesn't say "only when first required"; Marat pointed out that RSH3h could arguably be interpreted as meaning "perform this initialisation process again". (I'm on the fence and think that "initialisation" implies a one-off thing, but no harm in clarifying.)

I'm a bit confused by this wording, all I was trying to say is that the device can be (and actually is for identified clients) initialized elsewhere (not upon state machine init) and thus automatically violating RSH3h. So loosing this requirement would make things easier for the current implementations. The change itself is fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants