Re: [Sip] MESSAGE for rendering
Paul Kyzivat <pkyzivat@cisco.com> Fri, 14 December 2007 21:54 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 1J3IUG-0005n0-U5; Fri, 14 Dec 2007 16:54:28 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J3IUF-0005fa-Fr for sip-confirm+ok@megatron.ietf.org; Fri, 14 Dec 2007 16:54:27 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3IUF-0005ck-3j for sip@ietf.org; Fri, 14 Dec 2007 16:54:27 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3IUE-0003is-NO for sip@ietf.org; Fri, 14 Dec 2007 16:54:27 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 14 Dec 2007 16:54:26 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lBELsQR7013545; Fri, 14 Dec 2007 16:54:26 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lBELs9ZS027697; Fri, 14 Dec 2007 21:54:26 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 14 Dec 2007 16:54:19 -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); Fri, 14 Dec 2007 16:54:19 -0500
Message-ID: <4762FB8B.2020308@cisco.com>
Date: Fri, 14 Dec 2007 16:54:19 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: [Sip] MESSAGE for rendering
References: <E6C2E8958BA59A4FB960963D475F7AC30273B2D97F@mail.acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC30273B2D97F@mail.acmepacket.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2007 21:54:19.0555 (UTC) FILETIME=[E0FC6730:01C83E9B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2022; t=1197669266; x=1198533266; c=relaxed/simple; s=rtpdkim1001; 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:=20Hadriel=20Kaplan=20<HKaplan@acmepacket.com>; bh=wv6F/HPL3oiwiks0MKS8od1enqXRdZZtlL9V12YkEMA=; b=Gl4g0cjaBvgZ1W6bBHpa5z1zyhKzL0ND8jXZjCbYHAmyFYb91xe5c0hw5p TsLHOuFTYc6fCrUi1U1cHe1MK/X6nCBZTZO9WonmkGtsf8kfatrbSX0ELiqj 9oGWp7f5i0;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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
Hadriel, I am entirely with you if the *intent* of sending the vcard is to render it to the user in some human readable way. Its hardly any different from sending HTML. Its much more questionable if the intent is that the vcard be filed in the recipients address book without being rendered. Even so, I think it is an open question whether content-dispositions other than "render" are valid with MESSAGE. And if so, which ones? Paul Hadriel Kaplan wrote: > 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". > > -hadriel > > > _______________________________________________ > 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
- [Sip] MESSAGE for rendering Hadriel Kaplan
- Re: [Sip] MESSAGE for rendering Paul Kyzivat
- RE: [Sip] MESSAGE for rendering Hadriel Kaplan
- Re: [Sip] MESSAGE for rendering Dale.Worley
- RE: [Sip] MESSAGE for rendering Hadriel Kaplan
- Re: [Sip] MESSAGE for rendering Paul Kyzivat
- Re: [Sip] MESSAGE for rendering Paul Kyzivat
- Re: [Sip] MESSAGE for rendering Paul Kyzivat
- Re: [Sip] MESSAGE for rendering Salvatore Loreto
- Re: [Sip] MESSAGE for rendering Dean Willis
- Re: [Sip] MESSAGE for rendering Jonathan Rosenberg
- Re: [Sip] MESSAGE for rendering Paul Kyzivat
- Re: [Sip] MESSAGE for rendering Dean Willis
- Re: [Sip] MESSAGE for rendering Paul Kyzivat
- Re: [Sip] MESSAGE for rendering Dean Willis
- Re: [Sip] MESSAGE for rendering Dean Willis
- Re: [Sip] MESSAGE for rendering David R Oran
- Re: [Sip] MESSAGE for rendering Paul Kyzivat