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:[EMAIL PROTECTED]
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:[EMAIL PROTECTED]
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 [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
