On Wed, Aug 15, 2018, 4:44 AM Wouter van der Beek (wovander) < wovan...@cisco.com> wrote:
> Hi Greg, > Hi. My friends call me "3g" to disambiguate from my pal "2g" (Greg). > > > You are correct TCP connections are not required for cloud, TLS > connections are: > > > https://openconnectivity.org/specs/OCF_Core_Specification_Extension_CoAP_Native_Cloud_v2.0.0.pdf > > see line 510 and onwards. > Not sure how to interpret that. TLS w/o TCP? Anyway my point is it is not an OCF requirement - cloud is an extension. My point being that OCF cloud imposes additional requirements on servers. It's not enough to be an OCF node, you must add some stuff. Iow you cannot participate if you are a mere OCF server, with only udp/dtls. It really subverts the entire OCF model, imho. That's fine if that's what you want, but it hardly covers everything. ... > The OCF cloud solves the remote access issue: contacting the devices from > another network. > Respectfully, not so much. OCF cloud clients do not contact the origin devices, by design. They obtain data via a proxy server. More to the point: "the remote access issue" is just wrong. There are many remote discovery/auth/access scenarios, no one of which can be picked out as "the" remote access issue. The OCF cloud stuff just picks out one. Honestly, I do not think OCF has really thought this through. The ietf stuff has lots of use cases. Gregg > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9869): https://lists.iotivity.org/g/iotivity-dev/message/9869 Mute This Topic: https://lists.iotivity.org/mt/24238274/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
