Hi Jon, Thank you for your input. I have logged a Jira ticket for this issue (https://jira.iotivity.org/browse/IOT-319) & posted in the review for the new libcoap-18 that is being used in the Connectivity Abstraction (CA) branch (https://gerrit.iotivity.org/gerrit/#/c/189/1/resource/csdk/connectivity/lib/libcoap-4.1.1/pdu.h) so that this issue will be followed by all members.
You may feel free to do these things as well with any other issues you may find. Thanks Joseph Morrow -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Jon A. Cruz Sent: Friday, February 6, 2015 3:54 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] Breakage with transport codes Hi, I finally tracked down a problem that was blocking my test efforts. It turns out that the CoAP packets IoTivity code is currently sending are based off of very early drafts of the spec that were outdated by the first part of 2011. Specifically the result value 2.00 was removed, and instead 2.03, 2.04 and 2.05 should be used depending on the context. The net effect of this difference is to break CoAP compliance and cause OIC to be incompatible with standard tools and major libraries. I've not yet looked to see if there are any additional problems hiding past this one. Is this an intentional choice of the OIC standard, or is it merely an implementation oversight in IoTivity code? If it is the latter, then it should not be too hard for me to get a patch to correct it. Thanks. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
