IPv8 — Build the Branch & ZoneServer v1

Internet-Draft · Intended status: Standards TrackBuild the Branch, Ship the Solution.IPv8 is a managed network protocol suite that resolves IPv4 exhaustion, unifies network management, and stays 100% backward compatible — no flag day, no forced migration. Help fund the kernel build and the first reference implementation of the addressing schema.IPv8=ASN+IPv4// r.r.r.r + n.n.n.n$ ipv8 addr showr.r.r.r.n.n.n.n// 64-bit · IPv4 ⊂ IPv8§ 01 — Why IPv8IPv6 fixed addresses. IPv8 fixes the operating model.After 25 years of dual-stack effort, IPv6 still carries a minority of global traffic. IPv8 takes a different bet: ship a coherent management suite first, and make the address upgrade a side-effect of running it.§ 02 — Scope of workWhat the funds build.Two engineering tracks and one validation track, run by a dedicated project manager against the published Internet-Draft.BranchKernel build of the IPv8 stackLinux kernel branch implementing the IPv8 packet header (RFC §6)AF_INET8 / sockaddr_in8 socket API surfaceARP8 dual-probe neighbour capability discovery8to4 tunnelling for IPv8-over-IPv4 transitReferenceZoneServer v1 reference implementationDHCP8 single-response service bundleDNS8 resolver with A8 record supportOAuth8 local JWT validation cacheEven/odd .254 / .253 active-active gateway pairProofAddressing schema testEnd-to-end r.r.r.r.n.n.n.n routing across two test ASNs127.x.x.x internal zone isolation verified across ~24M zonesASN-encoded WHOIS8 route validation in the loopConformance report published under draft-thain-ipv8-02§ 03 — MilestonesA sequenced build, publicly tracked.M101/05Project manager onboardedSpec triage, contributor RFC process, weekly public build log.M202/05Kernel branch — header & socketsIPv8 header parsing, AF_INET8 surface, ARP8 dual-probe in-tree.M303/05ZoneServer v1 alphaDHCP8 + DNS8 + OAuth8 active-active pair on a reference appliance.

M404/05Two-ASN test fabricEnd-to-end r.r.r.r routing, WHOIS8 validation in the path.M505/05Conformance reportPublic results, packet captures, and -03 spec revision submitted.§ 04 — Where the money goesEvery dollar tied to a deliverable.Funds are routed through the GoFundMe campaign and disbursed against milestone acceptance. Quarterly statements are published alongside the build log.Contribute to the campaignProject Manager (12 months)35%Spec stewardship, RFC coordination, public reporting.Kernel engineering — IPv8 branch35%Header, sockets, ARP8, 8to4, upstream patches.ZoneServer v1 reference build20%DHCP8 / DNS8 / OAuth8 / XLATE8 services.Test fabric & infrastructure10%Two-ASN lab, WHOIS8 registry, CI, packet captures.§ Developers ProgramAre you a kernel hacker, C, or Rust dev?Join the team building IPv8 — the next generation of the Internet. Every commit is public. Every contributor is named. Be one of the engineers who wrote the successor to IPv4.2 developers signed up so far · seats open for Phase 1GoFundMe — Campaign liveFund the kernel.Validate the schema.Back the IPv8 build branch and ZoneServer v1. Contributions are public, progress is public, packet captures are public.§ 05 — FAQCommon questions.Is IPv8 a replacement for IPv6?+IPv8 is an alternative successor to IPv4 with a different design bet: integrated network management plus single-stack backward compatibility. IPv4 is a proper subset of IPv8 — r.r.r.r = 0.0.0.0 is an IPv4 address.Do I need to upgrade my devices?+No. IPv4-only devices on a shared segment with IPv8 devices continue to operate unchanged. ARP8 dual-probe ensures an IPv8 sender transmits IPv4 to an IPv4 neighbour. No IPv4 device ever receives a packet with version 8 in the IP header.What does the GoFundMe actually fund?+A dedicated project manager, a kernel build branch implementing the IPv8 stack, the first ZoneServer v1 reference implementation, and a two-ASN lab to validate the addressing schema end to end.Will the work be open?+Yes.

Code lands on a public branch, the spec evolves under draft-thain-ipv8-* on the IETF datatracker, and milestone reports are published with packet captures.Who is behind it?+J. Thain (One Limited), author of draft-thain-ipv8-02 and the companion specifications covering routing protocols, RINE, ZoneServer, WHOIS8, NetLog8, and Update8.