[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pre-established key mode as additional requirement?





On Feb 19, 2007, at 9:07 PM, Dan Wing wrote:


I would like to see if there is consensus for a new requirement for RTPSEC.

Specialized devices may need to avoid public key operations or
Diffie-Hellman operations because of the computational cost or because of the additional call setup delay. For example, it can take a second or two to perform a Diffie-Hellman operation in certain devices. Examples of these specialized devices would include some handsets, intelligent SIMs, PSTN gateways, and SBCs. For the typical case because a phone call hasn't yet been established, ancillary processing cycles can be utilized to perform the PK or DH operation; for example, in a PSTN gateway the DSP (which isn't yet
involved with typical DSP operations) could be used to perform the
calculation, so as to avoid having the central host processor perform the calculation. Some devices, such as SBCs, handsets, and intelligent SIMs do
not have such ancillary processing capability.

Thus, it seems a useful optimization to securely set up a call the first time with a remote endpoint, and thereafter, when communicating with the
same remote endpoint, to leverage the DH or PK that was performed
previously.

Thoughts?

It seems eminently reasonable to support key management schemes for rtpsec that can leverage cached/stored keying material from prior sessions to derive new keys for the current session without requiring expensive cryptographic authentication operations.

Are you thinking of this as a MAY, a SHOULD, or a MUST?

Would you consider the TLS "session restart" machinery as qualifying to meet this requirement?


-d