Re: [Sip] MESSAGE for rendering

Jonathan Rosenberg <jdrosen@cisco.com> Tue, 18 December 2007 23:33 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 1J4lvz-0000C4-1V; Tue, 18 Dec 2007 18:33:11 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J4lvx-0000Bw-Du for sip-confirm+ok@megatron.ietf.org; Tue, 18 Dec 2007 18:33:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4lvx-0000Bo-0y for sip@ietf.org; Tue, 18 Dec 2007 18:33:09 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4lvw-0002p9-Aw for sip@ietf.org; Tue, 18 Dec 2007 18:33:09 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 18 Dec 2007 15:33:07 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id lBINX7gq010044; Tue, 18 Dec 2007 15:33:07 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lBINX3LE026308; Tue, 18 Dec 2007 23:33:03 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Dec 2007 15:33:03 -0800
Received: from [64.101.76.25] ([64.101.76.25]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Dec 2007 15:33:02 -0800
Message-ID: <476858D7.9080209@cisco.com>
Date: Tue, 18 Dec 2007 18:33:43 -0500
From: Jonathan Rosenberg <jdrosen@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>
In-Reply-To: <0EA88CBE-EE81-4AB4-9AD3-56B75B710485@softarmor.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Dec 2007 23:33:02.0950 (UTC) FILETIME=[5541C060:01C841CE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2050; t=1198020787; x=1198884787; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:=20Re=3A=20[Sip]=20MESSAGE=20for=20rendering |Sender:=20; bh=0ijw3g8YPxLqWnS82zTvYmV6sb9ddp7ZwIxsLhWlSJc=; b=mPRs+YTpBP+x7AR7kJqeuXqLQyzm1dpfDj6YrmUCGtPUywJ14O4NQWlLkz Ze+AlL43k6Q/sN7j+p64sQeISU3EZOx857RYEysPbvcCtYMt3VWwOdqEumJ/ sz3BZPE5k0;
Authentication-Results: sj-dkim-4; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: "sip@ietf.org" <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.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 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
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com


_______________________________________________
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