Piggy-backing note

[zach@…]

It was brought up in the IETF82 CoAP presentation, that imlpementation issues have been noticed where piggy-backing should have been used to avoid inefficient use of messages. This ticket is to propose some text to provide quality of implementation advice on when to piggy-back responses.

Carsten provided the following text:

"Implementation note: The _protocol_ leaves the decision whether to piggy-back a response or not (i.e., send a separate response) to the server. The client MUST be prepared to receive either. On the _quality of implementation_ level, there is a strong expectation that servers will implement code to piggy-back whenever possible -- saving resources in the network and both at the client and at the server."

Which could be placed at the end of Section 5.2.1.

[zach@…]

Message received by email on Wed, 04 Jan 2012 13:03:34 +0000, inserted by email2trac:

Although this was discussed in Taipei, we want to hear if there is any
feedback on the proposed text below.

Thanks,
Zach

On Jan 4, 2012, at 3:01 PM, core issue tracker wrote:

[zach@…]

Done.