> >Once we get down to a decision of supporting nested versus > >not supporting nesting, presumably we are then entirely in > >the realm of the multipart coding itself. > > > >Could I ask someone to elaborate on what generic requirements > >already exist within multipart/mime in this respect, before > >we start looking at defining SIP specific rules or indications? > > I am very sure that I have seen text related to the support of nested > multiparts, and what nodes are expected to support, > somewhere, but I yet have not found it.
message/rfc822 [RFC2046], which is used when you forward a message, routinely has nested multiparts when the message you're forwarding itself had multiple parts. It looks something like this: From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Content-Type: multipart/mixed; boundary=A --A Content-Type: text/plain here is that email I mentioned during lunch. --A Content-Type: message/rfc822 From: Sammy Sammython <[EMAIL PROTECTED]> Content-Type: multipart/mixed; boundary=B Subject: Pictures from our recent trip --B Content-Type: text/plain Here are the pictures from the island! Enjoy! --B Content-Type: image/jpg Content-Transfer-Encoding: base64 EKFEJKFIEUJKEJKEJFF ... --B Content-Type: image/jpg Content-Transfer-Encoding: base64 EKFEJKFIEUJKEJKEJFF ... --B-- --A-- -d _______________________________________________ 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
