It is RFC 3261 that deprecated transport=tls, not my draft. The reason why my draft talks about it is that, as you mention, it is clearly something that was missed in the industry, causing interoperability problems.
> -----Original Message----- > From: Juha Heinanen [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 26, 2007 11:35 > To: Audet, Francois (SC100:3055) > Cc: [email protected]; Alan Johnston; Keith Drage; Peterson, Jon; > Dean Willis > Subject: RE: [Sip] draft-ietf-sip-sips-03.txt: Closing of > Opened issues > > Francois Audet writes: > > > You CAN use Double record-route. It doesn't break anything. > > > > This draft does not make any use of it. > > ok, sorry, i misunderstood your reply. > > by the way, why does your sips draft say that transport=tls > is deprecated when uri scheme is NOT sips? please clean your > draft of EVERYTHING that is not strictly related to use of > sips uri scheme. > > in real life transport=tls is NOT deprecated. also, in my > opinion, if tls can be used in via header, it should also be > usable as transport parameter value. > > tell me, why is tls (instead of tcp) needed in via when uri > scheme is sips? cannot tls/tcp be concluded if transport is > tcp and uri scheme is sips. > > -- 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
