Here is information about the new forum/working group
https://www.connectedhomeip.com/
On Thu, Dec 19, 2019 at 10:38 AM Khaled Elsayed via Lists.Iotivity.Org
wrote:
> Yes Clarke, I agree that OCF has this today but for some reason those big
> 3 have been trying to each get its own system
standard.
On Wed, Dec 18, 2019 at 11:17 PM Clarke Stevens
wrote:
> OCF/IoTivity has virtually identical goals and already enables this. It
> would be nice if Amazon, Apple & Google would work with OCF rather than
> start from scratch.
>
> -Clarke
>
> On Dec 18, 2019, at 2:06
So, how many times have we heard this over the past 5 or 6 years from
different consortium, forums or standardization bodies :-)?
“customers can be confident that their device of choice will work in their
home and that they will be able to setup and control it with their
preferred system,” the com
You have to specify and design what functionality your framework wants to
support over iotivity/ocf.
On 2 May 2019 4:59 pm, "Alban JAMES" wrote:
> Hi Dear,
>
> I am Alban, a Master student at Kookmin University in Seoul, Korea.
> In the scope of my work, I was entrusted with my mates the task of
Thanks Achim for sharing. This is an interesting development. Hope the
iotivity cloud team will adopt/experiment with this approach.
On Mon, Apr 15, 2019 at 3:40 PM Achim Kraus wrote:
> Dear iotivity-dev list,
>
> searching in the web about the usage of CoAP for cloud scenarios, I
> stumbled o
Hi all,
I would like to share the first version of ble-ocf-bridge. It is available
via github https://github.com/kelsayed/ble-ocf-bridge
This package provides a node.js based bridge for interconnecting devices
with Bluetooth low energy (BLE) profiles to OCF based clients. It is based
on iotivity
Do you mean non-link local IPV6 address on a local network? I think it
works.
Otherwise you would need to use the cloud model if you mean global in the
sense of any where in the Internet/Intranet.
BR,
Khaled
On Wed, Jan 30, 2019 at 5:35 PM SOURAV BHUWALKA
wrote:
> Hii,
>
> Iotivity supports I
Hi Aleksey ,
I am actually using the second configuration. In the client I have added
this which the server root trustca
{
"credid": 3,
"subjectuuid": "*",
"credtype": 8,
"publicdata": {
"encoding": "oic.
Nathan
>
>
>
> *From:* iotivity-dev@lists.iotivity.org [mailto:
> iotivity-dev@lists.iotivity.org] *On Behalf Of *Khaled Elsayed
> *Sent:* Monday, January 7, 2019 8:24 AM
> *To:* iotivity-dev
> *Subject:* [dev] First Release of MQTT OCF Gateway (Bridge)
>
>
>
> Hi a
community feedback. Don't hesitate to
ask any questions via the mailing lists or by filing github issues
(preferred).
Best regards,
Khaled Elsayed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10133):
https://lists.iotivity.org/g/iotivit
Hi Nathan and all,
Sure, I just have one more issue to get DTLS hand-shake going through.
Once that is done, I will write a full tutorial with all the steps which
can be added to your tutorial or included in the IoTivity Getting Started.
I also found the document UNDERSTANDING OCF CERTIFICATES IN
certificates.
>
> "oic.sec.cred.mfgcert" and "oic.sec.cred.mfgtrustca" types used only at
> the otm process, and will never used then for authentication by default.
>
>
>
>
>
> *Best regards,*
>
> *Aleksey Volkov*
>
>
>
> - *Orig
f credentials.
>
> Could you share full log from the beginning and dat file of yours 3rd
> client, please?
>
>
>
> *Best regards,*
>
> *Aleksey Volkov*
>
>
>
> - *Original Message* -
>
> *Sender* : Khaled Elsayed
>
> *Date* : 2019-0
SIGNED_ASYMMETRIC_KEY type credential
> for your case). So, please check your dat file for necessary credential.
> entries.
>
>
>
>
>
> *Best regards,*
>
> *Aleksey Volkov*
>
>
>
> - *Original Message* -
>
> *Sender* : Khaled Elsayed
>
> *Date
(OC_CLIENT) mode instead of 'client-server'
> (OC_CLIENT_SERVER) to initialize the Iotivity stack.
>
>
>
> *Best regards,*
>
> *Aleksey Volkov*
>
>
>
> - *Original Message* -
>
> *Sender* : Khaled Elsayed
>
> *Date* : 2018-12-1
s to make sure your cbor files actually get
> read successfully. It could be something as simple as a bad path.
>
> Hth
>
> Gregg
>
> On Mon, Dec 31, 2018, 4:02 AM Khaled Elsayed
>> Hi Reporting on this:
>>
>>> So, I will re-visit this and test the followi
IC_CA_NET_SSL: In DeleteCacheList
56:55.797 DEBUG: OIC_CA_NET_SSL: Out DeleteCacheList
56:55.797 DEBUG: OIC_CA_NET_SSL: Out DeleteSslEndPoint
56:55.797 ERROR: OIC_CA_NET_SSL: *TLS handshake failed*
56:55.797 ERROR: OIC_CA_IP_ADAP: CAencryptSsl failed!
On Sun, Dec 30, 2018 at 3:57 PM Khaled Elsa
t the certificates in
DER format to fill the JSON files.
Let me know if there is anything else you need to restart on this.
BR,
Khaled
On Thu, Dec 27, 2018 at 10:40 PM Gregg Reynolds wrote:
>
>
> On Mon, Dec 10, 2018, 1:02 AM Khaled Elsayed
>> Hi Gregg,
>>
>> No unf
C_CLIENT) mode instead of 'client-server'
> (OC_CLIENT_SERVER) to initialize the Iotivity stack.
>
>
>
> *Best regards,*
>
> *Aleksey Volkov*
>
>
>
> - *Original Message* -
>
> *Sender* : Khaled Elsayed
>
> *Date* : 2018-12-10 1
red out?
>
> I've seen "*No ciphersuites configured**" but sadly don't remember how I
> resolved it.*
>
> *G*
>
> On Wed, Dec 5, 2018, 9:34 AM Khaled Elsayed
>> Hi,
>>
>> I am trying to get certificate-based credential management to work
&g
Thanks Gregg for your thoughtful replies. Some replies inline.
On Sun, Dec 9, 2018 at 10:14 PM Gregg Reynolds wrote:
> Hi Khaled,
>
> Nice note, thanks. Not to start an endless discussion, but:
>
>
> On Sun, Dec 9, 2018, 5:43 AM Khaled Elsayed ...
>
>> 1) The specs
I think the squeaky wheel will get the grease.
>
> I’m hoping companies will see the benefits of OCF and will develop
> products and provide resources around IoTivity and that the ecosystem will
> evolve to better support itself.
>
> Thanks,
> -Clarke
>
> On Dec 9,
red out?
>
> I've seen "*No ciphersuites configured**" but sadly don't remember how I
> resolved it.*
>
> *G*
>
> On Wed, Dec 5, 2018, 9:34 AM Khaled Elsayed
>> Hi,
>>
>> I am trying to get certificate-based credential management to work
&g
The article has some inaccuracies. That's for sure. However, there is a
problem with OCF/IoTivity market adoption. I am not involved with any
company developing and we use IoTivity in a research project. We selected
IoTivity as our framework mainly because of its technical superiority. The
promise
different Client
> certificates. But the Server does need to have a the Root Cert installed
> for the CA(s) that issued the Client cert. We call that Root Cert the
> “Trust Anchor” because it is the last point in the dotted line of items
> that form a logical chain of trustworthiness.
>
48:53.279 ERROR: OIC_CA_NET_SSL: Failed to set up cipher
48:53.279 DEBUG: OIC_CA_NET_SSL: In DeleteSslEndPoint
On Tue, Nov 27, 2018 at 9:16 AM Khaled Elsayed wrote:
> Thanks Mats for the pointer. Very handy tool. Nicely done Rami.
>
> Khaled
>
>
>
> On Mon, Nov 26,
have a the Root Cert installed
>> for the CA(s) that issued the Client cert. We call that Root Cert the
>> “Trust Anchor” because it is the last point in the dotted line of items
>> that form a logical chain of trustworthiness.
>>
>>
>> Hope that helps,
&g
Also, if you can clearly identify what is happening, please share your
findings. I had a look but still not totally clear about the exact
procedure.
On Wed, Nov 28, 2018 at 4:07 PM Khaled Elsayed via Lists.Iotivity.Org
wrote:
> This can be done via certificates. You can find the example
This can be done via certificates. You can find the example for the
provisionclient. I am still trying to figure out myself as it is not very
well documented. Quoting Nathan reply on my question sent last week or so.
There is indeed an example of Certificate-based Client/Server
authentication in th
Interesting. OCF has become an ISO international standard ISO/IEC 30118
https://apnews.com/f37088c65f194e43bc83d6b173f5f968
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10032):
https://lists.iotivity.org/g/iotivity-dev/message/10032
Mute This To
Thanks Mats for the pointer. Very handy tool. Nicely done Rami.
Khaled
On Mon, Nov 26, 2018 at 5:21 PM Mats Wichmann wrote:
> On 11/26/18 7:53 AM, Khaled Elsayed wrote:
> > Hi Nathan
> >
> > Just wanted to confirm that json2cbor from iotivity-2.0.0 and latest
> mast
if there is such a tool.
Thanks
Khaled
On Wed, Nov 21, 2018 at 9:56 AM Khaled Elsayed wrote:
> Thanks Nathan so much for the detailed responses. I was using the master
> branch which I believe is based on 1.4. I just downloaded 2.0.0 and will
> use it for the experimentation.
>
Thanks Nathan so much for the detailed responses. I was using the master
branch which I believe is based on 1.4. I just downloaded 2.0.0 and will
use it for the experimentation.
My replies below inline.
On Tue, Nov 20, 2018 at 8:40 PM Heldt-Sheller, Nathan <
nathan.heldt-shel...@intel.com> wrote:
As I posted earlier, I am working on a mqtt-ocf gateway. As a start, I am
trying to deploy security on the OCF side. The proxy creates resources
corresponding to the MQTT topics on the fly for both subscribe and publish
request if the topic is new. This works perfectly and I tested that OCF
clients
,
Khaled
On Mon, Nov 12, 2018 at 5:23 PM, Khaled Elsayed
wrote:
> Hi Nathan and all,
>
> So, if I would like to create a credential for a group all members of
> which can access a certain resource, I should create:
>
> {
> "credid": 1,
> "
Hi Nathan and all,
So, if I would like to create a credential for a group all members of which
can access a certain resource, I should create:
{
"credid": 1,
"subjectuuid": "12345678-1234-1234-1234-123456789012", /* The group uuid*/
"credtype": 2, /* symmetric group key */
"privatedata":
You can still grab an old version of zephyr and build iotivity-lite. Works
perfectly. I had it running on a Nordic NRF52 module.
On Fri, Nov 9, 2018 at 8:08 AM, Kishen Maloor
wrote:
> Hello,
>
>
>
> Thanks for your note.
>
>
>
> > I'm trying to port IoTivity-Lite server to zephyr.
>
> > But, It
ghtness?)
>
>
>
> PS: have you evaluated aedes? Mainflux uses that as their MQTT broker and
> it’s my understanding it was built to replace mosca.
>
>
>
>
>
> *From:* iotivity-dev@lists.iotivity.org [mailto:iotivity-dev@lists.
> iotivity.org] *On Behalf Of *Khaled Elsay
st>.
> Note that you’ll need to join OCF in order to access that link, but basic
> membership is free so I encourage you to do so if you haven’t already!
>
> Thanks,
> Nathan
>
>
>
> *From:* iotivity-dev@lists.iotivity.org [mailto:iotivity-dev@lists.
> iotivity.org] *O
osed to know that
> “bathroomLight” is oic.r.switch.binary instead of oic.r.light.brightness?)
>
>
>
> PS: have you evaluated aedes? Mainflux uses that as their MQTT broker and
> it’s my understanding it was built to replace mosca.
>
>
>
>
>
> *From:* iotivity-dev
ex if you’re interested in.
>
>
>
> Thanks
>
> Ondrej @ Kistler
>
>
>
>
>
> *From:* iotivity-dev@lists.iotivity.org [mailto:iotivity-dev@lists.
> iotivity.org] *On Behalf Of *Khaled Elsayed
> *Sent:* Mittwoch, 22. August 2018 13:25
> *To:* Gregg Reynolds
> *Cc
r other architectural benefits) that an
>
> OCF<->MQTT binding might enable. That could contribute to discussions
>
> I routinely engage in on the OCF standards side.
>
>
>
> Thanks,
>
> -Kishen.
>
>
>
>
>
>
>
> --
>
> Kishen Maloor
>
>
>
> best regards
>
>
> JinHyeock
>
>
>
>
>
>
> - *Original Message* -
>
> *Sender* : Khaled Elsayed
>
> *Date* : 2018-08-20 20:28 (GMT+9)
>
> *Title* : [dev] MQTT G/W
>
> *To : *iotivity-dev
>
>
> Hi,
>
&g
) existed.
>
> But now PPM has been replaced with Mini Plugin Manager (MPM).
>
> You should be able to find old code in repository or through google search.
>
>
>
> Regards
>
> Dwarka
>
>
>
> *From:* iotivity-dev@lists.iotivity.org [mailto:iotivity-dev@lists.
&g
, Mats Wichmann wrote:
> On 08/20/2018 05:28 AM, Khaled Elsayed wrote:
> > Hi,
> >
> > Has anyone developed a MQTT gateway that would host a MQTT broker
> receiving
> > the MQTT publish requests and creates OCF resources corresponding to the
> > MQTT topics and hand
ote:
>
>
> On Mon, Aug 20, 2018, 1:36 PM Gregg Reynolds wrote:
>
>>
>>
>> On Mon, Aug 20, 2018, 6:28 AM Khaled Elsayed
>> wrote:
>>
>>> Hi,
>>>
>>> Has anyone developed a MQTT gateway that would host a MQTT broker
>>> receiving
Hi,
Has anyone developed a MQTT gateway that would host a MQTT broker receiving
the MQTT publish requests and creates OCF resources corresponding to the
MQTT topics and handles the update of the resources data. It should not be
that difficult so I am asking it is already there to avoid doing it ag
If I specify TARGET_TRANSPORT=IP would this be enough?
On Thu, Jul 12, 2018 at 12:20 AM, Khaled Elsayed
wrote:
> Hello
>
> Excuse me if this is a trivial question, how to build iotivity disabling
> some of the supported transports. Particularly, I need to disable iotivity
>
Hello
Excuse me if this is a trivial question, how to build iotivity disabling
some of the supported transports. Particularly, I need to disable iotivity
clients/servers from using BLE transport. It is harming some other programs
using the Bluez controller to connect to BLE peripherals.
Thanks
K
n 5, 2018 at 5:01 AM, Khaled Elsayed
> wrote:
>
>> I don't think this an official Bluetooth SIG profile. I believe it is
>> implemented in iotivity linux (https://wiki.iotivity.org/ble_for_linux)
>> and runtime.io Nimble stack. So, you can have a look at the source cod
I don't think this an official Bluetooth SIG profile. I believe it is
implemented in iotivity linux (https://wiki.iotivity.org/ble_for_linux) and
runtime.io Nimble stack. So, you can have a look at the source code. It is
straightforward if you are generally familiar with Bluetooth profiles/GATT.
I assume you meant free t-shirt of course :-)
On May 11, 2018 00:16, "Rami Alshafi" wrote:
> Developers,
>
> Please join us for the OCF IoTivity Hackathon, which includes an IoTivity
> training and hackathon competition! The event will start at 8:30am on
> Thursday, June 21 and run until 12pm on
6.04 and I ve tried both with Iotivity 1.3.1
> and Iotivity at master.
> Should I follow different instructions?
> Thank you.
>
> Best Regards,
> KM
>
> p.s what is the difference between resource directory and resource hosting
> (in service folder)?
>
> On 16-Ap
An architectural correction: the local OCF servers typically discover RD
and register with it not the other way around.
On Mon, Apr 16, 2018 at 3:37 PM, Khaled Elsayed
wrote:
> If the devices have public IP addresses (not recommended), they can be
> accessed with the help of a re
If the devices have public IP addresses (not recommended), they can be
accessed with the help of a resource directory RD server. The RD should
perform local discovery of the devices and can share this information with
external end points.
If devices have non-routable addresses, then proxy+RD is t
Try this guide here and see if things work out
https://openconnectivity.org/wp-content/uploads/2017/12/OCF-IoTivity-RPi3-GSG.pdf
On Mon, Apr 16, 2018 at 3:33 AM, 구자훈 wrote:
> Hello,
>
> I don't know if it's right to ask a question here.
>
>
>
> I am trying to implement about [IoTivity Developme
Hi Greg,
There are two ways. Either use a BLE stack that has some port of
iotivity-lite or devise some proxy to interface with a native BLE device
using its own stack that has no OCF support.
For the first case, mynewt is one option and the other is Zephyr. Also for
Nordic modules, RIOT with its
OK, got it. cmake is a nice tool too but I am no expert in using it for
different platforms. Still hate scons :)
On Mon, Dec 4, 2017 at 5:28 PM, Mats Wichmann wrote:
> On 12/04/2017 05:35 AM, Khaled Elsayed wrote:
> > Great to know I was not the only one who dislike scons. Never wo
Thanks Gregg. Will surely give it a try.
Cross-compiling with make works OK. Let us see what Bazel offers there.
On Mon, Dec 4, 2017 at 6:10 PM, Gregg Reynolds wrote:
>
>
> On Mon, Dec 4, 2017 at 10:07 AM, Gregg Reynolds wrote:
>
>>
>>
>> On Mon, Dec 4, 2
Great to know I was not the only one who dislike scons. Never worked with
Bazel. Still think that make/autoconf are the greatest tools in software :)
I think that if a bold switch to make is done, it will be a great step
forward at least to break the barrier for a learning curve for another
build e
Could you share the patch link?
On Wed, Nov 22, 2017 at 9:14 PM, Oleksandr Grytsov wrote:
> It is for IoTivity-Constrained.
> The patch is submitted.
>
> Thanks.
>
>
> On Tue, Nov 21, 2017 at 7:34 PM, Maloor, Kishen
> wrote:
>
>> Hello,
>>
>> Is this port to IoTivity or IoTivity-Constrained?
>>
processing is done in the main loop. So far it it enough for
> iotivity-constrained.
>
> I don't consider to add any RTOS. It would be convenient in some cases.
> But my target is really constrained devices
> and don't have enough resources.
>
> On Thu, Nov 1
This is interesting. So, I am just curious you would have iotivity running
over openthread stack? Doew openthread depend on the underlying OS? So, is
the architecture would be something like this?
| Iotivity |
---
---
Hi Yann
The ESP8266 patch submitted is not compatible/tested with iotivity 1.3. You
probably need to go back to release 1.2.
Have you tried changing Time.h to time.h?
On Fri, Sep 29, 2017 at 4:09 PM, yann stephen mandza
wrote:
> Good day All!
>
> I am trying to compile the Iotivity for Esp82
Hi
Do you mean by "Zigbee" Zigbee layer 3 and above or IEEE 802.15.4? If IEEE
802.15.4 then probably one of iotivity-constrained ports should work for
you.
On Fri, Sep 29, 2017 at 6:42 AM, Adarsh Umesh
wrote:
> Dear IoTivity Dev team,
>
> We are plannig to implement Zigbee with IotTivity fram
We have had similar issues with RD and modified many parts of the code in
order for it to run as described.
We need to clean up the code and share it. Hopefully, we do it this month.
Best regards
Khaled
On Thu, Sep 28, 2017 at 7:46 PM, 김문권 wrote:
> Hi, developers~
>
> I have two questions reg
Yes, the official way is to submit a patch via gerrit
https://wiki.iotivity.org/how_to_use_gerrit
On Mon, Sep 25, 2017 at 1:14 PM, Jonny Rodin
wrote:
> Hi,
>
> I’ve been working on getting IoTivity to build for iOS and recently
> switched from an earlier IoTivity 1.3.0 build to IoTivity 1.3-re
in.
>
> Thanks,
> -Kishen.
>
>
>
> -
> Kishen Maloor
> Intel Open Source Technology Center
>
>
>
>
> From: on behalf of Khaled
> Elsayed
> Reply-To: "khaledi...@gmail.com"
> Date: Tuesday, September 19, 2017 at 1:45 AM
> To: &qu
address for the interface and this is where the bug seems
to be.
The exception is the linux port which should of course starts with
everything in place via the linux box setup.
On Mon, Sep 18, 2017 at 4:38 PM, Thiago Macieira
wrote:
> On Monday, 18 September 2017 01:29:20 PDT Khaled Elsa
90642252/109652098423390642252/about>
>
> *J.M. Driver LLC*
>
>
>
> *From:* iotivity-dev-boun...@lists.iotivity.org [mailto:
> iotivity-dev-boun...@lists.iotivity.org] *On Behalf Of *Khaled Elsayed
> *Sent:* Montag, 18. September 2017 10:29
> *To:* Thiago Macieira
> *Cc:* iot
On Sun, Sep 17, 2017 at 6:33 PM, Thiago Macieira
wrote:
> On Sunday, 17 September 2017 07:03:11 PDT Khaled Elsayed wrote:
> > Insert the following lines after line 228 in oc_connectivity_init in
> > port/zephyr/src/ipadpater.c will solve the problem.
> >
> > Will update
t_if_addr *ifaddr = net_if_ipv6_addr_add(net_if_get_default(),
&in6addr_my, NET_ADDR_MANUAL, 0);
On Thu, Sep 14, 2017 at 6:26 PM, Thiago Macieira
wrote:
> On Thursday, 14 September 2017 06:36:44 PDT Khaled Elsayed wrote:
> > > Why would it not? You seem to be confusing the source address
Hi Thiago,
Please find replies/queries below:
On Wed, Sep 13, 2017 at 9:21 PM, Thiago Macieira
wrote:
> On quarta-feira, 13 de setembro de 2017 05:00:10 PDT Khaled Elsayed wrote:
> > 2- Zephyr is supposed to be working on tap0 interface with the following
> > parameters:
You need to upgrade your build system. The steps below made it for me:
install build-essential to get all libs/include files needed
sudo add-apt-repository ppa:ubuntu-toolchain-r/test -y && \
sudo apt-get update && \
sudo apt-get install gcc-6 g++-6 -y && \
sudo update-alternatives --install /usr
Hi,
Hi Iotivity-constrained developers
I am trying to run the iotivity-constrained server of zephyr port on qemu
before using it on the actual NRF board. The behavior is not correct. When
zephyr server is loaded, it initializes iotivity stack properly. Now
starting the linux client, it sends mult
Hi
Is there a way to enable the logger only in specific parts of the overall
program?E.g. may main.cpp otherwise all other OC stack modules/libraries
remain silent as if in release mode. I know I can use printfs etc, I just
like the format of the logger output.
Also, is there a way to search the
our gateway. That connection could be Ethernet
> or WiFi for example.
>
>
>
> My understanding is also that things will be slightly different (for the
> better) when Bluetooth 5.0 (that introduces mesh) gets into the picture.
> But I think that?s still a few months away at leas
east.
>
>
>
> To all networking experts out there, please chime him if I?m talking
> rubbish at any point ;)
>
>
>
> Geoffroy
>
>
>
> *From:* khaled at ieee.org [mailto:khaled at ieee.org] *On Behalf Of *Khaled
> Elsayed
> *Sent:* Tuesday, June 6, 2017 5:11 PM
>
, Geoffroy <
geoffroy.vancutsem at intel.com> wrote:
> Hi Khaled,
>
>
>
> You will find some input to some of your questions embedded below.
>
>
>
> *From:* iotivity-dev-bounces at lists.iotivity.org [mailto:
> iotivity-dev-bounces at lists.iotivity.org] *On Behal
??
Dear all,
We are working on a research project called campie http://campie.cu.edu.eg/
and have chosen iotivity/OIC as our base connectivity and service discovery
layer. I have several questions on iotivity as I am trying to draft our
platform architecture. Looking forward to an exciting discuss
I think you need to set the LDLibrary path not the path env variable
On Jun 1, 2017 07:18, "shreyas Shah" wrote:
> Dear Developers,
>
> I am using IoTivity-1.2.1 and my host system is ubuntu 12.04.
> I am trying to run the examples of service-Resource
> Container(ContainerSample and Contai
This sounds very I interesting of course. However, need to have some
distinguishing features from existing platforms that provide similar
services.
For the TBD rtos, riot and zephyr seem like good candidates.
Best regards
Khaled
On Apr 21, 2017 10:31, "Dwarkaprasad Dayama"
wrote:
> Hi IoTivity
Hello,
I am trying to setup a demo of iotivity using multiple technologies. This
demo should include:
1) Linux native client/server nodes
2) Iotivity constrained running on RIOT using RIOT under Linux port
3) Iotivity constrained with Zolertia Z1 running Riot with 802.15.4
connectivity.
4) BLE co
Hi Mike,
This is exactly what I was asking for. Could you explain what do you mean
by submitting a* new path*? Is what you illustrate below doable on current
gerrit for iotivity? I tried submitting using different author name for a
specific patch but gerrit always refuses the patch.
Best regards,
Great to know the steam is gathering beyond OCF/iotivity.
On Jan 12, 2017 19:16, "Gregg Reynolds" wrote:
>
>
> On Thu, Jan 12, 2017 at 3:24 AM, Khaled Elsayed
> wrote:
>
>> I heard there was a full OIC booth. You mean no developers were there?
>>
>
>
. I
thought there is some option to allow this mode of work. I hope option 2
you proposed can work.
Khaled
On Thu, Jan 12, 2017 at 1:51 PM, Philippe Coval <
philippe.coval at osg.samsung.com> wrote:
>
>
> On 12/01/17 10:21, Khaled Elsayed wrote:
>
> ?Adding to what Morten
I heard there was a full OIC booth. You mean no developers were there?
Khaled
On Thu, Jan 12, 2017 at 1:23 AM, Gregg Reynolds wrote:
> so I was the only iotivity dev dweeb at ces last week?
>
> ___
> iotivity-dev mailing list
> iotivity-dev at lists.
?Adding to what Morten mentioned, I have the following issue:
If two developers are working on the same patch, how to allow the other
developer (i.e. the one who did not originally submit the patch) to make an
update from his local machine? In our case, I had to submit the patch
manually to the ot
IoTivity Security Code must understand those SVRs thoroughly.
>
>
>
> Thanks,
> Nathan
>
>
>
> *From:* Gregg Reynolds [mailto:dev at mobileink.com]
> *Sent:* Sunday, December 25, 2016 9:30 PM
> *To:* Heldt-Sheller, Nathan
> *Cc:* Khaled Elsayed ; iotivity-dev at
Just a correction, the port is done by Khaled Qorany and myself with
Phillipe supporting/reviewing. We are now in the process of merging with
latest master branch. Matta thankfully managed to compile the port and
confirmed that it works.
As Phillipe and Matta pointed, the port is based on Arduino
gineer,
>
>
>
> On Tue, Dec 20, 2016 at 12:55 PM, Khaled Elsayed
> 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
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 se
92 matches
Mail list logo
