Re: [core] Retransmission of non-confirmable response message upon receiving request message retranmission?

["Kraus Achim (INST/ECS4)" <[e-mail]>]

Hi Carsten,

>  It does not mean the separate response is automatically retransmitted (that has its own ACK cycle).

though you're the author, I'm sure you know the intention :-).

Only resending the ACK, may keep the exchange open on the client side.
I'm wondering, in which use-case this would be preferred over resending the flight, 
which completes the exchange on the client side. 
I hope my interpretation, that the decision is left to the implementation, is right? 

Mit freundlichen Grüßen / Best regards

Achim Kraus

Engineering Cloud Services 4 Bosch IoT Hub (INST/ECS4) 



-----Ursprüngliche Nachricht-----
Von: Carsten Bormann <[e-mail]> 
Gesendet: Freitag, 29. November 2019 13:28
An: Kraus Achim (INST/ECS4) <[e-mail]>
Cc: Christer Holmberg <christer.holmberg=[e-mail]>; [e-mail]
Betreff: Re: [core] Retransmission of non-confirmable response message upon receiving request message retranmission?

> 
> Section 5 is then about the request/response 5.2.2, page 34 (top), "If a retransmitted request is received (perhaps because the original Acknowledgement was delayed), another Empty Acknowledgement is sent, and any response MUST be sent as a separate response."
> That seem to point to the same intention: retransmit the original messages (flight) as answer.
> 
> (It seems that my understanding differs from Carsten’s answer.)


   When the server chooses to use a separate response, it sends the
   Acknowledgement to the Confirmable request as an Empty message.  Once
   the server sends back an Empty Acknowledgement, it MUST NOT send back



Shelby, et al.               Standards Track                   [Page 33]
RFC 7252       The Constrained Application Protocol (CoAP)     June 2014


   the response in another Acknowledgement, even if the client
   retransmits another identical request.  If a retransmitted request is
   received (perhaps because the original Acknowledgement was delayed),
   another Empty Acknowledgement is sent, and any response MUST be sent
   as a separate response.

This means that once the server sends an empty ACK, it is committed to replying in a separate response; it can’t go back to piggybacking, even if a conveniently arriving retransmission of the request might suggest so.  It does not mean the separate response is automatically retransmitted (that has its own ACK cycle).

Grüße, Carsten