Thanks a lot for the informative reply. This is a useful set of documents.
On Tue, Dec 20, 2016 at 10:18 AM, Prakash Karthikeyan < prakash.karthikeyan at smartron.com> wrote: > Hi Kaled, > > Please find replies In-line. > > Thanks, > Karthikeyan Prakash, > Software Engineer, > > > > On Tue, Dec 20, 2016 at 12:55 PM, Khaled Elsayed <khaledieee at gmail.com> > wrote: > >> Hi, >> >> I am trying to gather some information on the security features in >> iotivity. I know DTLS is used, but is there anything like authorization >> from devices when they are discovered? Is any client capable of discovering >> whatever device running the stack? Is there a document that explain >> iotivity security with some good details? >> > > IoTivity Secured Servers can be discovered by any Secured Clients. There > is nothing like authorization to check whether it is authenticated device. > The next step after discovery is OT (Ownership Transfer). This Document ( > https://openconnectivity.org/wp-content/uploads/2016/01/Habib-Virji.pdf) > can provide you details about overall architecture and building/running > samples. > > http://events.linuxfoundation.org/sites/events/files/slides/ > LinuxConEU2015_IoTivitySecurity_0.pdf > Provisioning - https://wiki.iotivity.org/provisioning > >> >> Also, this Internet Draft https://tools.ietf.org/html/dr >> aft-ietf-core-object-security-01 just came out and it proposes using >> CBOR for application layer security. I know CBOR is used in the iotivity >> stack, so is this ID along the same line of thought in iotivity or is the >> model different? >> >> CBOR is essentially used in IoTivity to encode the payload it also used > in store/retrieve the credentials, Device details etc.,. People here can > give you more precise details in CBOR in IoTivity > > > >> Best regards, >> >> Khaled >> >> >> >> _______________________________________________ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> >> > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161220/2620cd53/attachment.html>
