From: "Christer Holmberg (JO/LMF)" <[EMAIL PROTECTED]> Now, if this text is not specific to ISUP and QSIG, but to binary data in general, I think it needs to be documented in Gonzalo's draft. Because, it seems to be one example of where we "override" the generic MIME rules (I haven't check, but the text says that some rules in RFC2045 does not apply to SIP...).
Well, we probably should document it. But SIP is not an exception, *e-mail* is, as far as I can tell from scanning through 2045: Mail transport for unencoded 8bit data is defined in RFC 1652. As of the initial publication of this document, there are no standardized Internet mail transports for which it is legitimate to include unencoded binary data in mail bodies. Thus there are no circumstances in which the "binary" Content-Transfer-Encoding is actually valid in Internet mail. However, in the event that binary mail transport becomes a reality in Internet mail, or when MIME is used in conjunction with any other binary-capable mail transport mechanism, binary bodies must be labelled as such using this mechanism. Dale _______________________________________________ Sip mailing list https://www1.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
