[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per INFO]
Hi,
(I've put all text about this into a single reply)
Dean:
=====
>>>>Shouldn't we use Content-Type to indicate what is in the message
body?
>>>>After all, we may need Content-Length etc.
>>>
>>>Ah, no.
>>>
>>>We had extended conversations on this earlier. Content-Type tells
>>>you what's in the body; it just doesn't tell you what to DO with the
>>>body.
>>>
>>>What,From sip-bounces at ietf.org Thu Oct 23 23:19:51 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id E02DB3A68AA;
Thu, 23 Oct 2008 23:19:51 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id A2E753A6358
for <sip at core3.amsl.com>; Thu, 23 Oct 2008 23:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.213
X-Spam-Level:
X-Spam-Status: No, score=-6.213 tagged_above=-999 required=5 tests=[AWL=0.036,
BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id YooEkbgm7EeG for <sip at core3.amsl.com>;
Thu, 23 Oct 2008 23:19:49 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
by core3.amsl.com (Postfix) with ESMTP id 90FA03A690E
for <sip at ietf.org>; Thu, 23 Oct 2008 23:19:49 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
226D520C88; Fri, 24 Oct 2008 08:21:09 +0200 (CEST)
X-AuditID: c1b4fb3c-ab8c9bb0000015b5-2d-490169545364
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
F0B602074D; Fri, 24 Oct 2008 08:21:08 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
Fri, 24 Oct 2008 08:21:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 08:21:07 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF08955CCC at esealmw113.eemea.ericsson.se>
In-Reply-To: <5CE22097-8807-48B3-A9AA-2EDD4588D4A7 at softarmor.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
packages per INFO]
Thread-Index: Ack1exikY5eWTSdlRGeTTBK8RkCtEwAJGuxw
References: <48FDEAD8.8010803 at cisco.com>
<CA9998CD4A020D418654FCDEF4E707DF0889E49A at esealmw113.eemea.ericsson.se>
<48FF2C45.7010204 at cisco.com>
<CA9998CD4A020D418654FCDEF4E707DF088F10A7 at esealmw113.eemea.ericsson.se>
<093BE299-DB32-4012-AC94-405DE4D00FF9 at softarmor.com>
<CA9998CD4A020D418654FCDEF4E707DF083CCF9B at esealmw113.eemea.ericsson.se>
<5CE22097-8807-48B3-A9AA-2EDD4588D4A7 at softarmor.com>
From: "Christer Holmberg" <christer.holmberg at ericsson.com>
To: "Dean Willis" <dean.willis at softarmor.com>,
"Paul Kyzivat" <pkyzivat at cisco.com>
X-OriginalArrivalTime: 24 Oct 2008 06:21:08.0793 (UTC)
FILETIME=[B4036290:01C935A0]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip at ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
packages per INFO]
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
Hi,
(I've put all text about this into a single reply)
Dean:
=====
>>>>Shouldn't we use Content-Type to indicate what is in the message
body?
>>>>After all, we may need Content-Length etc.
>>>
>>>Ah, no.
>>>
>>>We had extended conversations on this earlier. Content-Type tells
>>>you what's in the body; it just doesn't tell you what to DO with the
>>>body.
>>>
>>>What, for exa for example, is the purpose of an image/jpeg in an INFO?
>>
>>That is not what I meant.
>>
>>We can use the Info-Package header, but can't we use a generic mime
>>value - which tells us that there is an info package in the body.
>
>Nope. Not only might you have multiple bodies per INFO, you might have
>several different MIME types that might be usable with a given info-
>package.
>
>For example, an image push app might use image/jpeg, image/gif, image/
>raw, etc. The package defines which type or types are allowed.
>>Wouldn't it be much simplier to define a generic mime, e.g.
>>application/info-package, and then each info package only needs to
>>define the Info-Package header value for that particular package?
>
>No, as some packages might well send two bodies in a single INFO.
>
>For example, envision a location-enabled image push: It sends an image/
jpeg and a pidf/lo that are correlated.
>
>You need the Info-Package header to tell you what two bodies to look
for and what they mean, and the MIME markup to know which is which.
[Christer] If we assume that we are NOT going to allow multiple packages
per INFO (nobody has objected to that restriction) we wouldn't have that
problem.
Paul:
=====
>>Let's assume I want to send an INFO with package foo.
>>
>>The value of the Info-Package header is "foo", right?
>>
>>Now, what is the value of the Content-Type header?
>
>The package could support a number of content types: image/jpeg,
text/plain, multipart/related, ...
>Anything that the definition of the package says is allowed.
>
>At least that is how I think Eric intended to to be.
[Christer] I agree that a package could be associated with a number of
content types. But, since the Info-Package header shows which package is
included, I just wonder why we can't use a common C-T mime.
Regards,
Christer
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
mple, is the purpose of an image/jpeg in an INFO?
>>
>>That is not what I meant.
>>
>>We can use the Info-Package header, but can't we use a generic mime
>>value - which tells us that there is an info package in the body.
>
>Nope. Not only might you have multiple bodies per INFO, you might have
>several different MIME types that might be usable with a given info-
>package.
>
>For example, an image push app might use image/jpeg, image/gif, image/
>raw, etc. The package defines which type or types are allowed.
>>Wouldn't it be much simplier to define a generic mime, e.g.
>>application/info-package, and then each info package only needs to
>>define the Info-Package header value for that particular package?
>
>No, as some packages might well send two bodies in a single INFO.
>
>For example, envision a location-enabled image push: It sends an image/
jpeg and a pidf/lo that are correlated.
>
>You need the Info-Package header to tell you what two bodies to look
for and what they mean, and the MIME markup to know which is which.
[Christer] If we assume that we are NOT going to allow multiple packages
per INFO (nobody has objected to that restriction) we wouldn't have that
problem.
Paul:
=====
>>Let's assume I want to send an INFO with package foo.
>>
>>The value of the Info-Package header is "foo", right?
>>
>>Now, what is the value of the Content-Type header?
>
>The package could support a number of content types: image/jpeg,
text/plain, multipart/related, ...
>Anything that the definition of the package says is allowed.
>
>At least that is how I think Eric intended to to be.
[Christer] I agree that a package could be associated with a number of
content types. But, since the Info-Package header shows which package is
included, I just wonder why we can't use a common C-T mime.
Regards,
Christer
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip