-----Original Message-----
From: Bob Penfield [mailto:BPenfield at acmepacket.com]
Sent: Monday, June 04, 2007 11:10
To: Audet, Francois (SC100:3055); Robert Sparks; Dean Willis
Cc: SIP IETF
Subject: Re: [Sip] Ready for WGLC on SIPS draft? Any last
thoughts ontransport=tls?
I have seen cases where transport=tls appears in the
Record-Route where one hop between proxies uses TLS. For example:
UAC--<TCP>-->Proxy1---<TLS>--->Proxy2--<TCP>--->Proxy3---<TCP>--
>UAS
This is done using a SIP URI (not SIPS).
I have not been able to keep up with this discussion, but the
question I have is: without transport=tls, how would you
express the desire/need to do TLS for a SIP URI in a
Record-Route or Route header? I am talking about a case where
the proxy (Proxy2 above) supports TCP and TLS, but the
selection of transport is made for the initial INVITE, and
that same transport needs to be used for in-dialog requests?