Re: [wakaama-dev] Wakaama client flow and bootstrap

["Kalley, Vibhor" <Vibhor.Kalley@xxxxxxxxx>]

Hi Rajesh,

1) In the client implementation(lwm2mclient.c), I have noticed that the client uses hardcoded values for security, access control, server objects.
What will be the proper flow, if hardcoded values are not used?

Lwm2mclient is an example client, but you can write your own client with values which makes sense for  your setup.
In bootstrap mode the bootstrap server can have a config for your client, which dictates the values  your client can have after registration. Bootstrap server can delete and create objects with values according to the config for your particular client.
If you are using the wakaama bootstrap server you can put the configuration for your endpoint in /bootstrap_server/bootstrap_server.ini file.

2) My understanding about bootstrap process is :
Bootstrapping is used to fetch security and access control object from bootstrap server. Is this the only use of bootstrapping? Is bootstrapping related to DTLS ?
    If bootstrap server is different from the LWM2M server, how does the bootstrap server know about the details like access control,serverid of LWM2M server ?

I found this article  from Julien useful when I was learning about bootstrapping . Take a look might help you too:
https://medium.com/@vrmvrm/device-key-distribution-with-lightweight-m2m-36cdc12e5711#.tv2l323ox

This article was written some time ago so some of the information might not be accurate, but it's a good starting point.

Regards
Vibhor


-----Original Message-----
From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx] On Behalf Of wakaama-dev-request@xxxxxxxxxxx
Sent: Monday, April 18, 2016 9:00 AM
To: wakaama-dev@xxxxxxxxxxx
Subject: wakaama-dev Digest, Vol 21, Issue 9

Send wakaama-dev mailing list submissions to
wakaama-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/wakaama-dev
or, via email, send a message with subject or body 'help' to
wakaama-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
wakaama-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than "Re: Contents of wakaama-dev digest..."


Today's Topics:

   1. Wakaama client flow and bootstrap (RAJESH KUMAR S.R)


----------------------------------------------------------------------

Message: 1
Date: Mon, 18 Apr 2016 12:01:22 +0530
From: "RAJESH KUMAR S.R" <rajuuu1992@xxxxxxxxx>
To: wakaama-dev@xxxxxxxxxxx
Subject: [wakaama-dev] Wakaama client flow and bootstrap
Message-ID:
<CAC-BHbU69dEUPyO39ymuEE=p7Wv2PJnb1eQ-DNhED6Ui7kkM+A@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Hi,

I am new to LWM2M and wakaama.
I have few doubts regarding initial client registration.

1) In the client implementation(lwm2mclient.c), I have noticed that the client uses hardcoded values for security, access control, server objects.
What will be the proper flow, if hardcoded values are not used?

2) My understanding about bootstrap process is :
Bootstrapping is used to fetch security and access control object from bootstrap server. Is this the only use of bootstrapping? Is bootstrapping related to DTLS ?
    If bootstrap server is different from the LWM2M server, how does the bootstrap server know about the details like access control,serverid of LWM2M server ?


Thanks & Regards,
Rajesh kumar S R
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/wakaama-dev/attachments/20160418/f96bb66c/attachment.html>

------------------------------

_______________________________________________
wakaama-dev mailing list
wakaama-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wakaama-dev

End of wakaama-dev Digest, Vol 21, Issue 9
******************************************
________________________________
NOTICE OF CONFIDENTIALITY:
This message may contain information that is considered confidential and which may be prohibited from disclosure under applicable law or by contractual agreement. The information is intended solely for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the information contained in or attached to this message is strictly prohibited. If you have received this email transmission in error, please notify the sender by replying to this email and then delete it from your system.