IPv8 intended to fix the issues with IPv6
IANA completed allocation of the IPv4 unicast address space in February 2011. Regional Internet Registries exhausted their allocations between 2011 and 2020. CGNAT extended IPv4 life at the cost of latency, peer-to-peer protocol breakage, and troubleshooting complexity.
IPv6 [RFC8200] was developed to address exhaustion. After 25 years of standardisation and deployment effort IPv6 carries a minority of global internet traffic. The dual-stack transition model -- requiring every device, application, and network to simultaneously support both protocols -- proved commercially unacceptable. The absence of a forcing function meant organisations could continue with CGNAT indefinitely.
IPv8 resolves address exhaustion without dual-stack operation. IPv4 is a proper subset of IPv8. The transition requires no flag day and creates no operational discontinuity.
https://www.ietf.org/archive/id/draft-thain-ipv8-00.html
Waitman Gobble
@hello@rumbly.net
Hello Welcome To The New You I, me, mine, myself, we, us, ours, ourselves, you, your, yours, yourself, yourselves, he, him, his, himself, she, her, hers, herself, it, it's, itself, they, them, theirs, themselves
rumbly.net
Waitman Gobble
@hello@rumbly.net
Hello Welcome To The New You I, me, mine, myself, we, us, ours, ourselves, you, your, yours, yourself, yourselves, he, him, his, himself, she, her, hers, herself, it, it's, itself, they, them, theirs, themselves
rumbly.net
@hello@rumbly.net
·
5d ago
0
8
0
Conversation (8)
Showing 0 of 8 cached locally.
Syncing comments from the remote thread. 8 more replies are still loading.
Loading comments...