> 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/coding-of-onesait-editran-sessions-once-keys-are-exchanged..md). # Coding of Onesait · Editran sessions once keys are exchanged. Once keys have been exchanged, in editran sessions we will usually encode: ``` | CRYPTOGRAPHY (Y/N).......: S | | CRYPTOGRAPHIC VERSION......: 4 00 | | DATA ENCRYPTION ALGORITHM.: CCCC AUTHENTICATION ALGORITHM ...: DDD | | LOCAL SUBSYSTEM...........: X REMOTE SUBSYSTEM..........: Y | ``` CCCC – It is the data encryption algorithm (with this, we indicate the operational key that will be used to encrypt data). The allowed values are spaces, TD3C, AES1, AES2 and AES3 (no encryption, DES or single, double and triple-key AES). DDD – It is the authentication algorithm (it is the exchanged key, which is used to sign and to encrypt the operational key). The allowed values are DES and RSA. X- It is the OWN (local) subsystem. Remember that for some sessions with that remote, you may have different local subsystems than for another. Z- It is the FOREIGN (remote) subsystem.. Remember that for some sessions with that remote, you may have different remote subsystems than for another When we change a key within the same subsystem, it is NOT NECESSARY to touch the previous configuration. Editran looks among the values we have given it for which is the ACTIVE key (there is only 1) that exists in that subsystem, and operates with it. Hence, if either endpoint performs a new exchange, it does not have to notify the other endpoint (remember that TELEGC is defined and its operation is automatic from either endpoint), so that, if the key changes, it becomes active, and both editran will pick up the new one. Based on the above, on neither endpoint will it be necessary to touch the local and remote subsystem fields again. --- # 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/coding-of-onesait-editran-sessions-once-keys-are-exchanged..md?ask=&goal= ``` `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.