RE: [rohc] Re: multiplexing SigComp and non-SigComp messages on t he same TCP connection

[zhigang.c.liu@nokia.com]

Hi,

Unfortunately, I couldn't spend time on this issue and will be
on vacation starting next Monday until after new year. This has
been a quite good discussion since it revealed things we really 
haven't had chance to elaborate.

Just a quick summary of what we agreed (or seemed so):

1) RFC 3320 does NOT allow multiplexing of SigComp and non-SigComp
messages over the same TCP connection. Period.

2) The question is whether multiplexing is needed.

3) The mechanics of doing the multiplexing is clear.

4) Multiplexing is a new requirement, as the receiving SigComp
endpoint has to behave differently.

5) A very simple stateless bytecode can be used to carry an
uncompressed SIP message in a SigComp message. This can recover
SigComp failures due to loss of sync on states.

The rest is still more or less in debate, or unclear: single TCP
connection, 64KB upper limit of UDVM output, UDVM failure itself, 
security, etc. I'd encourage more pointed discussions from both
sides so that we can reach a conclusion.

Have a good holiday season!

Zhigang

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