Re: draft-ietf-sip-info-events-00: Content-Type vs Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per INFO]

 
Hi,

(I've put all text about this into a single reply)

Dean:
=====

>>>>Shouldn't we use Content-Type to indicate what is in the message
body?
>>>>After all, we may need Content-Length etc.
>>>
>>>Ah, no.
>>>
>>>We had extended conversations on this earlier.  Content-Type tells 
>>>you what's in the body; it just doesn't tell you what to DO with the 
>>>body.
>>>
>>>What, for example, is the purpose of an image/jpeg in an INFO?
>>
>>That is not what I meant.
>>
>>We can use the Info-Package header, but can't we use a generic mime 
>>value - which tells us that there is an info package in the body.
>
>Nope. Not only might you have multiple bodies per INFO, you might have

>several different MIME types that might be usable with a given info- 
>package.
>
>For example, an image push app might use image/jpeg, image/gif, image/ 
>raw, etc. The package defines which type or types are allowed.
>>Wouldn't it be much simplier to define a generic mime, e.g.  
>>application/info-package, and then each info package only needs to 
>>define the Info-Package header value for that particular package?
>
>No, as some packages might well send two bodies in a single INFO.
>
>For example, envision a location-enabled image push: It sends an image/
jpeg and a pidf/lo that are correlated.
>
>You need the Info-Package header to tell you what two bodies to look
for and what they mean, and the MIME markup to know which is which.

[Christer] If we assume that we are NOT going to allow multiple packages
per INFO (nobody has objected to that restriction) we wouldn't have that
problem.



Paul:
=====

>>Let's assume I want to send an INFO with package foo.
>>  
>>The value of the Info-Package header is "foo", right?
>>  
>>Now, what is the value of the Content-Type header?
>
>The package could support a number of content types: image/jpeg,
text/plain, multipart/related, ...
>Anything that the definition of the package says is allowed.
>
>At least that is how I think Eric intended to to be.

[Christer] I agree that a package could be associated with a number of
content types. But, since the Info-Package header shows which package is
included, I just wonder why we can't use a common C-T mime.


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