On Nov 6, 2011, at 8:47 PM, Hadriel Kaplan wrote: > > On Nov 6, 2011, at 9:55 PM, Worley, Dale R (Dale) wrote: > >>> From: Cullen Jennings [[email protected]] >>> >>>> Although of course, RFC 3261 violates this rule. >>> >>> Really - I don't think so. I think people are confused what binary mean. >> >> Well, in section 23.4.2 I see: >> >> Content-Type: application/pkcs7-signature; name=smime.p7s >> Content-Transfer-Encoding: base64 >> Content-Disposition: attachment; filename=smime.p7s; >> handling=required >> >> which appears to violate the specification that binary body parts are >> to be sent in binary. > > RFC 3853 updates 3261 with not only support for AES encryption of S/MIME, but > also this paragraph: > > Since SIP is 8-bit clean, all implementations MUST use 8-bit binary > Content-Transfer-Encoding for S/MIME in SIP. Implementations MAY > also be able to receive base-64 Content-Transfer-Encoding. > > > But this S/MIME discussion is like arguing about the length of horn a unicorn > must have. ;) > > -hadriel
Well I think Hadriel about nailed it. And with that I will go back to reading http://www.microsoft.com/presspass/press/2005/nov05/11-09icenatpr.mspx > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
