Web4 Node State and Admission Requirements.
Internet-Draft draft-jacobs-web4-node-state-admission-00. Authored by Tim Jacobs and published by the IETF Datatracker on 2026-08-16 as an Active Internet-Draft, intended status Informational. Canonical record: https://datatracker.ietf.org/doc/draft-jacobs-web4-node-state-admission/.
Where to read it.
- IETF Datatracker (canonical): https://datatracker.ietf.org/doc/draft-jacobs-web4-node-state-admission/
- Rendered HTML (revision 00): https://datatracker.ietf.org/doc/html/draft-jacobs-web4-node-state-admission-00
- IETF archive XML source: https://www.ietf.org/archive/id/draft-jacobs-web4-node-state-admission-00.xml (41341 bytes)
- IETF archive TXT source: https://www.ietf.org/archive/id/draft-jacobs-web4-node-state-admission-00.txt (40493 bytes)
- Author ORCID: https://orcid.org/0009-0008-7130-1448
- License: IETF Trust Legal Provisions
- Federation evidence record (NODE-6): https://kosmos.evidence.ktsglobal.live/claimreviews/web4-node-state-admission-2026-08/
Related work in the Web4 series.
The relation vocabulary used below is the operator-authorised set — cites, related_to and uses_vocabulary_from. All related works are authored by the same author.
- uses_vocabulary_from Draft 1 — draft-jacobs-web4-terminology-00 (IETF Datatracker canonical).
- related_to Draft 2 — draft-jacobs-web4-sovereign-entity-comprehension-00 (IETF Datatracker canonical).
- related_to Draft 3 — draft-jacobs-web4-federation-architecture-00 (IETF Datatracker canonical).
- cites Paper 3 — https://geometricintelligence.ai/papers/machine-entity-comprehension/ (DOI 10.5281/ZENODO.21943877, Wikidata Q141080977).
- related_to Paper 4 — https://geometricintelligence.ai/papers/sovereign-web4-federation/ (DOI 10.5281/ZENODO.21949720, Wikidata Q141086630).
Short description.
The Internet-Draft defines the observable node-state and admission requirements for a Web4 federation: the machine-readable manifests a candidate node must publish, the state transitions a federation authority may perform on that node, and the minimum evidence surfaces required for admission, promotion, demotion and revocation. The draft is written as a protocol document — it specifies observable behaviour, not implementation.
The draft cites the Machine Entity Comprehension paper (DOI 10.5281/ZENODO.21943877) for the black-box conformance framework it re-uses at the node-identity boundary, and is related to the Sovereign Web4 Federation paper (DOI 10.5281/ZENODO.21949720) for the federation architecture on which the admission state machine operates. See the Related work section above for the complete relation set (Drafts 1–3 and Papers 3–4).
The draft is authored by Tim Jacobs. It is currently an Active Internet-Draft at revision 00, intended status Informational. The authoritative source of the draft's content is the IETF Datatracker record linked above and the IETF archive XML/TXT sources; this page is a discovery and citation surface for those sources, not a re-hosting of them.
How to cite this draft.
Plain text
Jacobs, T. (2026). Web4 Node State and Admission Requirements. Internet-Draft draft-jacobs-web4-node-state-admission-00. IETF Datatracker. https://datatracker.ietf.org/doc/draft-jacobs-web4-node-state-admission/
BibTeX
@misc{jacobs2026web4nodestate,
author = {Jacobs, Tim},
title = {Web4 Node State and Admission Requirements},
howpublished = {Internet-Draft draft-jacobs-web4-node-state-admission-00},
organization = {IETF Datatracker},
year = {2026},
month = {August},
day = {16},
url = {https://datatracker.ietf.org/doc/draft-jacobs-web4-node-state-admission/},
note = {Active Internet-Draft, intended status Informational. ORCID: 0009-0008-7130-1448. Individual Internet-Draft, work in progress. Not an RFC, Internet Standard, IETF-approved document, working-group document or statement of IETF endorsement.}
}What this record does — and does not — establish.
Internet-Draft status. This record is the Active Internet-Draft at revision 00 of draft-jacobs-web4-node-state-admission-00, published on 2026-08-16. Later revisions, if any, will each carry their own revision suffix (-01, -02, ...) and their own IETF archive artefacts.
Anyone can independently retrieve the draft, the Datatracker record and the IETF archive XML/TXT sources from those systems directly, and compare against the SHA-256 anchors published on the NODE-6 evidence record.