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

["Lars-Erik Jonsson (EAB)" <Lars-Erik.Jonsson@epl.ericsson.se>]

Zhigang,

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.
However, we need to get the minutes out before we can go on with
that.

I therefore think it would be useful to get discussions going on
the list, both regarding the specific issue you have brought, and
other things that should be specified for applying SigComp on SIP.
If you want to, you can of course also submit an individual draft
to provide more discussion material. Such material might later on
be reused in a potential new WG draft.

OK?
/L-E


> -----Original Message-----
> From: zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> Sent: den 25 mars 2003 19:00
> To: cabo@tzi.org; Lars-Erik Jonsson (EAB)
> Cc: rohc@ietf.org; sipping@ietf.org
> Subject: RE: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> messages
> 
> 
> Hi Carsten and Lars-Erik,
> 
> I've volunteered to submit a personal draft on this issue. From
> ROHC WG chairs' point of view, do you think this is the way 
> to proceed?
> 
> Of course, I understood during the IETF56 that Carsten had some
> doubts on whether this is indeed an issue. My email below explained
> the issue a bit. I don't know if it's clear. Either way, we 
> can continue
> discuss this in ROHC mailing list
> http://www1.ietf.org/mail-archive/working-groups/sipping/curre
nt/msg04115.html
> 
> BR,
> Zhigang
> 
> > -----Original Message-----
> > From: ext zhigang.c.liu@nokia.com [mailto:zhigang.c.liu@nokia.com]
> > Sent: March 13, 2003 9:55 AM
> > To: Gonzalo.Camarillo@lmf.ericsson.se
> > Cc: adam@dynamicsoft.com; Isomaki Markus (NRC/Helsinki);
> > mwatson@nortelnetworks.com; sipping@ietf.org; rohc@ietf.org
> > Subject: [rohc] RE: [Sipping] SIGCOMP and large binary content SIP
> > messages
> > 
> > 
> > I agree. How to handling binary content is a generic issue for any
> > application messages. What I have in mind is to give generic 
> > descriptions/requirements (mainly on the SigComp receiver 
> > parsing part),
> > then touch on SIP (perhaps RTSP too) as a particular example.
> > 
> > Unless someone objects, I'll submit it in ROHC.
> > 
> > Zhigang
> > 
_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc