> -----Original Message----- > From: Christer Holmberg [mailto:[EMAIL PROTECTED] > Sent: Saturday, December 06, 2008 4:09 PM > > > >So if the SIP message has body-parts, and one of them is actually not > intended for that package but is instead just a generic add-on, like > geoloc for example, we need to dis-ambiguate that add-on body- > >part(s) from the others. > > It should be defined in what SIP messages geoloc information may be > transported, and what the receiver supporting it is supposed to do with > it. As we do for SDP. SDP in CANCEL has no meaning, for example, so it > is seen as a protocol error to send SDP in CANCEL.
Geoloc may be transported in any SIP request, afaik - except ACK and CANCEL. Putting a body in any/all messages which is not for the context of the message is not without precedent, I've been told. Maybe this is just the first time that we really expect it to be used? :) A content type of "application/sdp" can be used in any request that can carry mime bodies as far as I know. It just wouldn't make sense to make it's C-D "session" in anything but INVITE, ACK, PRACK, and UPDATE; and for the SUB/NOT/PUB you'd have to define a package for using it. BTW, CANCEL can't carry any body, afaict, if for no other reason than the Content-* headers needed to do so can't be used in CANCEL. (nor would we want it to be able to, for obvious reasons) -hadriel _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
