hi Lennox,
> In general, I don't think that fragmenting SIP messages is a
> good idea --
> you really shouldn't be sending messages larger than the IP
> fragmentation
> minimum in general. If you need to send that much information, use
Are'nt we puting some restrictions on sip by saying this ?
I very much agree that we shuld'nt be sending messages larger than IP
fragmentation but in some case that just can't be helped.
> external URLs and HTTP, so the client can download it or not
> as they wish.
> (I'd really rather have a *choice* as to whether my mobile
> phone downloads
> your 200MB TIFF showing who's calling...)
so you wuld'nt download the TIFF on your mobile, but what if your sip phone
is on your computer ^physically^ connected to the internet with reasonable
bandwidth. You wuld'nt mind downloading the TIFF. Sip protocol has to cater
to the needs of everyone right.
> That said, if you must do this, there's already a MIME type
> defined for
> fragmented messages -- message/partial. (I believe it was
> designed for
> posting large binaries to Usenet, back when there was a
> maximum message
> size.) See RFC 2046.
I don't think i follow u clearly here... can u please explain in a bit
detail.
Regards,
Mayank
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
