-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Simon" == Simon P Ditner <[EMAIL PROTECTED]> writes:
Simon> I think that most protocols have provisions for encryption in
Simon> them. For example SIP[1], and it's primary dependency,
Simon> RTP[2], both contain specifications for encryption -- it's
Simon> just that no one has bothered to implement them in Asterisk
Simon> yet.
IRRELEVANT.
a) RTP encryption only keeps the voice data private. If you can divert
the control channel (which is trivial with MGCP, not so with SIP)
then you can just turn the encryption off.
b) methods of keying the RTP channel via SIP are totally immature.
(this is a solved problem for IPsec. It's called IKE, and
authenticating the end points is also solved)
c) VoIP providers can't afford to do software RTP decryption, while
there exists TODAY, a multitude of low-latency hardware solutions
for IPsec.
- --
] Michael Richardson Xelerance Corporation, Ottawa, ON | firewalls [
] mcr @ xelerance.com Now doing IPsec training, see |net architect[
] http://www.sandelman.ca/mcr/ www.xelerance.com/training/ |device driver[
] I'm a dad: http://www.sandelman.ca/lrmr/ [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBQvJMnoqHRg3pndX9AQEk2wQA5/z2GtNvKx/m7adlEMVIDbGQcgXyb8za
dBQsjM8kqMOMaqr+b4fSOkzwfDxzCRqP7GIbl8zU3F+yk7aC6BelbYfVpJfOSFYl
wyBWT3KyXxrDNmM1QfD7YIFRBh7l4FdHiY7cnd/eNbaJwGkjTRa2K1MDyXDNnY0p
fyEfUnH32GU=
=gc8Y
-----END PGP SIGNATURE-----
