Hi, I might be missing something, but why not let the IP stack handle the fragmentation? You're talking TCP here, but I believe even with UDP, most IP stacks use the IP header for fragmentation and simply drop all the packets if the original message cannot be put together because of a missing fragment. For the TCP there is not a "new session", the packet is chopped / fragmented and loaded into the next packet. If a particular packet (fragment) is not acknowledged then the sender retransmits the particular fragment / packet.
---ron -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of binod k mohanty Sent: Thursday, November 24, 2005 7:43 PM To: [email protected] Subject: [Sip-implementors] Larger SIP Messages Hi All, If a SIP request gets larger in size i.e. more than or equal to 1300 bytes or within 200 bytes of the known path MTU then its required to open a new TCP connection for that request to send. The 200 bytes cushion is provided at client side in order that the size of response from the UAS is well taken care thus.So the UAS while sending the response can use the same trnsport from which it received the request to send the response.So UAS is never required to check the message size for switching transport.UAS's transport selection is dictated by the UAC. Please any body clear my doubt that if in some Invite Transactions the response grows by more than 200 bytes when for the first time UAS sends the SDP offer for example and how the situation is handled if the UAS received the request from UDP? Regards and Thanks Binod K Mohanty --------------------------------- To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
