The current text requires the client to take care of the retransmission and canceling of Access Report TLVs. The concentrator must echo the TLVs to form a sort of acknowledgment if I understood correctly. In fact, control TLVs are currently sent on an unidirectional stream, and are thus reliably delivered in order, and acknowledged at the transport level. Still, it makes sense to stop (re)transmitting an AR as soon as it is no longer relevant.
This PR moves AR TLVs to separate unidirectional streams. This removes the ability of the client to chose how to retransmit the ARs part of a lost packet, and replaces the application-level acknowledgment with a transport-level one. I am unsure how valuable is this acknowledgment to the client outside of stopping the retransmission timer. If there is no other use, then this is fine. Finally, the client retain the ability to cancel the transmission of ARs by resetting their corresponding unidirectional streams.
The current text requires the client to take care of the retransmission and canceling of Access Report TLVs. The concentrator must echo the TLVs to form a sort of acknowledgment if I understood correctly. In fact, control TLVs are currently sent on an unidirectional stream, and are thus reliably delivered in order, and acknowledged at the transport level. Still, it makes sense to stop (re)transmitting an AR as soon as it is no longer relevant.
This PR moves AR TLVs to separate unidirectional streams. This removes the ability of the client to chose how to retransmit the ARs part of a lost packet, and replaces the application-level acknowledgment with a transport-level one. I am unsure how valuable is this acknowledgment to the client outside of stopping the retransmission timer. If there is no other use, then this is fine. Finally, the client retain the ability to cancel the transmission of ARs by resetting their corresponding unidirectional streams.