RKE Services Overview (Group 15)

RKE: Alows a client computer and a content server to exchange AES 256 encryption keys by sending key parts through the raida. Expand-Only HKDF, 32-byte shares, dual keys (K_rke / K_sess), and CS IdP redeem.

Overview

Group 15 is the live RKE surface. Normative freeze: core/docs/rke-redesign-v2.md Appendix F.

  • 01 preload_master_keyThe content server (such as a Qmail Server) uploads a master key to the raida
  • 03 get_share_and_ticket — Client goes to RAIDA to get a key part to be used for encryption between client and content server, and a ticket to give to the content server so that content server can verify the client's identy.
  • 04 redeem_identity_ticket — Raida server verifies the ticket for the content server

Content-server wire: POST /rke/v2/session/open under K_rke, then POST /rke/v2/cmd under K_sess (stripe put/get, ECHO). Auth quorum ≥13/25 ticket redeems.

Scope boundary

Group 15 is the active RKE documentation set. Group 4 public-key-exchange pages remain dormant and intentionally stay out of the live navigation.

Universal preamble (48 bytes)

Modern RKE requests start their bodies with a 48-byte authenticated preamble. This structure identifies the coin being used for the operation and provides replay protection.

CH (Challenge - 16B) 0 Session ID (8B) 16 CT 24 DN 26 SN (4B) 27 DV 31 AN (Authenticity Number - 16B) 32