From: Dean Willis <[EMAIL PROTECTED]> There was a lot of discussion around the first of the month.
Where are we now? There is an open discussion point on the precise semantics of 'required' -- in the SIP context, it is probably more convenient to mean "required for processing of the containing body part", but in the e-mail gateway context, it is used to mean "required for the overall message to be processed". (The two are equivalent for non-nested multiparts.) My elaborate algorithm is, IMHO, a direct expression of the rules in the I-D, although I've probably added some "it could only mean this" assumptions which should be made explicit. Whether the algorithm itself is given in the I-D is a presentation issue. If the algorithm it too complex to implement, we must simplify the I-D. I think we should make some statement that multipart/related should not be used unless it is "protected" by some extension-requirement that ensures the recipient can process multipart/related. Dale _______________________________________________ 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
