Sounds appealing, until you realize that in an environment where TLS support is the exception and not the norm, you would degrade the performance of the network significantly by having lots of failed TLS connection attemps.
> -----Original Message----- > From: Dean Willis [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 05, 2007 23:52 > To: Juha Heinanen > Cc: Audet, Francois (SC100:3055); SIP IETF > Subject: Re: [Sip] Ready for WGLC on SIPS draft? Any last > thoughts on transport=tls? > > Juha Heinanen wrote: > > Francois Audet writes: > > > > > Later, in-dialog request will be sent on each hop reusing the > > existing > established connections (TLS or TCP) as per current RFC > > 3261 > procedures. > > > > what if established connection breaks for one reason or another and > > needs to be re-established for routing in-dialog request? > if there is > > no transport info in request route, how does the proxy know which > > transport to use? > > How about: > > It always tries TLS first, and if that doesn't work it either > 1) falls back to something else or 2) gives up. The choice > between 1 and 2 is made based on local policy. > > -- > Dean > > _______________________________________________ Sip mailing list https://www1.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
