Actually, it offers no value. It just makes it more likely that it will fail.
We've been through this already. You know that a UAC supports TLS by the fact that it used TLS to register. It's the "implicit indication". The draft however tells you how to be backward compatible with UAs that use transport=tls. > -----Original Message----- > From: Juha Heinanen [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 26, 2007 11:44 > 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: > > > It is RFC 3261 that deprecated transport=tls, not my draft. > > yes, but as i told, transport=tls is heavily used for good > reasons and if might make sense to deprecate the deprecation. > if you want to bring the issue up in your draft, we can also > make that change (since the draft makes changed anyway). > > > 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. > > no, it was not missed by the industry. industry is not that stupid. > transport=tls is used, because there is VALUE in using it. > > -- 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
