As already explained, it is not possible for a PAKE protocol to disclose a single bit of password information. This means that no mechanism can be available to ensure, directly at both ends of the protocol, that the correct password is being used by the other party. For example, the password cannot answer an effectively verifiable equation, which happens to be the dummy protocol error in Figure e49.5. In contrast, a digital signature scheme works in the same way, the main difference being that long-term secrecy is strong cryptographically. This is the method behind STS. Key exchange protocols allow two or more parties to set up a common encryption key that allows them to encrypt or sign data they wish to exchange. Key exchange protocols typically use cryptography to achieve this goal. To achieve this goal, different cryptographic techniques can be used. A key agreement authentication protocol for IMS (IMSKAAP) has been proposed by [CHE 08] to address the above issue. This IMSKAAP offers secure key exchange and allows servers to support lawful interception by integrating the benefits of KTAP and KAAP protocols. Generally speaking, DH`s key tuning method has a greater use of resources (both mathematically and in bandwidth) than previous quotas and requires quotas, as in the case of the public key. However, it has the advantage of offering perfect forward secrecy (PFS) and flexibility by allowing implementation in several different finite groups.

The first publicly known public key memorandum of understanding[1] that meets the above criteria was the Diffie-Hellman key exchange, in which two parties together expose a random generator in such a way that a listener cannot determine in a feasible way what is the resulting value used to make a common key. A key memorandum of understanding is usually called after two parties have been authenticated. The agreement on a common key allows the parties to communicate securely via unreliable communication networks. Mikey can be included in the minutes of the session. Currently, the integration of MIKEY into SIP/SDP and RTSP into KMASDP is defined.13 MIKEY can use other transports, in which case it is necessary to define how MIKEY is transported by such a transport protocol.