Re the question about multiple packages per INFO:
There MUST be exactly one Info Package type listed per Info-Package
header. Multiple Info-Packages per INFO message are disallowed.
[EDITOR NOTE: Really? Why not multiple Info-Packages, in a
multipart/mime? Well, I thought of one: it is hard to disambiguate.
For example, take an INFO message with an Info-Package: key_image,
caller_picture. I then have a multipart/mime with, you guessed it,
an image/jpeg and an image/jpeg. I would offer we do allow this and
require the MIME parse order of the body match the order of the Info-
Package enumerations; if you have too many packages or body parts or
they do not align, you barf. However, I timed out on this and thus
we will have to wait for the next version for me to flesh this out.
If we do do this, then we'll reference RFC 3261 as updated by
draft-ietf-sip-body-handling to require multipart MIME handling.]
How about defining an initial package type of "multipart". It allows
only content-type multipart/mixed. Then each contained type must have
its own Info-Package header. If you want to allow multiple packages per
INFO then you need to negotiate support for "multipart". Or maybe we
require support of multipart if you support any other package type.
Thanks,
Paul
_______________________________________________
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
