you missed the SCTP option as alternative to TCP
> -----Original Message----- > From: sip-implementors-boun...@lists.cs.columbia.edu > [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On > Behalf Of Abhishek Dhammawat > Sent: Donnerstag, 24. September 2009 12:26 > To: Kanta C; Sip Server > Subject: Re: [Sip-implementors] When to use TCP and UDP for > sip request > > Hi > > TCP should be use when reliability is required. > Also when dealing with large messages TCP should be used to > avoid fragmentation of the messages over UDP. > > For details please refer RFC 3261 section 18.1.1. > " If a request is within 200 bytes of the path MTU, or if it > is larger than 1300 bytes and the path MTU is unknown, the > request MUST be sent using an RFC 2914 [36] congestion > controlled transport protocol, such as TCP." > regards > Abhishek Dhammawat > Aricent > > > -----Original Message----- > From: sip-implementors-boun...@lists.cs.columbia.edu > [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On > Behalf Of Kanta C > Sent: Thursday, September 24, 2009 3:41 PM > To: Sip Server > Subject: [Sip-implementors] When to use TCP and UDP for sip request > > Hi All, > > Is there a rule for selecting the the transport layer > protocol like when to use TCP or when to use UDP.... > Regards, > Kinnu > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection > around http://mail.yahoo.com > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > "DISCLAIMER: This message is proprietary to Aricent and is > intended solely for the use of the individual to whom it is > addressed. It may contain privileged or confidential > information and should not be circulated or used for any > purpose other than for what it is intended. If you have > received this message in error,please notify the originator > immediately. If you are not the intended recipient, you are > notified that you are strictly prohibited from using, > copying, altering, or disclosing the contents of this > message. Aricent accepts no responsibility for loss or damage > arising from the use of the information transmitted by this > email including damage from virus." > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
