RFC submission: IETF Internet-Draft for mortal workspace claims protocol

[instagrim-dev]

Goal

Submit an IETF Internet-Draft formalizing the enforcement claims protocol (mortal distributed leases with actor identity and operator override) for multi-agent coordination.

Current State

• Behavioral specs complete: advisory, enforcement, induction (normative, hardened)
• HTTP transport binding defined (transport/HTTP.md)
• Reference implementation (Go, zero deps) with conformance runner (42 pass, 0 fail)
• Security considerations, IANA considerations, and error model documented
• One production implementation (BMO)

Remaining Work

Required

• Second independent implementation — Python or Rust client/server passing the conformance runner against advisory/conformance/expectations.yaml + enforcement/conformance/expectations.yaml
• Internet-Draft formatting — Rewrite enforcement/SPEC.md + transport/HTTP.md into I-D XML or mmark format using xml2rfc toolchain
• Interoperability report — Document that two independent implementations can coordinate via the HTTP transport (cross-impl claim acquire/conflict/override)
• Formal security analysis — Expand §9 of transport binding into standalone Security Considerations per RFC Editor requirements (threat model, mitigations, residual risks)
• IANA registration request — Decide whether to register /.well-known/agent-coordination-substrate or a media type

Recommended

• Identify target IETF working group or propose a BOF (candidates: HTTPAPI, new multi-agent coordination WG)
• Engage 2–3 external reviewers from the agent infrastructure community
• Write an Abstract and Introduction section suitable for IETF audience (not agent-native; explain the problem to protocol engineers)
• Add formal ABNF for zone path syntax (currently prose-defined)
• Define versioning/negotiation mechanism (how clients discover spec version)

Nice to Have

• OpenAPI 3.1 definition generated from transport/HTTP.md
• Compliance test HTTP server (standalone binary that validates incoming requests against the transport spec)
• Reference SSE event stream implementation with Last-Event-ID replay

Context

• The enforcement claims layer is the strongest RFC candidate because it defines a novel protocol (mortal distributed leases with mandatory operator override) with no existing RFC coverage
• Prior art: RFC 2131 (DHCP leases), Chubby/ZooKeeper (distributed locks) — neither covers agent-specific coordination with mortality + override guarantees
• The advisory and induction layers could follow as companion I-Ds once the enforcement claim protocol is accepted

Success Criteria

An Internet-Draft published at https://datatracker.ietf.org/ with at least two interoperable implementations cited in the document.