rohc team mailing list archive

[Raman Gupta <ramangupta16@xxxxxxxxx>]

Hi Didier,

The Ethernet based transport application for ROHC pkts is very similar in
concept and implementation to rohctunnel app, because I wanted to keep
error simulations, stats collection and usage same. However it uses link
layer Ethernet transport instead of IP/UDP. Aim was to provide similar and
easy alternate to someone looking for a link layer transport to conserve
more bandwidth by avoiding UDP/IP header overhead e.g. over point to point
links without gateway/router in between.

Merging the two will complicate the code and confuse usage. Keeping them
separate will help them evolve independently without fear of breaking the
other.

Examples of evolving the apps, that I am thinking are :-

1) ROHC multiplexing to combine multiple ROHC pkts in single transport pkt
to conserve more bandwidth.
2) Keep Alive msgs between Compressor and Decompressor so as to clear the
context or restart when other side restarts or crashes.
3) Service monitoring.

--Raman

On Fri, Feb 1, 2013 at 5:55 PM, Didier Barvaux <didier@xxxxxxxxxxx> wrote:

> Raman,
>
> >  Did you got some time to review the patch?
>
> Not yet. I just saw that you copied/pasted many lines of code from the
> UDP tunnel. Do you think the 2 programs could be merged?
>
> Regards,
> Didier
>
> _______________________________________________
> Mailing list: https://launchpad.net/~rohc
> Post to     : rohc@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~rohc
> More help   : https://help.launchpad.net/ListHelp
>
>