rohc team mailing list archive

[Didier Barvaux <didier@xxxxxxxxxxx>]

Hello,

> > Will sending these packets first eliminate the problem?   I think
> > there are still chances the inconsistent list struct will occur.
> 
> I think that the current library sends only one single
> co_common/seq_8/rnd_8 packet when the list of TCP options changes its
> structure. If that packet is lost, the structure change is lost as
> well.
> 
> To circumvent this, the ROHC protocol requires that the compressor
> sends the changes until it is confident enough that the decompressor
> got the changes.
> 
> So, one packet is not enough. It is not robust enough to packet loss
> or reordering. It should be sent N times at least. N shall be
> configurable because it depends on network type and conditions.

I have just implemented the repetition of the list in case of change.
It is available in the main branch at revision  or later.

You may configure the number of transmissions of the list with the
rohc_comp_set_list_trans_nr() function. See its documentation:
http://rohc-lib.org/doc/rohc-doc-r1027/group__rohc__comp.html#ga32608bc06e1b0d1656e463eeb1ccbd7f

Tell me if it corrects the problems you encounter.

Regards,
Didier

Attachment: signature.asc
Description: PGP signature