On 10/31/2011 03:20 PM, Iñaki Baz Castillo wrote: > 2011/10/31 Worley, Dale R (Dale)<dwor...@avaya.com>: >>> From: Iñaki Baz Castillo [i...@aliax.net] >>> >>> Hi, is there any RFC defining a binary body for SIP (in contrast to >>> UTF-8/ASCII bodies)? >> >> RFC 3261 section 7.4.1: >> >> SIP messages MAY contain binary bodies or body parts. When no >> explicit charset parameter is provided by the sender, media subtypes >> of the "text" type are defined to have a default charset value of >> "UTF-8". > > Thakns for pointing it out, but... > > >> You should have found that one yourself. > > ...I see no answer to my real question: > > Is there any RFC defining a binary body for SIP (in contrast to > UTF-8/ASCII bodies)? > > I already know that RFC 3261 states that a body can contain binary > data. What I'm asking for is for a RFC defining a binary body for SIP.
Any MIME-type that is defined to have binary content could legitimately appear in a SIP message. I'm not personally aware of any RFCs that define SIP extensions that require the transport of binary message bodies, but it's certainly allowed. RFC 3261 places no restrictions on the MIME-types that can appear in the Content-Type header. -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies Jabber: kflem...@digium.com | SIP: kpflem...@digium.com | Skype: kpfleming 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at www.digium.com & www.asterisk.org _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
