DRAGE, Keith (Keith) wrote:
Should we even allow bodies that do not relate to info packages in INFO
messages (legacy issues excepted).
I think we must allow it. The use case I have in mind is when there is a
header in the message that contains a URI, and the desire is to use a
CID URI referencing a body part in the message. (To avoid the need to
have or access a separate server.
An example of this would be a Geolocation header. (Although the draft
for that seems to have expired.)
I don't know if that precise case makes practical sense, but its an
example of a general mechanism we have that should not be excluded.
Another example (though improbable) is an S/MIME body.
If I had a SDP offer to send at the same time as a body for an info
package, I suspect I would be told to send one in a reINVITE and the
other in an INFO, rather than combine them in a single message.
Yes, it is certainly true that sending a SDP for purposes of O/A is
inappropriate in INFO.
Whatever the answer to this question, I guest the draft would need a
paragraph to cover it.
Yes, I agree.
Thanks,
Paul
Regards
Keith
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dean Willis
Sent: Friday, October 24, 2008 10:36 PM
To: Christer Holmberg
Cc: SIP IETF; Paul Kyzivat
Subject: Re: [Sip] draft-ietf-sip-info-events-00:
Content-Type vsInfo-Package [was RE:
draft-ietf-sip-info-events-00: multiplepackages per INFO]
On Oct 24, 2008, at 4:32 PM, Christer Holmberg wrote:
Hi,
[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.
Then which of the multiple bodies, each of which carries
the same C-T
mime marking, is which? Are you relying on ordering?
Let's assume BOTH bodies contain C-T: image/jpeg. How do you know
which is associated with the info package?
So you have a multipart body, with one or more parts related to an
INFO package, and other parts related to something else, such
as AIB,
E2M, etc. Right?
The content-disposition of the body parts related to INFO packages
needs to differentiate them from the other body parts.
--
Dean
_______________________________________________
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
_______________________________________________
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
