-
The TS 20150228 mentions in E1.1.2
„Thus the Certificate Resource would contain a 32 byte public key and the Secret Key Resource a 32 byte private key.“
But ECC uses two public keys (“x” and “y”) each…
boaks updated
8 years ago
-
Hi,
I use http://leshan.eclipse.org/ and observed next issue:
when server creates new obj.instance, for example, /10255/777, server puts instance id 777 in the payload (instead option "Uri path" as wa…
-
The spec marks the resources like **Manufacturer, Hardware version, Firmware version, Software version** etc, as *_optional_.
However from a management server perspective, these attributes are critic…
-
I have a device which subscribes to configuration value "luminosidad", but each time I deploy new software, I restart the IoTA MQTT (which is configured to memory instead of mongodb), I do the device …
-
It appears currently the specification doesn't specify behavior for the below case. Please consider specifying the behavior in the below.
1. DTLS secured lwm2m client registration succeeds.
2. Lwm2m s…
-
Can you please push the repo to the official Fiware DockerHub: https://hub.docker.com/u/fiware/.
While we can find LWM2M agent (https://hub.docker.com/r/fiware/lightweightm2m-iotagent/), MQTT agent i…
-
TS, section 7.1.1 Pre-Shared Keys.
According to OMA LwM2M `TLS_PSK_WITH_AES_128_CBC_SHA256` is mandatory. However in CoAP [RFC7252], only `TLS_PSK_WITH_AES_128_CCM_8` is mandatory. And the same in t…
-
According the TS the registration contains
```
"The list of Objects supported and Object Instances available on the LWM2M Client".
```
That list for the example client of Appendix F) is:
```
, , …
boaks updated
8 years ago
-
OMA-TS-LightweightM2M-V1_0-20160202-D:
page 66, table 23.
The create operation still contains a "instance id", though
page 33, table 14.
doesn't contain it any longer.
boaks updated
8 years ago
-
Figure 23,
update registration`PUT /rd/5a3f` should be `POST`
boaks updated
8 years ago