Skip to content
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

Bootstrap server with shortServerId #88

Closed
boaks opened this issue Feb 29, 2016 · 8 comments
Closed

Bootstrap server with shortServerId #88

boaks opened this issue Feb 29, 2016 · 8 comments
Labels
bug Dysfunctionnal behavior

Comments

@boaks
Copy link

boaks commented Feb 29, 2016

According the LWM2M TS, E.2

"A Bootstrap Server has no such an Object Instance associated to it."

So the shortServerId should be 0.
(When functions as "queue mode" or "sms" gets relevant also for the bootstrap, the TS may be required to be fixed :-) .)

@sbernard31
Copy link
Contributor

The Spec say that there is no LWM2M Server instance for bootstrap server.
In other words, all instances of LWM2M Server aren't related to a bootstrap server.
So why should we set the shortServerId to 0 ?

@boaks
Copy link
Author

boaks commented Mar 2, 2016

Because the 0 indicates in my opinion, that there is no related LWM2M Server.
A value different from 0 may be seen as something like a "wild pointer".

@sbernard31
Copy link
Contributor

We talk about the §E.2 right ? I mean the object 1, resource 0 ?
So we are in the LWM2M Server object, here we don't have instance related to bootstrap server.
But we always need a link to the Security(0) object. (to know server URI, credentials ..)

@boaks
Copy link
Author

boaks commented Mar 2, 2016

Uups, my issue was missleading, sorry!
I ment the shortserverid in the lwm2m security object (0/?/10).
The demo client uses:
initializer.setInstancesForObject(SECURITY, noSecBootstap(serverURI, 123));
so it creates a security object with 123 as shortserverid.

@sbernard31
Copy link
Contributor

So we can close this bug ? :)

@boaks
Copy link
Author

boaks commented Mar 2, 2016

Hm, though the security object for a bootstrap server uses a shortserveid other then 0, I would say this is a bug. Or what should be the "meaning" of a shortserverid 123 for a bootstrap server security object?

@sbernard31
Copy link
Contributor

Ok I re-read the short server id resource description in the security object :
"This identifier uniquely identifies each LWM2M Server configured for the LWM2M Client. This Resource MUST be set when the Bootstrap Server Resource has false value. Default Short Server ID (i.e. 0) MUST NOT be used for identifying the LWM2M Server."
So I think you're right the security object corresponding to the bootstrap server should always have a short server id set to 0.
We need to change static constructors about bootstrap server by removing the shortID attribute.

@sbernard31 sbernard31 added the bug Dysfunctionnal behavior label Mar 2, 2016
@sbernard31
Copy link
Contributor

Fix in master (commit 2e6122b)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Dysfunctionnal behavior
Projects
None yet
Development

No branches or pull requests

2 participants