RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP messages

[zhigang.c.liu@nokia.com]

Robert,

>  I don't think it is a problem with SigComp multiplexing, but 
> more like a SIP internal issue. What if there is a TCP stream 
> of SIP messages and the Content-Length header is missing or 
> false? They will screw up the same way with or without 
> SigComp. 

Since TCP is a reliable transport, this only happens for a
mis-behaved SIP sender. But that is not the "multiplexing" problem 
I mentioned below, which happens even "during normal functioning" 
(see below).

> During normal functioning both SIP and SigComp 
> provide their own flow separation mechanism and they work just fine.

I don't think so. That is what I intended to show by the example,
i.e. the issue to "multiplex uncompressed application messages and 
SigComp messages on the same port". One solution, as I mentioned
before, is to require sigcomp receiver has the ability to parse
uncompressed application messages and detect the end. 

(Of course, I saw Carsten's email and I need understand his
point of view, which says there is no such "multiplexing" and
it is not possible and necessary.)

BR,
Zhigang
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc