Re: MESSAGE for rendering

This is an aspect of the ongoing attempt to nail down what
the content 
dispositions mean, and whether they mean the same thing for
all methods. 
Its especially pertinent for "render" because that
is the default 
disposition code for sip body parts, and because its far
from clear that 
"render" could mean the same thing for all
methods.

	Paul

David R Oran wrote:
> Perhaps the salient difference isn't whether the
contents are directly 
> rendered (or indirectly rendered), but whether there
are additional 
> side-effects that alter an application-level state
machine.
> 
> On Dec 19, 2007, at 12:21 AM, Dean Willis wrote:
> 
>>
>> On Dec 18, 2007, at 5:33 PM, Jonathan Rosenberg
wrote:
>>
>>> I think application/im-iscomposing+xml IS
rendered; and its rendering 
>>> causes the UI to show that the user is typing.
>>>
>>
>> I think INVITE is rendered, and its rendering
causes the uses phone to 
>> make a ringing nose that causes the user to press a
button that causes 
>> a new message to be sent.
>>
>>> As a litmus test for this stuff, a question is
whether it can 
>>> reasonably be converted to a text/plain content
and sent in a 
>>> MESSAGE, and if it is rendered, is the
resulting behavior reasonable. 
>>> For the iscomposing indicators, I think you
could. You could instead 
>>> send a text IM like "Joe is typing a
reply..." and render that, and 
>>> this would achieve the same objective.
>>
>> If you displayed the current iscomposing object on 
the screen, I'm 
>> afraid you'd just confuse my mom. It's not just
text.
>>
>> Before you send it, you really need to know that
the other end 
>> understands what you mean. That's the crux of what
is wrong with INFO 
>> today.
>>
>>> Also, I would not want to send iscomposing over
the SIP dialog - I 
>>> think it should be on the media path. There
will be a LOT of them, 
>>> and there is a requirement for timeliness. See
my other note on the 
>>> criteria for sending something in dialog vs.
along the media path.
>>>
>>
>> Well, that's reasonable, but we have what we have,
and that's a SIP 
>> message for iscomposing, and probably some IPR on
that too.
>>
>> -- 
>> Dean
>>
>>
>> _______________________________________________
>> Sip mailing list  https://ww
w1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP
Protocol
>> Use sip-implementorscs.columbia.edu for
questions on current sip
>> Use sippingietf.org for new developments on the
application of sip
> 


_______________________________________________
Sip mailing list  https://ww
w1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementorscs.columbia.edu for questions on current
sip
Use sippingietf.org for new developments on the application of
sip