[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]
Christer Holmberg wrote:
So, just to make sure I understand: you are talking about a case where the INFO does contain a multipart message body, but only one of the mimes contains an actual info-package (the other mime(s) contains something else)?
pretty much. And to distinguish those, you need more than C-T.
But I think as we have been discussing, if we only allow one info
package per INFO, then the Info-Package header belongs in the message,
not in the body part.
I'll revise your example a bit:
INFO sip:foo at bar.com
To:...
From:...
Some-Header: CID:abcdefg
Info-Package: foo
Content-Type:multipart/mixed
Content-Length:...
--boundary
Content-Type: application/foo-data
Content-Disposition: package;handling=required
foo data
--boundary
Content-ID: abcdefg
Content-Type: application/some-header-data
Content-Disposition: by-reference;handling=optional
some other (non-info package) data
--boundary--
In the above I have used C-D of "package" to identify the part that
contains the info package. That is yet to be determined, but I think it
needs to be well defined, even if it is "render".
A more straightforward case would be:
INFO sip:foo at bar.com
To:...
From:...
Info-Package: foo
Content-Type: application/foo-data
Content-Disposition: package;handling=required
Content-Length:10
foo data
_______________________________________________
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
RRf3g6lMw8;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat at cisco.com; dkim=pass (
sig from cisco.com/rtpdkim2001 verified; );
Cc: SIP IETF <sip at ietf.org>, Dean Willis <dean.willis at softarmor.com>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
Christer Holmberg wrote:
So, just to make sure I understand: you are talking about a case where the INFO does contain a multipart message body, but only one of the mimes contains an actual info-package (the other mime(s) contains something else)?
pretty much. And to distinguish those, you need more than C-T.
But I think as we have been discussing, if we only allow one info
package per INFO, then the Info-Package header belongs in the message,
not in the body part.
I'll revise your example a bit:
INFO sip:foo at bar.com
To:...
From:...
Some-Header: CID:abcdefg
Info-Package: foo
Content-Type:multipart/mixed
Content-Length:...
--boundary
Content-Type: application/foo-data
Content-Disposition: package;handling=required
foo data
--boundary
Content-ID: abcdefg
Content-Type: application/some-header-data
Content-Disposition: by-reference;handling=optional
some other (non-info package) data
--boundary--
In the above I have used C-D of "package" to identify the part that
contains the info package. That is yet to be determined, but I think it
needs to be well defined, even if it is "render".
A more straightforward case would be:
INFO sip:foo at bar.com
To:...
From:...
Info-Package: foo
Content-Type: application/foo-data
Content-Disposition: package;handling=required
Content-Length:10
foo data
_______________________________________________
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