Re: Question on draft-ietf-sip-outbound-20 draft: multipleflowcreation
Nils Ohlmeier <[email protected]>
| Newsgroups | gmane.ietf.sip,gmane.ietf.sip-implementors |
|---|---|
| Message-ID | <[email protected]> |
Am 31.08.09 19:11, schrieb Francois Audet: > I would tend to disagree that a policy of "Use UDP preferably > and switch to TCP if message is too big" is a good policy. Especially > considering that you'd have to keep the TCP connection alive anyways. > > I believe that always using the TCP connection in this case would > make more sense. > > But it's definitively legal. I totally agree with this. But from several years attending SIPit's I would highly recommend you to NOT mix UDP and TCP. From time to time I had already interoperability issues when my proxy did for example UDP to TCP conversion (and back). If you are talking/thinking about an UA implementation which mixes UDP and TCP on the first hop already I would anticipate lots of interoperability issues down the road. You should at least attend a SIPit to check how other proxy and UA implementations react on this. In the end any benefits which you might get from this design decision might be easily eaten up by the support efforts later. Best regards Nils Ohlmeier _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip