All,
Have question on SIGCOMP as applied to SIP.
Take a model where SIGCOMP compartments are created
at registration time. Say, a REGISTER from the client
establishes state at the Server, and 200-OK for the
REGISTER establishes state at the client.
The server could ack client's state-creation requests
along with this 200-OK.
The client is now ready to send compressed msgs
using the state acked from the server.
However there is no SIP/SIGCOMP that goes back to the
server at this point. Therefore, any initial messages
that the server sends to the client after this registration
cannot yet be compressed using state info sent with the
200-OK. (until an feedback/ack is received from the client
for the states created)
Is this how it is done? What are the current
best-practices, on the server-side, in this context?
Should I otherwise post this to the rohc list at ietf.
Thanks for any help/advice.
--
Srini K
ksrini at motorola
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
