On Nov 1, 2011, at 12:03 AM, Iñaki Baz Castillo wrote: > Thanks Kevin. But anyhow it seems that there is no SIP spec/RFC > defining a binary body, am I wrong?
RFC 3204 is used for ISUP and QSIG bodies, for example in SIP-T/SIP-I scenarios. And that really is used by SIP in the real world - a LOT. (not by user endpoints though obviously) RFC 3853 defines S/MIME AES as binary in SIP, though I don't know of anyone implementing that. Microsoft sends binary-enoded MIME payloads in SIP MESSAGE requests in certain Instant-Messaging use-cases. And someone sends binary encoded payloads for DTMF indications in SIP NOTIFY requests - I don't remember who it is, but I remember it because it's so crazy (the MIME body's content is literally an RFC 2833 RTP DTMF event packet, minus the IP and UDP header). -hadriel _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
