[asterisk-dev] RFC4733 SRTP option

[Nick Lewis]

>Well, you can actually exchange keys for SRTP without 
>revealing the keys in the open in the SIP messaging 
>channel. So it's not that crazy, Nick.

I was thinking more from an ietf marketing point of
view than a technical one. RFC2833 has been obsoleted 
so new implementations must use RFC4733. But RFC4733 
mandates SRTP. Therefore in an implementation that 
does not need security (e.g. soho pbx with pstn 
trunks) no rtp event DTMF method can be used.

In my view there needs to be a base level ietf 
product that specifies functionality without any
security 

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre.
_____________________________________________________________________
Disclaimer of Liability
ATL Telecom Ltd shall not be held liable for any improper or incorrect use of the  information described and/or contained herein and assumes no responsibility for anyones use  of the information. In no event shall ATL Telecom Ltd be liable for any direct, indirect,  incidental, special, exemplary, or consequential damages (including, but not limited to,  procurement or substitute goods or services; loss of use, data, or profits; or business  interruption) however caused and on any theory of liability, whether in contract, strict  liability, or tort (including negligence or otherwise) arising in any way out of the use of  this system, even if advised of the possibility of such damage.

Registered Office: ATL Telecom Ltd, Fountain Lane, St. Mellons Cardiff, CF3 0FB
Registered in Wales Number 4335781

All goods and services supplied by ATL Telecom Ltd are supplied subject to ATL Telecom Ltd standard terms and conditions, available upon request.