Dear Thiago, Your concern is regarding Spec or Iotivity implementation? AFAIK, in Spec CoAP serialization over TCP is not mandatory. It has its own mandates only if implemented.
Regards Dwarka ---------------------------------------------------------------------------- ------ Software R&D Center | Web & Convergence Team | IoT Solution Lab Open Interconnect Consortium - Open Source Work Group Member Iotivity Steering Group - Advisory Committee -----Original Message----- From: [email protected] [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of Thiago Macieira Sent: Wednesday, August 19, 2015 4:20 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] TCP must be optional Hello all I'm seeing a few changes go about CoAP over TCP and I'm wondering what those are for. Please make sure that TCP support remains forever optional in IoTivity. No device should be required to have it, as we'll have both networks and operating systems that lack TCP support. That means no feature can depend on TCP and must work over UDP (unless the feature itself is optional). Any TCP support must be negotiated after getting the capabilities of both end-points as well as any intermediaries along the way. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150820/ecdefe50/attachment.html>
