Re: [Sip] MESSAGE for rendering

Paul Kyzivat <pkyzivat@cisco.com> Wed, 19 December 2007 12:59 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 1J4yWV-00028H-Fa; Wed, 19 Dec 2007 07:59:43 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J4yWU-00027Y-3J for sip-confirm+ok@megatron.ietf.org; Wed, 19 Dec 2007 07:59:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4yWT-00027P-OT for sip@ietf.org; Wed, 19 Dec 2007 07:59:41 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4yWT-0000jy-Da for sip@ietf.org; Wed, 19 Dec 2007 07:59:41 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 19 Dec 2007 07:59:39 -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 lBJCxcpJ009804; Wed, 19 Dec 2007 07:59:38 -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 lBJCxHil004945; Wed, 19 Dec 2007 12:59:38 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); Wed, 19 Dec 2007 07:59:22 -0500
Received: from [10.86.248.47] ([10.86.248.47]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 19 Dec 2007 07:59:21 -0500
Message-ID: <476915A9.8090309@cisco.com>
Date: Wed, 19 Dec 2007 07:59:21 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.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> <9F8EAFA7-33E1-4C09-9014-22ECB462C127@softarmor.com>
In-Reply-To: <9F8EAFA7-33E1-4C09-9014-22ECB462C127@softarmor.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Dec 2007 12:59:21.0861 (UTC) FILETIME=[F955BB50:01C8423E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1344; t=1198069179; x=1198933179; 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:=20Dean=20Willis=20<dean.willis@softarmor.com>; bh=R7xwn02HxTFhdDhI4wkB30wkkB7pTNYIhV3Ai9Bpt0Q=; b=0Y/s7B+3y2mDbXDSAoc5moTJgHmIqeh51a2CI+60dwdDO3/TUOukAYquuY nnckgeR2LEU6F+bqKnmvg8SkrYMr2MKxwyYVVNnD3h6HGx49401QU+p+5AU/ BaGNLaX2/f;
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: 52e1467c2184c31006318542db5614d5
Cc: "sip@ietf.org" <sip@ietf.org>
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


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.

Do you think its ok for the message to contain html?

If you rendered html text directly it would also confuse your mom.

Whatever is sent is just an *encoding* that must be translated into a 
meaningful rendering for the recipient.

	Paul


_______________________________________________
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