RE: [Sip] MESSAGE for rendering
Hadriel Kaplan <HKaplan@acmepacket.com> Fri, 14 December 2007 23:39 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 1J3K7f-0008UJ-AY; Fri, 14 Dec 2007 18:39:15 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J3K7d-0008UE-Mx for sip-confirm+ok@megatron.ietf.org; Fri, 14 Dec 2007 18:39:13 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J3K7d-0008U6-BE for sip@ietf.org; Fri, 14 Dec 2007 18:39:13 -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 1J3K7c-0006hB-So for sip@ietf.org; Fri, 14 Dec 2007 18:39:13 -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:39:12 -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:39:12 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Dale.Worley@comcast.net" <Dale.Worley@comcast.net>, "sip@ietf.org" <sip@ietf.org>
Date: Fri, 14 Dec 2007 18:34:29 -0500
Subject: RE: [Sip] MESSAGE for rendering
Thread-Topic: [Sip] MESSAGE for rendering
Thread-Index: Acg+qPY4r2ZirmevQhuvCL41KY8J0gAAGwvQ
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30273B2DF33@mail.acmepacket.com>
References: <E6C2E8958BA59A4FB960963D475F7AC30273B2D97F@mail.acmepacket.com> <4762FB8B.2020308@cisco.com> <200712142327.lBENRjRq023454@dragon.ariadne.com>
In-Reply-To: <200712142327.lBENRjRq023454@dragon.ariadne.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: 02ec665d00de228c50c93ed6b5e4fc1a
Cc:
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
More importantly MESSAGE allows out-of-dialog requests. :) I was thinking the same as you, but I believe Paul's right in that render=inline and vcard/vcalendar are not inline. The question is if we want to let "attachment" disposition be allowed. I dread to do that, because people are already using MESSAGE to transfer 10MB images, but that's a separate ugly problem. :( -hadriel > -----Original Message----- > From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net] > Sent: Friday, December 14, 2007 6:28 PM > To: sip@ietf.org > Subject: Re: [Sip] MESSAGE for rendering > > From: Paul Kyzivat <pkyzivat@cisco.com> > > 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. > > IMHO, filing information is as good as actually rendering it. The > real question is layering -- "render" means "deliver to the layer > above the SIP UA". Anything that partakes of media is "rendered" and > is acceptable for MESSAGE, anything that partakes of signaling is not > "rendered" and is acceptable for INFO. > > One criterion is "Would it make sense to let the user arbitrarily > re-route where this information goes?" With a vcard, it makes sense. > With the information INFO was intended to carry, it does not: > > RFC 2976 1.1 Example Uses > > The following are a few of the potential uses of the INFO message: > > - Carrying mid-call PSTN signaling messages between PSTN > gateways. > > - Carrying DTMF digits generated during a SIP session. > > - Carrying wireless signal strength information in support of > wireless mobility applications. > > - Carrying account balance information. > [in a pay-as-you-go network -- DRW] > > Dale > > > _______________________________________________ > 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