Documentation · HTTPS transport
HTTPS transport: a carrier without authority
The Transport Profile fixes HTTP/2 over TLS 1.3 operations, resource accounting, retry outcomes, and residual metadata while carrying opaque protected packets.
Fixed carrier
Every operation uses HTTP/2 over TLS 1.3 with canonical content length and a lowercase operation identifier. The profile forbids alternate HTTP versions, early data, content coding, transfer encoding, trailers, query parameters, fragments, and streaming request bodies.
Five operations
| Operation | Purpose | Accepted HTTP result |
|---|---|---|
| AFFILIATE | Establish bounded Endpoint affiliation state | 201 |
| RESERVE | Reserve one bounded delivery handle | 201 |
| SUBMIT | Submit one raw protected packet | 202 |
| CLAIM | Claim bounded opaque packets | 200 |
| SETTLE | Settle transport ownership | 200 |
Body and outcome authority
HTTP, TLS, a certificate issuer, and the Station do not define protocol meaning. A successful Station response cannot substitute for authenticated Endpoint confirmation or authorize application effects.
Exact resource accounting
Storage, claim, settlement, body sizes, retry classes, and residual metadata are explicitly bounded. Rejection or ambiguous transport outcomes cannot advance protected Endpoint state by inference.