Re: [Sip] MESSAGE for rendering

Paul Kyzivat <pkyzivat@cisco.com> Wed, 19 December 2007 00:11 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4mWm-0006pI-Ju; Tue, 18 Dec 2007 19:11:12 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J4mWl-0006pD-Ao for sip-confirm+ok@megatron.ietf.org; Tue, 18 Dec 2007 19:11:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4mWk-0006p4-VI for sip@ietf.org; Tue, 18 Dec 2007 19:11:11 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4mWk-00044d-HC for sip@ietf.org; Tue, 18 Dec 2007 19:11:10 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 18 Dec 2007 19:11:10 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lBJ0B9EL001123; Tue, 18 Dec 2007 19:11:09 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lBJ05Ril005824; Wed, 19 Dec 2007 00:11:08 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Dec 2007 19:07:18 -0500
Received: from [161.44.174.118] ([161.44.174.118]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Dec 2007 19:07:18 -0500
Message-ID: <476860B7.1090603@cisco.com>
Date: Tue, 18 Dec 2007 19:07:19 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [Sip] MESSAGE for rendering
References: <E6C2E8958BA59A4FB960963D475F7AC30273B2D97F@mail.acmepacket.com> <4762FB8B.2020308@cisco.com> <200712142327.lBENRjRq023454@dragon.ariadne.com> <E6C2E8958BA59A4FB960963D475F7AC30273B2DF33@mail.acmepacket.com> <47631BA9.5040904@cisco.com> <476819FE.6060406@ericsson.com> <0EA88CBE-EE81-4AB4-9AD3-56B75B710485@softarmor.com> <476858D7.9080209@cisco.com>
In-Reply-To: <476858D7.9080209@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Dec 2007 00:07:18.0083 (UTC) FILETIME=[1E362930:01C841D3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2491; t=1198023069; x=1198887069; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[Sip]=20MESSAGE=20for=20rendering |Sender:=20 |To:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>; bh=bSIiLGr6jDO+TnZ7Xsm+w9ExbW5lusNuiNQao/R8ACM=; b=IYePJotkyw0LGkZ3SmJ3FaSFZgBub+RVrDZ16jFADjtkd8arH68HS3PZyU S8mTz6YmDhiZsWpOMfIjc4tTkEw5No4NMuq/31UpaQqQGgFqbFgmxRgmLQ/T 6AFtYw4HsR;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: "sip@ietf.org" <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

I agree with Jonathan re the rendering.

Regarding suitability of using MESSAGE in a sip dialog for this, I think 
its suitability for this is no better or worse than for sending the 
actual text itself. I suppose the is-typing functionality increases the 
number of messages used by roughly a factor of two. If you thought 
MESSAGE was suitable without this, then you might still think it is 
suitable with it.

Its probably not a good example. The point is that rendering doesn't 
necessarily mean literal rendering of communicated text. E.g. you could 
send some MIDI encoding and have it rendered audibly.

	Paul

Jonathan Rosenberg wrote:
> I think application/im-iscomposing+xml IS rendered; and its rendering 
> causes the UI to show that the user is typing.
> 
> 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.
> 
> 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.
> 
> -Jonathan R.
> 
> Dean Willis wrote:
>>
>> On Dec 18, 2007, at 1:05 PM, Salvatore Loreto wrote:
>>
>>> Hi Paul,
>>>
>>> just to add another example to this discussion (same as the vcard 
>>> example):
>>> an application/im-iscomposing+xml content-type can be put in the body 
>>> of a SIP MESSAGE and it is not (or it is not supposed to be) rendered
>>> as is to the recipient; an application that understood it would 
>>> render it in whatever way it indicates that a user is in the process 
>>> of composing a message.
>>>
>>
>> Okay, I'm now completely convinced that most uses of MESSAGE are 
>> really candidates for the new INFO events.
>>
>> -- 
>> Dean
>>
>> _______________________________________________
>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>>
> 


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip