Hi,
>>>* if they're out of sync, which one takes precedence (that is, do I
>>>process a Content-Type that isn't listed in the
>>>Content-Type-List?)
>
>I'm with Dan on this. Also, this is well trodden ground in
>email, and they haven't found a need for this.
Email does not have the same real-time requirements which SIP has.
>>The Content-Type contains "multipart/*", while the Content-Type-List
>>contains the types (app/sdp, app/isup, app/whatever etc)
>>within that multipart.
>>
>>Please note that I am talking about SIP headers, not in the MIME
>>bodies (of course, if a MIME body contains another multipart/*, the
>>header could perhaps also be used there).
>
>There really isn't any difference between sip headers and
>mime headers.
>From a mime perspective the entire sip message is just a
>bunch of mime headers including some that are extension headers.
My point was that you can't determine what types of MIME bodies you have
simply by taking the whole SIP message and performing a string search on
"Content-Type". Because, some of the Content-Types you will find may not
describe what is in a MIME body - it may be part of the MIME body data.
-----boundary
Content-Type: protocol/sip
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Content-Type: application/pidf+xml
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
...
-----boundary
In this example the string search will find two "Content-Type", but only
one of them actually describes the content of the MIME body, while the
other is just data inside that body.
Regards,
Christer
_______________________________________________
Sip mailing list https://www1.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
