Re: [Sip] MESSAGE for rendering

Dean Willis <dean.willis@softarmor.com> Wed, 19 December 2007 13:50 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 1J4zK4-0005y1-5D; Wed, 19 Dec 2007 08:50:56 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J4zK2-0005tc-1B for sip-confirm+ok@megatron.ietf.org; Wed, 19 Dec 2007 08:50:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4zK1-0005rN-LY for sip@ietf.org; Wed, 19 Dec 2007 08:50:53 -0500
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J4zK0-0005vz-7g for sip@ietf.org; Wed, 19 Dec 2007 08:50:53 -0500
Received: from [10.240.23.39] (m6e5f36d0.tmodns.net [208.54.95.110]) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id lBJDoj24005243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 19 Dec 2007 07:50:46 -0600
In-Reply-To: <476915A9.8090309@cisco.com>
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> <476915A9.8090309@cisco.com>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <D4F1A952-6C68-4AD6-A78F-296439C66B84@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] MESSAGE for rendering
Date: Wed, 19 Dec 2007 07:50:38 -0600
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.753)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

On Dec 19, 2007, at 6:59 AM, Paul Kyzivat wrote:
>
> Do you think its ok for the message to contain html?
>

That's actually debatable.

HTML at least has relatively standard "rendering"  -- XML, especially  
in the absence of some kind of style sheet, doesn't.

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

True. It would be nice to make sue her UA supports HTML before  
sending it to her, wouldn't it?

But at least here (this use of MESSAGE) we have an existing way to  
say "I don't support that MIME type in a render-to-user context",  
which may be adequate. That does put is in a better position than we  
were with INFO.

--
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