rohc team mailing list archive

[Didier Barvaux <didier@xxxxxxxxxxx>]

Hi,

> I understand why you avoid the header compression,  the problem is if
> one is running an encryption application, etc it is difficult to
> compress he payload.

If encryption is used, you may or may not be able to compress the
packet. It depends on the encryption used:
 - With IPsec (ie. the ESP protocol), you can use the IP/ESP profile of
   ROHC for example.
 - With SSL/TLS encryption at application level, you can use the
   IP-only, IP/UDP, IP/UDP/RTP... profiles without any problem.


> If for example, you create a raw socket then
> your application is able to write the headers and also compress it.
> I have a bit of a problem getting my head around memcopy, and on that
> is it possible to use a framework such as Netmap which is way much
> efficient in the IO, What I am thinking of is to create ROHC as a
> device driver in that respect. You can then use mmap system call
> instead of memcopy to map ROHC device memory directly into a user
> process's address space. I am not a programmer but I think it's more
> efficient to use kernel kiobuf  implement DMA raw I/O. Just my
> thoughts.

Sorry, I'm not sure to understand your thoughts. If you need an answer,
please rephrase them.

Regards,
Didier

Attachment: signature.asc
Description: PGP signature