Oops, I just realized I didn't state this the way I meant...
Paul Kyzivat wrote:
Christer,
For SDP, you find the part by looking for the one with
Content-Disposition:session. If there is a part with no C-D header then
one with a C-T of application/sdp defaults to "session". So its all
about C-D.
For *offers and answers* you find the part by looking for the one with
Content-Disposition:session. If there is a part with no C-D header then
one with a C-T of application/sdp defaults to "session". So its all
about C-D. (In theory, application/sdp is just one of the C-Ts that
might be used to encode offers and answers.)
Paul
Christer Holmberg wrote:
Hi,
I do think there is something we haven't discussed: how do we figure
out what part of the overall body is the part that carries the
package? Normally this is no issue, since it is the entire body of
the INFO message. But there are cases where it might not be. For
instance if S/MIME is used, or if there is some header in the message
the needs to reference a body part from a CID URI.
The answer to this goes back to Content-Disposition. The body part
that contains the info package should have a unique C-D. That can be
"render", or we could pick some other one.
I believe the mime rules are something like:
--boundary
Mime-headers
Empy-line
Content (SDP, info packet, etc)
--boundary--
For SIP, the ruleas are:
SIP-part
Empty-line
Message body (SDP, info packet - or one of more mimes).
I guess the question is whether we should define some generic syntax for
the info packages, e.g. Something which identifies the beginning of an
info package.
For SDP, you find the beginning by looking for the v= parameter.
Regards,
Christer
_______________________________________________
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
