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

[zhigang.c.liu@nokia.com]

Lars-Erik,

> Actually, the proposal from the SFO meeting was to create a new
> WG draft to define what we think should be defined for the case
> of "SigComp for SIP", as RFC 3486 does not seem to be sufficient.

Yes, this is the document Carsten proposed to "bind" SigComp and SIP. 
If I understand correctly, it will address SIP specific issues: larger
DMS, SigComp compartment mapping, etc. I volunteered to be the editor 
of this document. This is clear to me and not my question here. 

My question is the handling of binary content in application messages. 
In my view, this is a generic issue although it started with SIP. My 
thought was to have a *separate* document that addresses this issue (and 
perhaps other generic SigComp "bugs" if we find out). So, my question is:

1) Does it make sense to have two separate documents, as I explained above?

2) If the answer is yes, how do we proceed for the second one (i.e. on binary
content)? I discussed the issue on SIPPING list and volunteered to write 
a draft. I guess from your reply that it's OK for me to submit a personal
draft to ROHC WG.

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