Hi Krish,
The scheme that you have shown is not allowed. A solution
for sending multiple media types in a message already exists
for e-mail. SIP re-uses that scheme.
Please refer to RFC 2046 on the multipart-MIME media types.
The multipart/mixed media type defined in this RFC is
used in SIP messages when multiple media types have to be
used in a single message.
-Binu
Krishnan P Sudharsana-A14377 <[EMAIL PROTECTED]> on
07/08/2002 12:08:43 PM
To: [EMAIL PROTECTED]
cc: Wu Fei-FWU1 <[EMAIL PROTECTED]>, T Satyanarayana-A12694
<[EMAIL PROTECTED]>, K Kaushik Sriram-A12869
<[EMAIL PROTECTED]>, Karpoor Lakshmi Sanjay-A17738
<[EMAIL PROTECTED]>, "Sudharsana krishnan P (E-mail)"
<[EMAIL PROTECTED]> (bcc: K Binu/HSSBLR)
Subject: [Sip-implementors] Content-Length Header clarification. Is the
following allowed??
All
I had the following confusion related to use of multiple message parts
in a SIP message.
I did not find anything in the SIP RFC related to use of multiple
Content-Length headers.
What if I have the SIP msg looking like the following and assume the
following
1. Ist Content-Length maps to the 1st body part.
2. Body parts split using CRLFCRLF.
3. Content-Length does not include the last CRLF.
4. There shall be as many Content-Length headers as there are body parts.
SIPMSG_START
Hdr1
Hdr2
...
Content-Length: 139
Content-Length: 150
II_MSGBODY_PART
II_MSGBODY_PART
SIPMSG_END
Please clarify the following for me
1. Is this allowed?
2. If not, why not? (I know that the above approach restricts the ordering
of multiple Content-Length headers. Is that the reason?)
Regards,
krish
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
