@techreport{thain-ipv8-03,
    number =    {draft-thain-ipv8-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-thain-ipv8/03/},
    author =    {James Thain and Aleksei Aleinikov},
    title =     {{Internet Protocol Version 8 (IPv8)}},
    pagetotal = 56,
    year =      2026,
    month =     oct,
    day =       15,
    abstract =  {This document specifies Internet Protocol Version 8 (IPv8), an extension of IPv4 {[}RFC791{]} that prepends a 32-bit Route Number (RN) to each IPv4 address to produce a 64-bit address space. IPv4 is a proper subset of IPv8: an IPv8 address whose RN is zero is bit- identical to an IPv4 address, and IPv4 packets are IPv8 packets whose RN is implicitly zero. IPv8 is incrementally deployable over existing IPv4 infrastructure. Forwarding silicon, BGP4 routing, and operator administrative boundaries continue to operate without modification. IPv8-aware behaviour is implemented in software at the edges of forwarding paths and signalled through extension mechanisms (BGP large communities, IS-IS TLVs, OSPF opaque LSAs) that unupgraded transit elements flood transparently and ignore. This document defines the IPv8 address format, the textual representation conventions including the canonical hyphenated locator form, the relationship to IPv4, the architectural principles governing the suite, and the security and operational considerations applicable to all companion specifications. Routing-protocol behaviour, encapsulation rules, trust mechanisms, and management interfaces are specified in companion documents listed in \S{}1.},
}