Hello Mališa,
> Thank you for summarizing the discussion we had and proposing these changes.
> I have modified the text in order to reflect the email below by:
I'm not sure I understand the distinction between "unsupported" and
"unexpected" parameters. Are they about having an unknown code vs.
Hello Christian,
Thank you for summarizing the discussion we had and proposing these changes. I
have modified the text in order to reflect the email below by:
- encoding additional info as a CBOR array allowing multiple parameters to be
transported within
- removing the previous error code
Dear Göran,
Many thanks for the review! As we discussed during the WG meeting, I added new
text in the draft to stress that the procedure in Appendix B.2 of OSCORE should
be used in the case of a failure event occurring at the JRC. The use of this
procedure is now RECOMMENDED, and in case it
Hello Mališa,
we've just talked about server state and the error codes sent with
subsequent join requests in [1], especially Sections 8.4.1 and Section
8.4.5. (Working group, please be aware that I have not read and
understood the full document but am responding to a particular question
here).
-Apologies if you received this CFP multiple times-
* Call for Papers
*GoodTechs 2019
*Track Session in Serious Games to Improve Quality of Life
*September
