RE: [Sip] MESSAGE for rendering

Hadriel Kaplan <HKaplan@acmepacket.com> Fri, 14 December 2007 23:14 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 1J3JjO-0005Wt-IG; Fri, 14 Dec 2007 18:14:10 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J3JjM-0005Wo-6f for sip-confirm+ok@megatron.ietf.org; Fri, 14 Dec 2007 18:14:08 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3JjL-0005Wg-SR for sip@ietf.org; Fri, 14 Dec 2007 18:14:07 -0500
Received: from host6.216.41.24.conversent.net ([216.41.24.6] helo=etmail.acmepacket.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J3JjL-00067L-HC for sip@ietf.org; Fri, 14 Dec 2007 18:14:07 -0500
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.0.751.0; Fri, 14 Dec 2007 18:14:07 -0500
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Fri, 14 Dec 2007 18:14:07 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Date: Fri, 14 Dec 2007 18:09:22 -0500
Subject: RE: [Sip] MESSAGE for rendering
Thread-Topic: [Sip] MESSAGE for rendering
Thread-Index: Acg+m+WjXgBStFcCTsabr5d22PWf7QABT6cg
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30273B2DF10@mail.acmepacket.com>
References: <E6C2E8958BA59A4FB960963D475F7AC30273B2D97F@mail.acmepacket.com> <4762FB8B.2020308@cisco.com>
In-Reply-To: <4762FB8B.2020308@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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


> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Friday, December 14, 2007 4:54 PM
> To: Hadriel Kaplan
> Cc: sip@ietf.org
> Subject: Re: [Sip] MESSAGE for rendering
>
> 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?

I guess the question is if "render" is synonymous with "inline", as 3261 sounds like it is?  If so, then I think you're right "render" is wrong.  How is it done in email?  I think content-disposition "attachment" vs. inline.  So yeah, the question is if MESSAGE can handle non-render ones.  (clearly "session" would NOT be valid :)

-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