Home /Modules/http-4.0/STATUS.md

STATUS.md

http-4.0/STATUS.md · 63 line(s) · markdown

HTTP 4.0 Source — Current Engineering Status

Status: Experimental foundation; not production-ready. Protocol name: SLeeLa HTTP 4.0, not an IETF HTTP/4 standard. Carrier currently implemented: HTTP/1.x over TCP in the reference server. No HTTP/3/QUIC adapter is present.

Present in source

Latest CI evidence

Not yet established

Release gate

Keep HTTP 4.0 experimental until all of the following are demonstrated:

  1. Review and resolve every repository SHA-256 manifest mismatch without bypassing the integrity check.
  2. Pass native repository CI and HTTP 4.0 conformance CI on Linux, macOS, and Windows.
  3. Integrate per-stream state and receive/send flow-control into the actual persistent server dispatch path, with overflow, reset, duplicate, ordering, and allocation-failure tests.
  4. Define and validate exact payload schemas and state rules for every frame type.
  5. Implement an authenticated carrier adapter backed by a maintained HTTP/3/QUIC implementation, or explicitly limit deployment to a separately authenticated carrier. Do not claim native QUIC support until it exists and passes interoperability tests.
  6. Implement durable, authenticated resume checkpoints, atomic persistence, crash-safe publication, and end-to-end final digest verification using vetted cryptographic primitives.
  7. Run sustained coverage-guided fuzzing and attach reproducible logs.
  8. Complete an independent security review and publish its scope and findings.

Documents