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

Correct.

On Oct 23, 2008, at 4:07 PM, Paul Kyzivat wrote:

>
>
> Christer Holmberg wrote:
>> Hi,
>> 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.
>
> 	Paul
>
>> Is it something which is generic for all info packages (e.g.  
>> application/info), OR is it something which is specified in the foo  
>> package description?
>> Regards,
>> Christer
>> ________________________________
>> From: Paul Kyzivat [mailto:[email protected]]
>> Sent: Thu 23/10/2008 20:21
>> To: Christer Holmberg
>> Cc: Dean Willis; SIP IETF; Eric Burger
>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs  
>> Info-Package [was RE: draft-ietf-sip-info-events-00: multiple  
>> packages per INFO]
>> Christer,
>> I don't understand where you are heading with this?
>> If I want to send an INFO with a jpeg, then what is this other mime  
>> type
>> doing other than getting in my way.
>> OTOH, we haven't discussed Content-Disposition wrt INFO. In the  
>> absence
>> of any mention, I assume that "render" will be used for info  
>> packages,
>> and the detailed processing defined by the Info-Package value.
>> In some sense, the Info-Package value is serving the same purpose as
>> Content-Disposition. We could *consider* using the C-D *instead* of  
>> the
>> Info-Package header, so that what we would be negotiating would be  
>> the
>> acceptable C-D values. The downside of that is that we would then  
>> need
>> to open up the registration of new C-D values. I think that might be
>> opposed by a lot of people.
>>        Thanks,
>>        Paul
>> Christer Holmberg wrote:
>>> Hi,
>>>
>>>>> 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.
>>>
>>> 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