-
Notifications
You must be signed in to change notification settings - Fork 25
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
Event Binding for CoAP Multicast #43
Labels
coap
related to coap protocol binding
Has Use Case Potential
The use case can be extracted and explained
Needs discussion
question
Selected for Use Case
Comments
Is there any further comments on this question? |
I think we should try this out first in PlugFests. |
On September 20 in Fukuoka, it was pointed out that although this is worth discussing further, the IG/WG should incubate first. See minutes here. |
@ektrah has mentioned that there is activity on this in the IETF ACE and CoRe working groups. |
With @ektrah we have identified 3 use cases of CoAP Multicast:
|
egekorkan
added
Has Use Case Potential
The use case can be extracted and explained
Selected for Use Case
labels
Jan 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
coap
related to coap protocol binding
Has Use Case Potential
The use case can be extracted and explained
Needs discussion
question
Selected for Use Case
CoAP devices may emit events by POSTing to a specific multicast address + well-known path.
This information can easily packed into a TD. Question is if that multicast address should go into
href
or rather the mechanism how to join the multicast group.The text was updated successfully, but these errors were encountered: