I’ve completed my work for SenML-CBOR support. I ended up writing my own parser/serializer because cn-cbor was requiring too much RAM.
Regards,
Scott
Scott Bertin |
Sr Firmware Engineer |
P: +1 678-264-2042 | C: | Scott.Bertin@xxxxxxxxxx |
3225 Cumberland Boulevard Suite 300 | Atlanta | GA 30339 | Telular.com |

From: wakaama-dev-bounces@xxxxxxxxxxx <wakaama-dev-bounces@xxxxxxxxxxx>
On Behalf Of Scott Bertin
Sent: Friday, July 19, 2019 11:31 AM
To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
Subject: Re: [wakaama-dev] LWM2M 1.1 next steps
***NOTICE***
This came from an external source. Use caution when replying, clicking links, or opening attachments.
I’ve completed the Read-Composite and Send operations. They can be found in
https://github.com/sbertin-telular/wakaama/tree/lwm2m_1.1.
Here is what I see still needs to be implemented (no particular order):
- New attributes (Minimum/Maximum evaluation period) and attributes at the resource instance level. Attributes as a whole could use a rework to be compliant.
- Write-Composite. With the current Wakaama design I’m not sure this can be implemented atomically.
- Observe-Composite
- Cancel Observation-Composite
- TCP binding. David Navarro has said (wakaama-dev
2/20/2019) that he has already implemented it, but it hasn’t been released yet.
- LWM2M 1.1.1 compatibility changes
- New optional resources in objects for the client example
- OSCORE. David Navarro has said (wakaama-dev
2/20/2019) someone is working on this.
- SenML-CBOR. Ideally this would be based on whatever CBOR is used for the OSCORE support to prevent having multiple CBOR parsers/serializers.
- Enforcing access control. LWM2M 1.1.1 makes this optional for an “Access Control-Disabled” configuration where only 1 server is supported.
For my immediate needs all that is missing is SenML-CBOR support. I plan to implement SenML-CBOR support based on cn-cbor, which I am already using. I understand that the license may or may not be acceptable to the Eclipse Foundation, so
it may not ever get merged into Wakaama.
After that I will be taking a break from Wakaama development to merge all the latest changes into my codebase. When pull requests start getting feedback/merged into Wakaama again I’ll support them and getting my latest changes merged cleanly.
Regards,
Scott Bertin
