IPv8 Draft Status
draft-thain-ipv8-02 is the current version used by this wiki.
| Field | Value |
|---|---|
| Document | draft-thain-ipv8-02 |
| Title | Internet Protocol Version 8 (IPv8) |
| Author | James Thain |
| Organization | One Limited |
| Published | 17 April 2026 |
| Expires | 19 October 2026 |
| Datatracker | draft-thain-ipv8 |
| Archived HTML | draft-thain-ipv8-02.html |
| Archived TXT | draft-thain-ipv8-02.txt |
Internet-Draft Notice
Section titled “Internet-Draft Notice”The IETF Datatracker page states that this document is an Internet-Draft. Anyone may submit an Internet-Draft, and this one is not endorsed by the IETF and has no formal standing in the IETF standards process.
Internet-Drafts are working documents. They can be updated, replaced, or expire. This wiki therefore treats IPv8 as a proposal under discussion.
Distance To RFC
Section titled “Distance To RFC”As of 18 April 2026, draft-thain-ipv8-02 appears to be at the public Internet-Draft stage. The Datatracker listing identifies it as an active individual Internet-Draft, with IESG state I-D Exists. That means it is visible and discussable, but not approved as an RFC.
| RFC path checkpoint | Current IPv8 status | Meaning |
|---|---|---|
| Internet-Draft posted | Done | The draft is publicly archived and can be reviewed. |
| Active latest version | Done | draft-thain-ipv8-02 is the latest version used by this wiki. |
| Working Group adoption | Not shown | The draft is not listed as a draft-ietf-* Working Group document. |
| Working Group rough consensus | Not shown | No WG consensus record is visible from the draft status page. |
| Working Group Last Call or document shepherding | Not shown | No publication handoff is visible. |
| IETF Last Call | Not shown | The wider IETF has not been asked for final review. |
| IESG approval | Not done | The visible IESG state is I-D Exists, not approved publication. |
| RFC Editor queue | Not done | No RFC Editor publication queue state is visible. |
| IANA registry actions | Requested only in draft text | Any requested protocol parameter assignments would require approval through the IETF/RFC process. |
| RFC number assigned | Not done | The document is not an RFC. |
Practical reading: IPv8 is currently a proposal. To become a Standards Track RFC, it would need review, consensus, IESG approval, and RFC Editor publication. For details, see IETF RFC Process.
Current Wiki Policy
Section titled “Current Wiki Policy”- Explanatory pages follow
draft-thain-ipv8-02. - Historical draft text is preserved for versions
00,01, and02. - Pages should describe what the draft says and avoid presenting the proposal as a completed standard.
- When behavior changes between versions, the latest version is described first and older behavior is noted in the archive.