> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean > Willis > > But if there are multiple body parts (only one of which is an INFO > body) , INFO requires a mechanism for finding the right body part.
Isn't there some rule somewhere about the order of the body parts making a difference if multiples of the same type/disp are received? Or am I having a memory corruption? Like since the INFO package is the generator of the message, can't we just say the first/top-most one is the package's? Maybe I'm dreaming. > We can't delimit this based on the MIME type for the same reason we > can't just do a one-to-one map between INFO and MIME -- sometimes a > single MIME type is used in different ways for different applications. *Only* devices supporting that specific INFO package would need to care. Since we'll have an indication/negotiation of support for specific INFO packages, only devices which implement support for such packages would need to discern such an ambiguity. We don't have this problem right now, because we don't have such a package in mind. Ergo we don't need to solve it. Let the specific package definitions do it if they need it - make them pay the price for their issue. -hadriel p.s. and I'm only arguing to reduce this thing because the main carrot for this draft was to not make it much more work for developers from current INFO usage. It doesn't have to be perfect - just good enough. _______________________________________________ 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
