> On Apr 11, 2016, at 10:25 PM, Michael Koster <michael.koster at > smartthings.com> wrote: > > So Wireshark renders CoAP query options as an HTTP query string? > > That's a bit confusing. Should it not render it as a map? > Or a list of xx=yy values, but not an HTTP query string.
> In reading up on the Wireshark CoAP display filter, I found this also: > > coap.opt.ctype Content-type Character string 1.6.0 to 2.0.2 > From RFC7252, this option is called Content-Format and is of type uint: > > 12 | | | | | Content-Format | uint | 0-2 | (none) > > So maybe an upddate to the wireshark CoAP display filrter is in order. > > Michael > >> On Apr 11, 2016, at 9:44 PM, ???(Uze Choi) <uzchoi at samsung.com >> <mailto:uzchoi at samsung.com>> wrote: >> >> This is presented as switch?colour=0&if if=baseline in the wireshark, but if >> we look detail >> Each filed is composed of like this. >> Option : switch >> Option : colour=0 >> Option : if=baseline >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160411/b589b4f0/attachment.html>
