On sexta-feira, 29 de julho de 2016 15:45:58 PDT ???(Uze Choi) wrote:
> You looks a little bit confused with IoTivity scope.
> Beyond the OCF protocol path, we cannot handle everything.
> Let's think about the UPnP bridge, are we handling the UPnP secure channel
> from first?
That's a good questio
On sexta-feira, 29 de julho de 2016 15:32:13 PDT ???(Uze Choi) wrote:
> Please do not block the enthusiasm to provide the solution for non HTTPS
> website. CA is not affected from it. Please do not concern.
Enthousiasm is fine, but we don't have to accept every single submission,
specially if tha
On sexta-feira, 29 de julho de 2016 06:25:16 PDT ?? wrote:
> Repeating the Uze's point, why we need to focus on feature which is out of
> scope for OCF spec & IoTivity?
Ok, so we shouldn't have this feature at all. There's no HTTP proxy feature in
the OCF spec. Is that what you meant?
If we foll
On sexta-feira, 29 de julho de 2016 15:22:35 PDT ???(Uze Choi) wrote:
> Front some reasons are related with capability.
> Incrementally we can extend the web site coverage scope.
Yes, we could. I am saying that doing it incrementally is not acceptable for
me. The first version that lands on the m
On quinta-feira, 28 de julho de 2016 22:32:10 PDT Dave Thaler via iotivity-dev
wrote:
> On 15 May 2015, Moumita Ray made a change to iotivity that changes the
> separator in query filters:
>
> Changed ampersand '&' to semicolon ';' to concatenate multiple query
> string
>
> This change s
On sexta-feira, 29 de julho de 2016 14:53:40 PDT ???(Uze Choi) wrote:
> Some of reasons are independent from incremental release
> and the others are invalid if HTTPS support does not affect CA layer.
Let me go over them again, in priority order:
* some websites require HTTPS
The only wa
On sexta-feira, 29 de julho de 2016 14:35:09 PDT ???(Uze Choi) wrote:
> There seems to be no rational to block incremental release,
> because HTTPS is not mandatory from Website perspective.
I've already given you five arguments why HTTPS needs to be there.
--
Thiago Macieira - thiago.macieira (
nce which it
appears is no longer needed, is there any reason to retain the ';' in the code?
I'm asking because I'm working on unforking libcoap and would like to avoid
pushing non-RFC-compliant changes upstream.
Dave
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/602e9895/attachment.html>
On sexta-feira, 29 de julho de 2016 14:07:51 PDT ???(Uze Choi) wrote:
> Once later HTTPS add-on does not affect the CA layer architecture,
> incremental release is valid.
No, I'm sorry. IoTivity must not release this feature if you can't access an
HTTPS site.
--
Thiago Macieira - thiago.macieir
On sexta-feira, 29 de julho de 2016 13:05:42 PDT ???(Uze Choi) wrote:
> Regarding your comment :
> "most of the changes to the CA layer that make it work with HTTP become
> superfluous and should not be applied." -> CA layer affect thinDevice-G/W
> side not for G/W-WebServer(HTTP/HTTPS).
That's no
rrit.iotivity.org/gerrit/#/q/owner:rzr+status:open
Regards
--
https://wiki.tizen.org/wiki/User:Pcoval
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/8c84fe3a/attachment.html>
gt;
> (Going from memory so you'll have to confirm) This is caused by a change
> in tinycbor. The implementation of _cbor_value_dup_string was moved from
> cborparser.c to a new file cborparser_dup_string.c. I think all you need
> to do is add that file to cbor_src (in tinycbor/SConscript).
>
> HTH,
>
> Gregg
>
--
BR,
Chao Guo
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/072201f1/attachment.html>
gt; 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/20160728/ba46124c/attachment.html>
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/e0970b8b/attachment.html>
enable that - should be able to find with
search engine.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/401754ac/attachment.html>
On quarta-feira, 27 de julho de 2016 12:15:54 PDT Chao Guo wrote:
> I tried to compile the source code which is download from 1.1-rel branch of
> github, when I make everything ready and start the process, it terminated
> because of errors.
1.1-rel tells you to do:
git checkout v0.2.1
in
ile +82 10 3304 8502
markus.jung at samsung.com
Best Regards,
Dr.techn. Markus Jung
IoT, IoTivity, OIC | IoT Lab
Software R&D Center | Samsung Electronics Co., Ltd
Mobile +82 10 3304 8502
markus.jung at samsung.com
http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/cf45eefd/attachment.html>
m
cborparser.c to a new file cborparser_dup_string.c. I think all you need
to do is add that file to cbor_src (in tinycbor/SConscript).
HTH,
Gregg
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/c0c73d6a/attachment.html>
ivity.org/pipermail/iotivity-dev/attachments/20160728/91ac6474/attachment.html>
Then, I think this is not mandatory, because this path is out of the OCF
security scope.
BR, Uze Choi
-Original Message-
From: Thiago Macieira [mailto:thiago.macie...@intel.com]
Sent: Thursday, July 28, 2016 12:05 AM
To: ???(Uze Choi)
Cc: ashok.channa at samsung.com; iotivity-dev at list
On 07/28/2016 09:52 AM, Carl Dunham wrote:
> Philip, how do we get a login for Jira to report bugs?
it uses the Linux Foundation authentication system - use your LF credentials
(or create an account there if you don't have one yet)
--
HTML ?? ??...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/809b8202/attachment.html>
On quinta-feira, 28 de julho de 2016 06:32:31 PDT ?? wrote:
> >>Because the implementation may not want to run the proxy on the same port
> >>as the main OCF resources, for security reasons or for >>implementation
> >>details. The information in either the /oic/res reply or the proxy's own
> >>reso
On quinta-feira, 28 de julho de 2016 10:24:21 PDT ???(Uze Choi) wrote:
> Then, I think this is not mandatory, because this path is out of the OCF
> security scope.
Correct, it's out of OCF security. IoTivity security rules still apply,
though.
I'm saying that IoTivtiy should not accept the code
ement,*
>
>
>
>
> *Salim Zayen*
> *?l?ve ing?nieur *
> *t?l?phone :+216 23 85 66 25*
> *esprit*?
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/fa60750e/attachment.html>
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/d00f3095/attachment.html>
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/7b44961e/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201602111742151_N3WZA6X7.png
Type: image/png
Size: 33527 bytes
Des
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/b254dd74/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201602111742151_N3WZA6X7.png
Type: image/png
Size: 33527 bytes
Des
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/6db57bae/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201602111742151_N3WZA6X7.png
Type: image/png
Size: 33527 bytes
Des
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/cc36a5b4/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201602111742151_N3WZA6X7.png
Type: image/png
Size: 33527 bytes
Des
ted in the wiki
(https://wiki.iotivity.org/architecture.)
BR, Uze Choi (OSWG Developer Ecosystem Build TG Chair)
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160728/28697adf/attachment.html>
31 matches
Mail list logo
