Home /Modules/http-4.0/README.md

README.md

lib/http-4.0/README.md · 55 line(s) · markdown

SLeeLa HTTP 4.0 — application protocol models

HTTP 4.0 is the next SLeeLa application-protocol generation derived from the HTTP 3.0 model inventory. These .sleela files define library-level data models and policy decisions; they do not prove that native transport, cryptography, flow control, or wire behavior has been implemented.

Model inventory

Preserved HTTP 3.0 baseline

Preserves the 160-bit logical-port namespace (0 through 10^48−1), request correlation, keyed-MAC DIGEST model, nonce replay guard, INTACTX check, canonical 14-item / 172-byte BASKET metadata, L1–L4 capabilities, and DOWNLOAD fields: SESSION-ID, DATETIME, FILE-ID, FILE-NAME, INDEX, OFFSET, TOTAL-SIZE. Large-file mode begins above 52,428,800 bytes; this is not a file-size cap.

HTTP 4.0 model additions

  1. Session-scoped stream identity and independent send/receive sequence counters.
  2. Stream close/reset state and bounded concurrent-stream policy.
  3. Authorization as a distinct dispatch-gate requirement.
  4. Explicit digest-algorithm label for future negotiation.
  5. Header and queue limits in addition to HTTP 3.0 payload/dictionary bounds.
  6. Explicit authenticated-offer and legacy-fallback decisions.

Specification and implementation boundaries

The normative draft, adversarial test plan, and evidence-based capability matrix live in ../../http-4.0/: SPEC.md, CONFORMANCE.md, CAPABILITY-MATRIX.md, and STATUS.md. The C reference now has a bounded per-stream state model and stricter DOWNLOAD metadata parsing, but the session model is not yet wired into server dispatch and the changes have not been run through the full build in this interaction.

Security and implementation boundaries

The SLeeLa generation label is not the IETF HTTP/3 version. Do not claim QUIC, HTTP/3 framing, QPACK, transport encryption, algorithm agility, persistent replay protection, or enforcement of these limits until native implementation and tests demonstrate them. HTTP 3.0's reference documentation describes an HTTP/1.x carrier. Production deployment still requires authenticated TLS/QUIC or another protected transport. SipHash-2-4's 64-bit tag is not a replacement for modern transport security or peer identity authentication.

Before calling HTTP 4.0 production-ready, port native behavior, update the wire specification, test malformed input/replay/stream resume, compare C/C++ behavior, run sanitizers and fuzzing, and verify manifests and CI. Model counters alone are not a security boundary.