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

Review of draft-ietf-core-conditional-attributes-10 #53

Open
bsilverajan opened this issue Jan 27, 2025 · 0 comments
Open

Review of draft-ietf-core-conditional-attributes-10 #53

bsilverajan opened this issue Jan 27, 2025 · 0 comments

Comments

@bsilverajan
Copy link
Collaborator

From https://mailarchive.ietf.org/arch/msg/core/JFK9bJOBiZfP_TNFgcWUMOWOf0c/

*Q4:*Is it correct to assume that Conditional Notification Attributes,
Conditional Control Attributes and other query parameters can be present
in the same query? Is there some order in the evaluation? maybe this
does not matter as all of them have to be valid anyways? For example,
the example below:

|REQ: GET
coap://coap.me:5683/sensor?precision=0.1&c.band&c.gt=30&c.con&|c.pmax=10

  • |precision=0.1|: application specific, indicates precision of|0.1|.
  • |c.gt=30|: This parameter sets a threshold, indicating that a
    notification should be triggered when the resource value exceeds 30.
  • |c.band|: Modifier of|c.gt|parameter. It is alone so it sets an
    upper bound. We will get notifications that are less than 30.
  • |c.con|: This parameter indicates that the notification must be
    confirmable, requiring an acknowledgment from the client.
  • |c.pmax|: This parameter indicates that we should get notifications
    at least every 10 seconds.
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