The IETF (Internet Engineering Task Force), which is responsible for the development of internet protocols and architecture, has put forward the first draft version of the IPv8 protocol specification for discussion. The document was proposed by the third-party company One Limited, created outside the IETF standardization process and has the status of 'Internet-Draft' (anyone can publish such a draft if formalities are followed). The IPv8 protocol is notable for its use of locally cacheable OAuth2 JWT tokens for authenticating elements in networks and verifying each established outgoing connection via a request to DNS8 (without querying DNS8, no record is created in the XLATE8 state table (similar to NAT) and the connection is blocked).
Addressing in IPv8 is similar to IPv4 — the IPv4 address space is a subset of IPv8, and an IPv8 address is formed as a routing prefix (autonomous system number) + IPv4 address (.n.n.n.n). With a zero routing prefix (0.n.n.n.n), a regular IPv4 address is formed, which can be used to interact with existing networks. IPv4. In essence, each autonomous system (ASN) is provided with its own separate IPv4 range. In the packet header, the version number 8 is indicated in the IP field, and 64 bits are allocated for the sender and receiver addresses — 32 bits for the ASN prefix + 32 bits for the host address in IPv4 style. In the global BGP8 routing table, only one entry is allowed for each ASN, with a minimum prefix length of /16.
It is claimed that the solution is 100% backward compatible, deployment can be seamless, and no modification of existing devices, applications, and networks will be required for the use of IPv8. This is achieved by using IPv4 in end networks and on client systems, utilizing the address translator XLATE8 for accessing the global IPv8 network, which translates requests between IPv4 and IPv8 in a manner similar to NAT. Additionally, elements are proposed for direct use of IPv8 on end systems and in network infrastructure, such as AF_INET8 network sockets, a new type of DNS record — A8, ARP8, ICMPv8, SNMPv8, routing protocols BGP8, IBGP8, OSPF8, and IS-IS8.
The basic IPv8 stack includes the DHCP8 protocol, a system domain names DNS8, time synchronization protocol NTP8, telemetry collection protocol NetLog8, WHOIS8 resolver for routing approval, ACL8 access control system, and IPv4/IPv8 address translator XLATE8. An entry in the connection state table XLATE8 is added after each connection request to DNS8 and the registration of an active route through WHOIS8 service. All functionality related to telemetry collection, authentication, name resolution, time synchronization, and address translation is implemented in the form of a unified Zone Server platform. A network-connected IPv8 device sends one Discover request to DHCP8 and receives all necessary parameters for Zone Server operation in response.
Source: opennet.ru
