-
Notifications
You must be signed in to change notification settings - Fork 2k
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
doc: Extend and take responsibility for 802.15.4 security roadmap #20123
Conversation
This copies the version of 2020-05-29, with only the header line added.
5ea3f5b
to
30635ad
Compare
2. discuss mid- and long-term plans for network stack maintenance & development (GNRC vs other supported stacks) | ||
3. Support for CoAP blockwise transfer, observe. Also see [Ken's](https://github.com/kb2ma) unofficial [CoAP for RIOT](https://github.com/kb2ma/RIOT/wiki/CoAP-Home) page. | ||
4. revisit network time synchronization | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here and below: more than two lines between sections?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've unified it to 2 empty lines between subsections and kept the 3 empty lines between top levels (as it was in the wiki).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK. feel free to unify emty lines. :)
30635ad
to
5542ecd
Compare
Contribution description
This puts details to, and answers questions currently open in, the road map around 802.15.4 security.
While I won't fix that alone, I think it makes sense to place myself as the person coordinating this.
Issues/PRs references
This is an example of the changes in the direction discussed during the 2023.11 VMA, and a follow-up to #20122
Depends on #20122