Subject: RE: [rohc] ROHC: Header parsing

From: "Lars-Erik Jonsson (LU/EAB)" <[email-masked]>
Date: Tue, 16 Mar 2004 10:34:04 +0100

Jagan,

There is no way to explicitly know that packet stream is 
an RTP stream, but one will have to guess. The good thing
with ROHC IP/UDP/RTP compression is that it is lossless,
independent of if the UDP payload is actually RTP or not.
One can thus start with assuming RTP, and if the compression
ratio turns out to be negative for the RTP part, a profile
switch to IP/UDP-only should be performed (see section 5.11).

Cheers,
/L-E

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]On 
> Behalf Of Jagan
> S
> Sent: den 13 mars 2004 06:28
> To: [email-masked]
> Subject: [rohc] ROHC: Header parsing
> 
> 
> Hi,
> 
> 3095 specifies context identification at compressor  by 
> parsing RTP/UDP/IP
> header fields.
> 
> Yes. We can identify IP header by analyzing :' Version' / 
> 'Length' fields
> of IP header.
> UDP header by analyzing: 'protocol type' field from IP header
> 
> My question is about: How to identify the presence of RTP header ?
> 
> 
> Thanks in advance
> - Jagan
> ..............................................................
> ..............................................................
> ..............................................................
> ...................
> 
> 
> 
> 
> _______________________________________________
> Rohc mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/rohc
> 

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.

_______________________________________________
Rohc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/rohc