DRAGE, Keith (Keith) wrote:
To comment on the multipart body question below, my understanding of the
requirement from the previous discussion is that it does not come from
the need to send two info packages at the same time.
Rather it comes from the need to send an info package plus some other
associated but yet to be described message body that happens to be
needed to be sent at the same time (e.g. info package containing a
Geolocation header pointing to a geolocation body in the same message).
If we could eliminate this, we could get rid of it, but I suspect we
cannot.
Given this, the support of multiple packages comes for free, so why
eliminate it.
Free? Certainly not.
If, as an implementor, all I care about is INFO, and I don't have any
other use case for multipart (which, as of now, are mostly niche uses
and are not common), I'll now NEED to implement multipart for INFO.
So, I don't have a problem saying that INFO can contain multiple bodies
as any message can, but I do have a problem with the idea that the INFO
framework ITSELF allows multiple packages per INFO.
-Jonathan R.
--
Jonathan D. Rosenberg, Ph.D. 111 Wood Avenue South
Cisco Fellow Iselin, NJ 08830
Cisco, Voice Technology Group
[EMAIL PROTECTED]
http://www.jdrosen.net PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
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
