On 7/7/08 12:03 PM, Paul Kyzivat wrote:
Adam Roach wrote:
On 7/4/08 1:28 PM, Paul Kyzivat wrote:
Adam,
I have to admit that I still haven't grokked the distinction between
multipart/mixed and multipart/related.
From a data structures perspective, multipart/mixed is an unordered
set, while multipart/related is a tree. The difference is actually
pretty radical.
I just went and reviewed RFC2387 *again*. I think my problem with it
is that I don't know where it was *intended* to be used. It clearly
wasn't *intended* to be used with SIP.
Now that I look again in the context of this discussion, it seems,
IMO, to be *inappropriate* for many cases where we are likely to have
multiple body parts in a sip message.
Consider the case of an INVITE that has SDP and a body part referenced
by an Alert-Info header. These two are not related at all, and neither
is the "starting" body part. They are each independently related to
the sip message itself.
So, what uses do you have in mind for multipart/related? Without some
specific and tangible ones, it is hard to justify making sip-specific
interpretations of it in this general document.
RFC 4662.
In a closely related vein (the one that shows where Content-Disposition
may be necessary), see also draft-roach-list-subscribe-bodies-00.
/a
_______________________________________________
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
