If it uses Outbound, then connection gets re-established by client automatically (based on keep-alives).
Otherwise, correct, you don't know. I guess the real question is "do we need to solve this case"? I guess to me it means that it would be useful only for mutual TLS cases. Is this big enough of a problem to justify the expense of having to deal with the parameter? That's a question for the group. I don't have a strong opinion on it (just a preference for using Outbound for this). > -----Original Message----- > From: Juha Heinanen [mailto:[EMAIL PROTECTED] > Sent: Monday, June 04, 2007 12:42 > To: Audet, Francois (SC100:3055) > Cc: Robert Sparks; SIP IETF; Dean Willis > Subject: RE: [Sip] Ready for WGLC on SIPS draft? Any last > thoughts on transport=tls? > > 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? > > -- juha > _______________________________________________ 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
