You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I see my problems with Observe in Zephyr stems from the following lines in Zephyr coap.c and the fact “inner observe” with OSCORE is zero:
(At least the notifications sent are rejected due to below “age check”)
age = coap_get_option_int(response, COAP_OPTION_OBSERVE);
/* handle observed requests only if received in order */
if (age == -ENOENT || is_newer(r->age, age)) {
r->age = age;
r->reply(response, r, from);
}
I think a work around may be to add an external/outer OSCORE observe value that would pass above check?
The text was updated successfully, but these errors were encountered:
" A client MUST consider the notification with the highest Partial IV
as the freshest, regardless of the order of arrival. In order to
support existing Observe implementations, the OSCORE client
implementation MAY set the Observe option value to the three least
significant bytes of the Partial IV. Implementations need to make
sure that the notification without Partial IV is considered the
oldest."
Issue received per email:
As I see my problems with Observe in Zephyr stems from the following lines in Zephyr coap.c and the fact “inner observe” with OSCORE is zero:
(At least the notifications sent are rejected due to below “age check”)
I think a work around may be to add an external/outer OSCORE observe value that would pass above check?
The text was updated successfully, but these errors were encountered: