Repository navigation
README: 8.11.2.1 step 24 conflicts with 1815-2012's rule 16 - #71
Merged
Merged
Conversation
The standard requires the deferral the procedure's step 24 doesn't allow, and the tool accepts a deferred answer only within the response timeout plus 200 ms. See #1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The known-limitations entry said IEEE 1815's state table would let a device defer the READ in 8.11.2.1 step 24. 1815-2012 4.6.6 rule 16 requires the deferral. The entry and the code comment now say so, name 3.1r1's id (8.11.2a), and note that the tool waits for the answer for the response timeout plus 200 ms, so a device that defers passes only if its unsolicited confirm times out first. See #1.