🏗 Leshan 2.0 : LWM2M 1.1 🚧 #563
Comments
|
Hi Bernard I would be very interested in the newly introduced Non-IP binding for NB-IOT, where we can use 3GPP SCEF to carry LwM2M traffic, though the spec is released, however a reference design regarding how to integrate with T8 interface would be a good start for us to contribute BR/Vincent |
|
As a part of a joint project with Ericsson about contributing OSCORE to Californium we at RISE have also been working on using OSCORE in Leshan, as OSCORE is part of LWM2M 1.1. Currently we have code produced for enabling communication over OSCORE between the Leshan server, bootstrap server and client. In addition we have added support to bootstrap a client so it receives information to generate an OSCORE context for communication with the Leshan server. We would be interested in contributing this code to Leshan. |
|
@wenzheng, sry for the delay response, I have no experience about NB-iot but I suppose the first step must be to have a way to make CoAP and DTLS working over NB-IOT in Java. In a californium context that means create new @rikard-sics, That's a good news to know we could get a new contribution from RISE. :) But I ask myself how we could handle this because as explained we plan to firstly release a 1.0.0 of Leshan which supports LWM2M v1.0.x. (so without 1.1 feature) Maybe we could integrate this in another branch of Leshan which would aim to support LWM2M v1.1. |
|
It seems there is some interests about Observe-Composite and Cancel Observation-Composite at eclipse-californium/californium#881. |
Yes it could make sense to put it in a separate LWM2M 1.1 branch since OSCORE is not part of LWM2M 1.0.x
Actually the contribution is not that big since we made it very targeted on providing OSCORE support. Since the actual code for OSCORE communication is in Californium, for Leshan it was more about adding code to use it.
This work is part of a joint project with Ericsson and for the future we have the ambition to continue to use and support this code. |
|
We at HPE are interested in developing 1.1 features like CBOR, Composite Read,Write,Observe., Bootstrap trigger and Non-IP transport. We will start a new branch and contribute in coming days. |
|
@yemkay : i would like to request you, please share further information once 1.1 feature available to use |
Just to come back to this regarding OSCORE in Leshan. Would it be fine if we made a pull request with the code we currently have putting it into a separate branch of Leshan? I suppose such a branch would have to be created first? |
|
@rikard-sics I created a 2.0.x branch and its jenkins job. I suppose you need OSCORE feature from Californium, so the first step will be to wait for a Californium v2.0.0M14, right ? |
Thanks a lot for creating the branch. I see that Californium 2.0.0-M14 has now been released. I will proceed with making smaller pull requests with parts of our code as you requested. |
|
@rikard-sics , just to let you know I plan to create a PR to integrate Californium 2.0.0-M14 this afternoon. |
|
@rikard-sics branch 2.0.x is ready with cf 2.0.0-M14. |
|
@rikard-sics oops not so ready, build failed because of new legal bundle in californium. I will try to fix it. |
|
@rikard-sics this time it's really OK. |
Thanks for setting up the branch. I will proceed with the pull requests in steps as you mentioned. |
|
Is there any estimated time frame as to when lwm2m 1.1 is supported? |
Question : what means "LWM2M 1.1 is supported" ? Do you mean full support of all defined features.. Even for 1.0 we didn't cover 100% of the specification. So you should ask yourself which part of the specification you need and share this with us. This could help to define priorities ! Anyway, I will not be able to give you any date. This is just the beginning for 1.1 implementations. Some contributors just started to work on this. Personally, I'm focus on the version 1.0.x. and maybe I will be able to start to develop some 1.1 features at the end of the year. All the work about LWM2M 1.1 is available in branch 2.0.x. |
|
Is OSCORE available in branch 2.0 now ? Thanks. |
There is an open pull request to add support for OSCORE communication between a Leshan client and server to the 2.0.x branch here: |
|
@sbernard31 , @rikard-sics , do you know the progress to implement "Send" Operation defined in LwM2M 1.1? Has it been implemented, or is someone working on it now? Thanks. |
|
Thanks for update, i will check it out, i have no idea for now what it is) |
|
A first try about supporting |
|
A new milestone release containing new LWM2M 1.1 features is out : 2.0.0-M3. ❗☠️❗ Affected by security issue❗☠️❗ |
|
A new milestone release containing new LWM2M 1.1 features is out : 2.0.0-M4. 🎉 Please do not hesitate to test and give us feedback. 🙏 ❗☠️❗ Affected by security issue❗☠️❗ |
|
A new milestone release containing new LWM2M 1.1 features is out : 2.0.0-M5. 🎉 We still take feedback about the release or the needed features. 🙏 (see comment just above ☝️) Next release (M6) will be about cleaning (like removing old UI demo, keeping only one JSON or CBOR lib, more feature in demos, some code cleaning or more little missing feature about LWM2M v1.1 ...) Then for M7, we will probably try begin to work on one of the bigger task: refactoring code to allow ❗☠️❗ Affected by security issue❗☠️❗ |
|
I forgot to mention that M6 should also be the first release which will be built with java 8 ( see #924) (until now that was java7) |
|
Great, thanks
|
|
A new milestone release about LWM2M 1.1 support is out : 2.0.0-M6. 🎉 About M7, next tasks should be about :
Adding more transport Layer (#1025) will probably be delaied to M8. ❗☠️❗ Affected by security issue❗☠️❗ |
|
|
|
A new milestone release about LWM2M 1.1 support is out : 2.0.0-M7. 🎉 This 2.0.0-M7 contains About M8, next tasks should be about :
About OSCORE, there is testable demos in ❗☠️❗ Affected by security issue❗☠️❗ |
|
A new milestone release about LWM2M 1.1 support is out : 2.0.0-M8. 🎉 Main focus for M9 : Adding more transport Layer (#1025) ❗☠️❗ Affected by security issue❗☠️❗ |
|
Maybe I missed it, but for now, there is now schedule day for a 2.0.0 release? |
|
Correct, there is no release day scheduled. I think mandatory feature for 2.0.0 is at least #1025 and I guess this will be a long task to do. If one or more major release of californium is released during the development phase of Leshan 2.0.0 we will integrate it as soon as possible. If needed, I can let you know when will be soon of a 2.0.0 release. |
|
A new milestone release about LWM2M 1.1 support is out : 2.0.0-M9. 🎉 See : https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39368 Main focus for M10 : Adding Transport Layer Abstraction (#1025) ❗☠️❗ Affected by security issue❗☠️❗ |
|
A new milestone release about LWM2M 1.1 support is out : 2.0.0-M10. 🎉 This should be the last milestone release before massive changes about Transport Layer Abstraction. Lot of the new API is already in If you are using Leshan 2.0.0-Mx or if you are curious about those changes, 📢 we strongly encourage you to take a look at #1025 (comment) 📢 ❗☠️❗ Affected by security issue❗☠️❗ |
|
A new milestone release about LWM2M 1.1 support is out : 2.0.0-M11. 📢 : This is first Milestone Release containing new Transport Layer Abstraction (GH-1025). This is massive changes and maybe not yet fully mature. So please read ❗☠️❗ Affected by security issue❗☠️❗ |
|
A new milestone release about LWM2M 1.1 support is out : 2.0.0-M12. 📢 : This is second Milestone Release containing new Transport Layer Abstraction (GH-1025). This is massive changes and maybe not yet fully mature. So please read ❗☠️❗ Affected by security issue❗☠️❗ |
|
A new milestone release is out : 2.0.0-M13. 📢 : This mainly a security fix of 2.0.0-M12, please read release description |
|
A new milestone release is out : 2.0.0-M15. 📢 : Thx to new Transport Layer Abstraction (GH-1025), this release contains a very experimental CoAP over TCP (and TLS) provider based on java-coap. Please do not hesitate to try it and give us feedback. Next milestone (M16) should contain :
So a lot of classes will be moved and new maven module will be created but behavior should not changed. |
|
A new milestone release is out : 2.0.0-M16. 📢 : As plan this release is mainly about new maven module refactoring, so a lot of classes was moved and new maven module was created/renamed but behavior should not have changed. See Module Name and API Break. This is strongly recommended to migrate to this version before to migrate to future 2.0.0-M17. |
|
any plan for M17? I'm mainly interested in the Californium upgrade which fixes a memory leak |
I created a dedicated issue about that : #1670 |
|
A new milestone release is out : 2.0.0-M17. |
Leshan v2.0.0 (master branch) is currently in development and aims to support LWM2M 1.1 (or at least some part of it).
You can have a look to currently supported or in development features or current roadmap.
If you are interested in LWM2M 1.1 support in Leshan, we strongly advice to :
This is the best way to get a final 2.0.0 release which fit your needs.
(If you need stable API and are fine with LWM2M v1.0, you should use Leshan v1.x)
The text was updated successfully, but these errors were encountered: