peter van der Stok
2017-04-03 07:59:55 UTC
Hi Core,
I had the pleasure to present the "pending" draft at the start of the
Friday session.
The draft proposes a new coap response code 2.06.
Carsten remarked that response code 5.03 also exists.
Our 2.06 draft allows to specify the location of the result, allowing
interleaved requests.
Additionally, the 2.06 draft will allow multiple requests.
My intention is to not only specify a minimum retry interval but also a
maximum interval (not specified for 5.03)
Consequently, I think that there are enough reasons to continue the 2.06
proposal.
Alternatively, the 5.03 can be extended with the current 2.06
specification.
Peter
I had the pleasure to present the "pending" draft at the start of the
Friday session.
The draft proposes a new coap response code 2.06.
Carsten remarked that response code 5.03 also exists.
Our 2.06 draft allows to specify the location of the result, allowing
interleaved requests.
Additionally, the 2.06 draft will allow multiple requests.
My intention is to not only specify a minimum retry interval but also a
maximum interval (not specified for 5.03)
Consequently, I think that there are enough reasons to continue the 2.06
proposal.
Alternatively, the 5.03 can be extended with the current 2.06
specification.
Peter
--
Peter van der Stok
vanderstok consultancy
mailto: ***@vanderstok.org
www: www.vanderstok.org
tel NL: +31(0)492474673 F: +33(0)966015248
Peter van der Stok
vanderstok consultancy
mailto: ***@vanderstok.org
www: www.vanderstok.org
tel NL: +31(0)492474673 F: +33(0)966015248