[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sip] Ready for WGLC on SIPS draft? Any last thoughts on transport=tls?



Juha -

The classic answer for this is that the gateway should have a DNS name with its NAPTR and SRV
records configured to specify exactly TLS. Do you agree that if you have DNS available, that's good
enough?


I think you're pointing to specifically the case where you don't have DNS records pointing to UAS,
is that correct?


RjS

On Jun 4, 2007, at 1:05 PM, Juha Heinanen wrote:

Francois Audet writes:

Which hop???

UAC -----> Proxy 1 ------> Proxy 2 ------> UAS

for example, lets say that UAS is pstn gw that needs to be contacted over tls. proxy 1 makes a decision to use this particular pstn gw, rewrites r-uri so that it among other things contains transport=tls parameter, and then forwards the request to proxy 2 that is a "dumb" proxy whose purpose is to front end the gw.

i don't know another way to do this because sip uri scheme cannot be
upgraded to sips and sips scheme cannot be downgraded to sip.

-- juha



_______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors at cs.columbia.edu for questions on current sip Use sipping at ietf.org for new developments on the application of sip