RE: [rohc] Video and header compression

[zhigang.liu@nokia.com]

> the primary video application target for ROHC should be one where 
> there are more than one RTP packet per video frame.

I think there is no doubt about it. 

> ... The timestamp and the Marker will change often, which the SO cannot
> handle... Perhaps we can get this from the FO format...

As I said in my previous email, using FO is the way to go. It's conceptually

consistent (with audio) and straightforward in implementation. 

Just consider the FO format for audio: it needs to have SN field, M-bit 
field, TS and/or IP-ID field. So, what are the additional things needed 
for video? None. The major differences between audio and video are NOT 
in the header format. They are TS_STRIDE (e.g. 3000 for video instead
of 240 or 160 in the case of audio) and the frequency of FO headers
(90%, or even 100%?). Please see my comments on them in my previous
email.

Zhigang
 
> Cheers, 
> 
> / Krister