On Jul 19, 2017 8:27 PM, "조병탁" <[email protected]> wrote:
I would really appreciate if someone could give me some advice about my
question.
dunno much about it but:
"Elective Option
An option that is intended to be ignored by an endpoint that does
not understand it. Processing the message even without
understanding the option is acceptable."
are you sure that's desirable?
Thanks,
bt.jo
--------- *Original Message* ---------
*Sender* : 조병탁 <[email protected]> Senior Engineer/IoT사업화팀(DS)/삼성전자
*Date* : 2017-07-14 13:45 (GMT+9)
*Title* : [Question] about iotivity 1.3.0 new CoAP options
Hello
I have question about Accept version & content-format version on iotivity
1.3.0 (OCF 1.0 spec.)
Accept version : CoAP option number 2049
Content-Format Version : CoAP option number 2053
above new option idicate a critical option(Odd number) - CoAP rfc7252.
(Not elective option(even number).)
so if some device uses OIC 1.1 spec. and does not implemented new critical
option, some CoAP lib. will reject that message.
Of cource, if device uses iotivity open source, there is no issue.
but if device uses custome OCF implementation or 'iotivity constrained',
device could not response about request of iotivity 1.3.0.
(maybe 'er-coap' library will reject unsupported critical option - CoAP
rfc7252)
So i think above new option should be elective option not critical option
for backward-compatibility.
Please correct me if i misunderstood.
Thanks,
bt.jo
_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
