Skip to main content

Module response

Module response 

Source
Expand description

Response binding types — the client’s commitment to how the response must be produced.

In a request proof the map is the client’s commitment. It is null when the response is neither encrypted nor streamed. In a response proof it is the realized binding and MUST equal the request’s map where both are present.

Gate-2 amendments 3 + 4 make the two dimensions orthogonal and the map four-field: {1: root_type_id, 2: response_kind, 3: protection_mode, 4: kem_recipient-or-null}, with response_kind = {1: unary, 2: stream_setup} and protection_mode = {1: cleartext, 2: encrypted}. The KEM recipient is non-null iff protection_mode == encrypted, independent of response_kind. The cleartext MAP alternative is stream_setup-only: a cleartext unary response is neither encrypted nor streamed and is encoded as a null response_binding, never a map (canonical vector N-27).

Structs§

KemRecipient
ML-KEM-768 recipient material for an encrypted response.
ResponseBinding
Response binding map carried in the response_binding claim (−70004).

Enums§

ProtectionMode
Whether the response is encrypted (Gate-2 amendment 4, axis 2). Orthogonal to ResponseKind.
ResponseKind
How the response is delivered (Gate-2 amendment 4, axis 1).