An interesting optimization, but it doesn't appeal to me: * if they're out of sync, which one takes precedence (that is, do I process a Content-Type that isn't listed in the Content-Type-List?) * if a UA knew an intermediate box used Content-Type-List, the UA could use Content-Type-List to make the intermediate box think some sort of Content-Type is not present. That additional content-type might contain the secret of the universe, which the intermediate box really needed to know. * looking for "^Content-Type *:" isn't too hard; you don't really need to bother parsing MIME and looking for nested parts unless there is, in fact, a content-type you care about. Per Paul's message, if you only want ones with Content-Disposition: session, you could look for that string within 4-5 lines of Content-Type; if you found it, then you could parse the MIME in the body.
-d > -----Original Message----- > From: Christer Holmberg (JO/LMF) > [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 10, 2007 6:44 PM > To: Paul Kyzivat; Dan Wing > Cc: [EMAIL PROTECTED]; [email protected] > Subject: RE: [Sip] Support for Multipart/MIME > > > Hi, > > The following is not a proposal, but more "brain storming". > > Would it be helpful to have a SIP header, e.g. > Content-Type-List, which > would list the different Content-Types in a multipart/* body. > > A node could then first check that header in order to see whether the > multipart/* contains something a specific node is interested in - > without having to parse the full multipart/* body first. It > could speed > up the processing in nodes which may have interest only in a small set > of Content-Types. > > Comments? > > Regards, > > Christer _______________________________________________ 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
