Re: SIP level bundeling
Brett Tate <[email protected]> Mon, 30 May 2011 05:35:57 -0700
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <7FF1E5E16911C54BB2D57D4C4A2ED35A08CA6CB46D@EXMBXCLUS01.citservers.local> |
> > 2) In case of SIP fregmanmtion, I guess as TCP does not know the > logical intelligence of SIP message, therefore sip message can be > fregmented at any location even in between sip header, before call is > ..... am i correct ... > > Of course. TCP is not message boundary so the receiver must buffer the > received data until it becomes a valid SIP message (it could drop the > connection if it takes so long as it could be an attack). Additionally concerning stream-oriented transports, the Content-Length header value is used to locate the end of the SIP message. See RFC 3261 section 7.5, 18.3, and 20.14. _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is essentially closed and only used for finishing old business. Use [email protected] for questions on how to develop a SIP implementation. Use [email protected] for new developments on the application of sip. Use [email protected] for issues related to maintenance of the core SIP specifications.