I remember catching this in a code review @ https://gerrit.iotivity.org/gerrit/#/c/15197/15/resource/csdk/stack/src/ocstack.c at 1433
The "diagnostic payload" was being destroyed but it was added back in after the comment. So the plumbing for diagnostic messages is present in the form of the regular response payloads Iotivity uses with the message that can potentially appear as a string value in the map, it's just that it's not being used. I don't know how faithfully it follows the section of the RFC you linked though. From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Malsbary, Todd Sent: Monday, March 20, 2017 4:03 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] diagnostic payloads Hello, Is there any means to send/receive diagnostic payloads as specified in https://tools.ietf.org/html/rfc7252#section-5.5.2? I'm guessing the answer is no and there's no work in progress on supporting it (I couldn't find any relevant JIRA/pending commits), but I'd like to confirm. Thanks, -Todd -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170320/84cc5cad/attachment.html>
