> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/key-manager/introduction/types-of-key-exchanges.md).

# Types of key exchanges

When we exchange keys through the key exchange management application, we can perform 1 or 2 types of exchanges:

* Initially, 2 entities exchange an RSA key (public part), in both directions and in plain text. This is always done, regardless of whether what they later exchange are DES keys.
* Subsequently, these 2 endpoints:

> From the initial exchange onward, when new RSA public keys are exchanged, all transmissions will be signed with some private key for which we know that the corresponding associated public key has been sent to the remote side. In other words, in the second exchange, at least the initial one can be used to sign; in the third, the initial one or the second one, and so on.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/key-manager/introduction/types-of-key-exchanges.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.