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

Use OBR.3 and OBR.29 to identify device association for any action (association, disassociate, correction, wrong, update) in DEV-52 messages #99

Closed
eldonmetz opened this issue Apr 26, 2024 · 0 comments · Fixed by #103

Comments

@eldonmetz
Copy link
Collaborator

Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2)

Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem.

Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.

Priority:

  • High: Important issue where there is major issue to be resolved. Requires discussion and debate.
  • Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.
  • Low: Typo or other minor classification that an editor can manage. Requires no group discussion.
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

Successfully merging a pull request may close this issue.

1 participant