headers
Iñaki Baz Castillo | 1 Nov 2011 05:03
Gravatar

Re: Binary bodies in SIP?

2011/10/31 Kevin P. Fleming <kpfleming <at> digium.com>:
> 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.

Thanks Kevin. But anyhow it seems that there is no SIP spec/RFC
defining a binary body, am I wrong?

--

-- 
Iñaki Baz Castillo
<ibc <at> aliax.net>

_______________________________________________
Sip-implementors mailing list
Sip-implementors <at> lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Permalink | Reply | 5 comments |
headers
Rajesh Jain | 1 Nov 2011 05:19
Picon

Re: Binary bodies in SIP?

rfc 3204 seems to define binary encoding for ISUP and QSIG signaling bodies.

Thanks
Rajesh Jain

On Tue, Nov 1, 2011 at 9:33 AM, Iñaki Baz Castillo <ibc <at> aliax.net> wrote:

> 2011/10/31 Kevin P. Fleming <kpfleming <at> digium.com>:
> > 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.
>
> Thanks Kevin. But anyhow it seems that there is no SIP spec/RFC
> defining a binary body, am I wrong?
>
> --
> Iñaki Baz Castillo
> <ibc <at> aliax.net>
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors <at> lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
Permalink | Reply | 1 comment |
headers
Olle E. Johansson | 1 Nov 2011 07:36
Gravatar

Re: Binary bodies in SIP?

The closest thing I can think of is S/MIME signatures and certificates that of course are encoded in text,
but is not text in the data.
There are actually references to sending images in RFC 3261:

"The disposition type icon indicates that the body part contains an image suitable as an iconic
representation of the caller or callee that could be rendered informationally by a user agent when a
message has been received, or persistently while a dialog takes place." 

Page 122, RFC 3261.

Now, images can of course be encoded or sent binary. The RFC doesn't give us recommendations, so I guess you
will have to track back to the original set of documents for MIME.

(Surprised that Dave did not find that :-) )

/O
Permalink | Reply | 27 comments |
headers
Iñaki Baz Castillo | 1 Nov 2011 13:29
Gravatar

Re: Binary bodies in SIP?

2011/11/1 Rajesh Jain <rajesjai <at> gmail.com>:
> rfc 3204 seems to define binary encoding for ISUP and QSIG signaling bodies.

Thanks a lot.

--

-- 
Iñaki Baz Castillo
<ibc <at> aliax.net>

_______________________________________________
Sip-implementors mailing list
Sip-implementors <at> lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Permalink | Reply | 0 comments |
headers
Iñaki Baz Castillo | 1 Nov 2011 13:31
Gravatar

Re: Binary bodies in SIP?

2011/11/1 Olle E. Johansson <oej <at> edvina.net>:
> The closest thing I can think of is S/MIME signatures and certificates that of course are encoded in text,
but is not text in the data.
> There are actually references to sending images in RFC 3261:
>
> "The disposition type icon indicates that the body part contains an image suitable as an iconic
representation of the caller or callee that could be rendered informationally by a user agent when a
message has been received, or persistently while a dialog takes place."
>
> Page 122, RFC 3261.
>
> Now, images can of course be encoded or sent binary. The RFC doesn't give us recommendations, so I guess you
will have to track back to the original set of documents for MIME.

Good to know, thanks a lot.

--

-- 
Iñaki Baz Castillo
<ibc <at> aliax.net>

_______________________________________________
Sip-implementors mailing list
Sip-implementors <at> lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Permalink | Reply | 0 comments |
headers
Worley, Dale R (Dale | 1 Nov 2011 16:00
Favicon

Re: Binary bodies in SIP?

> From: Olle E. Johansson [oej <at> edvina.net]
> 
> Now, images can of course be encoded or sent binary. The RFC doesn't
> give us recommendations, so I guess you will have to track back to the
> original set of documents for MIME.

The text of 3261 doesn't mention it, but the examples show
"Content-Transfer-Encoding: base64" for some body parts.

> (Surprised that Dave did not find that :-) )

It's "Dale", please!

Dale
Permalink | Reply | 25 comments |
headers
Hadriel Kaplan | 1 Nov 2011 16:23
Favicon

Re: Binary bodies in SIP?


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
Permalink | Reply | 2 comments |
headers
Iñaki Baz Castillo | 1 Nov 2011 18:29
Gravatar

Re: Binary bodies in SIP?

2011/11/1 Hadriel Kaplan <HKaplan <at> acmepacket.com>:
> 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)

Well, if that does not affect to users endpoints then I don't care :)

> RFC 3853 defines S/MIME AES as binary in SIP, though I don't know of anyone implementing that.

What is S/MIME?? :)

> Microsoft sends binary-enoded MIME payloads in SIP MESSAGE requests in certain Instant-Messaging use-cases.

I was speaking about real SIP :)

> 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).

That's amazing.

Thanks a lot.

--

-- 
Iñaki Baz Castillo
(Continue reading)

Permalink | Reply | 0 comments |
headers
fengbin dong via LinkedIn | 2 Nov 2011 05:17
Picon
Favicon

Invitation to connect on LinkedIn

LinkedIn
------------

    fengbin dong requested to add you as a connection on LinkedIn:

------------------------------------------

Priyank,

I'd like to add you to my professional network on LinkedIn.

Accept invitation from fengbin dong
http://www.linkedin.com/e/-ftd1dd-guhtf5st-g/cFM0GAd-yBCwaJGWsQs1GGTyK-p78Ke3DbMDt3xi3HiTZiXE_HRum-ba/blk/I278233619_20/1BpC5vrmRLoRZcjkkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYMcBYVcjoPcP8UdP99bSREd5ljjkNfbPcVcPkPe3cRc38LrCBxbOYWrSlI/EML_comm_afe/?hs=false&tok=3oE2GU62o1LQY1

View invitation from fengbin dong
http://www.linkedin.com/e/-ftd1dd-guhtf5st-g/cFM0GAd-yBCwaJGWsQs1GGTyK-p78Ke3DbMDt3xi3HiTZiXE_HRum-ba/blk/I278233619_20/30OnPANdzcPczwTcAALqnpPbOYWrSlI/svi/?hs=false&tok=3Dcre2GHA1LQY1

------------------------------------------

Why might connecting with fengbin dong be a good idea?

People fengbin dong knows can discover your profile:

Connecting to fengbin dong will attract the attention of LinkedIn users. See who's been viewing your profile:

http://www.linkedin.com/e/-ftd1dd-guhtf5st-g/wvp/inv18_wvmp/?hs=false&tok=31rRWhFio1LQY1

--

-- 
(c) 2011, LinkedIn Corporation
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Kyzivat | 2 Nov 2011 19:01
Picon
Favicon

Re: Binary bodies in SIP?

I think I recall some work from long ago that banned use of 
Content-Transfer-Encoding. (But I'm not sure I remember it right.) It 
might have been Cullen who did it.

Does that ring any bells?

	Thanks,
	Paul

On 11/1/11 11:00 AM, Worley, Dale R (Dale) wrote:
>> From: Olle E. Johansson [oej <at> edvina.net]
>>
>> Now, images can of course be encoded or sent binary. The RFC doesn't
>> give us recommendations, so I guess you will have to track back to the
>> original set of documents for MIME.
>
> The text of 3261 doesn't mention it, but the examples show
> "Content-Transfer-Encoding: base64" for some body parts.
>
>> (Surprised that Dave did not find that :-) )
>
> It's "Dale", please!
>
> Dale
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors <at> lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
(Continue reading)

Permalink | Reply | 24 comments |

Gmane