[Sip] MESSAGE for rendering

Hadriel Kaplan <HKaplan@acmepacket.com> Fri, 14 December 2007 17:32 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3EP8-0006tZ-R8; Fri, 14 Dec 2007 12:32:54 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J3EP7-0006tS-93 for sip-confirm+ok@megatron.ietf.org; Fri, 14 Dec 2007 12:32:53 -0500
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3EP6-0006tJ-Vf for sip@ietf.org; Fri, 14 Dec 2007 12:32:52 -0500
Received: from host6.216.41.24.conversent.net ([] helo=etmail.acmepacket.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J3EP6-00039V-N0 for sip@ietf.org; Fri, 14 Dec 2007 12:32:52 -0500
Received: from mail.acmepacket.com ( by etmail.acmepacket.com ( with Microsoft SMTP Server (TLS) id 8.0.751.0; Fri, 14 Dec 2007 12:32:52 -0500
Received: from mail.acmepacket.com ([]) by mail.acmepacket.com ([]) with mapi; Fri, 14 Dec 2007 12:32:52 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "sip@ietf.org" <sip@ietf.org>
Date: Fri, 14 Dec 2007 12:27:52 -0500
Thread-Topic: MESSAGE for rendering
Thread-Index: Acg+dqgqYS7BX6waS9O7owPwRjXqag==
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30273B2D97F@mail.acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: [Sip] MESSAGE for rendering
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

Regarding the INFO use-case discussion, one comment from people is MESSAGE is really for things to be rendered to the user, and not for such things as vcards or vcalendars.  Not that I want to contradict myself on it being a valid use-case for INFO, but personally I'm not so sure that vcard/vcalendar is wrong for MESSAGE.  I mean we can argue if sending that type of data is really justification for an "Instant Message" request, but I'm talking more about whether content that isn't directly rendered to the user can be put into MESSAGE.

In some ways a vcard/vcalendar *is* being rendered to the user - it's just that by definition the content type is formatted in a vcard or vcalendar format and needs to be interpreted, if the app understands it.  Just as, for example, a MESSAGE can contain message/cpim when we don't really expect to visibly render the message/cpim headers without interpretation.

It just so happens that some applications know a vcard/vcalendar type content can be integrated into their contact or calendar program, and bypass "rendering" it directly to the user in visible form.  From a SIP protocol perspective it is still user "data" for "rendering".


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