So, I think they are serious.
-
So, I think they are serious.
Internet Protocol Version 8 (IPv8)
Internet Protocol Version 8 (IPv8) is a managed network protocol suite that transforms how networks of every scale -- from home networks to the global internet -- are operated, secured, and monitored. Every manageable element in an IPv8 network is authorised via OAuth2 JWT tokens served from a local cache. Every service a device requires is delivered in a single DHCP8 lease response. Every packet transiting to the internet is validated at egress against a DNS8 lookup and a WHOIS8 registered active route. Network telemetry, authentication, name resolution, time synchronisation, access control, and translation are unified into a single coherent Zone Server platform. IPv4 is a proper subset of IPv8. An IPv8 address with the routing prefix field set to zero is an IPv4 address. No existing device, application, or network requires modification. The suite is 100% backward compatible. There is no flag day and no forced migration at any layer. IPv8 also resolves IPv4 address exhaustion. Each Autonomous System Number (ASN) holder receives 4,294,967,296 host addresses. The global routing table is structurally bounded at one entry per ASN. This document is one of the companion specifications: draft-thain-ipv8-00 Core protocol (this document) draft-thain-routing-protocols-00 BGP8, IBGP8, OSPF8, IS-IS8, CF draft-thain-rine-00 Regional Inter-Network Exchange draft-thain-zoneserver-00 Zone Server Architecture draft-thain-whois8-00 WHOIS8 Protocol draft-thain-netlog8-00 NetLog8 Protocol draft-thain-support8-00 ARP8, ICMPv8, Route8 draft-thain-ipv8-mib-00 IPv8 MIB and SNMPv8 draft-thain-wifi8-00 WiFi8 Protocol draft-thain-update8-00 Update8 and NIC Certification
(www.ietf.org)
I'll make the popcorn.
-
So, I think they are serious.
Internet Protocol Version 8 (IPv8)
Internet Protocol Version 8 (IPv8) is a managed network protocol suite that transforms how networks of every scale -- from home networks to the global internet -- are operated, secured, and monitored. Every manageable element in an IPv8 network is authorised via OAuth2 JWT tokens served from a local cache. Every service a device requires is delivered in a single DHCP8 lease response. Every packet transiting to the internet is validated at egress against a DNS8 lookup and a WHOIS8 registered active route. Network telemetry, authentication, name resolution, time synchronisation, access control, and translation are unified into a single coherent Zone Server platform. IPv4 is a proper subset of IPv8. An IPv8 address with the routing prefix field set to zero is an IPv4 address. No existing device, application, or network requires modification. The suite is 100% backward compatible. There is no flag day and no forced migration at any layer. IPv8 also resolves IPv4 address exhaustion. Each Autonomous System Number (ASN) holder receives 4,294,967,296 host addresses. The global routing table is structurally bounded at one entry per ASN. This document is one of the companion specifications: draft-thain-ipv8-00 Core protocol (this document) draft-thain-routing-protocols-00 BGP8, IBGP8, OSPF8, IS-IS8, CF draft-thain-rine-00 Regional Inter-Network Exchange draft-thain-zoneserver-00 Zone Server Architecture draft-thain-whois8-00 WHOIS8 Protocol draft-thain-netlog8-00 NetLog8 Protocol draft-thain-support8-00 ARP8, ICMPv8, Route8 draft-thain-ipv8-mib-00 IPv8 MIB and SNMPv8 draft-thain-wifi8-00 WiFi8 Protocol draft-thain-update8-00 Update8 and NIC Certification
(www.ietf.org)
I'll make the popcorn.
@nuintari@mastodon.bsd.cafe why the hate to odd numbers in IP versioning?
-
So, I think they are serious.
Internet Protocol Version 8 (IPv8)
Internet Protocol Version 8 (IPv8) is a managed network protocol suite that transforms how networks of every scale -- from home networks to the global internet -- are operated, secured, and monitored. Every manageable element in an IPv8 network is authorised via OAuth2 JWT tokens served from a local cache. Every service a device requires is delivered in a single DHCP8 lease response. Every packet transiting to the internet is validated at egress against a DNS8 lookup and a WHOIS8 registered active route. Network telemetry, authentication, name resolution, time synchronisation, access control, and translation are unified into a single coherent Zone Server platform. IPv4 is a proper subset of IPv8. An IPv8 address with the routing prefix field set to zero is an IPv4 address. No existing device, application, or network requires modification. The suite is 100% backward compatible. There is no flag day and no forced migration at any layer. IPv8 also resolves IPv4 address exhaustion. Each Autonomous System Number (ASN) holder receives 4,294,967,296 host addresses. The global routing table is structurally bounded at one entry per ASN. This document is one of the companion specifications: draft-thain-ipv8-00 Core protocol (this document) draft-thain-routing-protocols-00 BGP8, IBGP8, OSPF8, IS-IS8, CF draft-thain-rine-00 Regional Inter-Network Exchange draft-thain-zoneserver-00 Zone Server Architecture draft-thain-whois8-00 WHOIS8 Protocol draft-thain-netlog8-00 NetLog8 Protocol draft-thain-support8-00 ARP8, ICMPv8, Route8 draft-thain-ipv8-mib-00 IPv8 MIB and SNMPv8 draft-thain-wifi8-00 WiFi8 Protocol draft-thain-update8-00 Update8 and NIC Certification
(www.ietf.org)
I'll make the popcorn.
@nuintari Is it supposed to be twice as good as IPv4?
-
So, I think they are serious.
Internet Protocol Version 8 (IPv8)
Internet Protocol Version 8 (IPv8) is a managed network protocol suite that transforms how networks of every scale -- from home networks to the global internet -- are operated, secured, and monitored. Every manageable element in an IPv8 network is authorised via OAuth2 JWT tokens served from a local cache. Every service a device requires is delivered in a single DHCP8 lease response. Every packet transiting to the internet is validated at egress against a DNS8 lookup and a WHOIS8 registered active route. Network telemetry, authentication, name resolution, time synchronisation, access control, and translation are unified into a single coherent Zone Server platform. IPv4 is a proper subset of IPv8. An IPv8 address with the routing prefix field set to zero is an IPv4 address. No existing device, application, or network requires modification. The suite is 100% backward compatible. There is no flag day and no forced migration at any layer. IPv8 also resolves IPv4 address exhaustion. Each Autonomous System Number (ASN) holder receives 4,294,967,296 host addresses. The global routing table is structurally bounded at one entry per ASN. This document is one of the companion specifications: draft-thain-ipv8-00 Core protocol (this document) draft-thain-routing-protocols-00 BGP8, IBGP8, OSPF8, IS-IS8, CF draft-thain-rine-00 Regional Inter-Network Exchange draft-thain-zoneserver-00 Zone Server Architecture draft-thain-whois8-00 WHOIS8 Protocol draft-thain-netlog8-00 NetLog8 Protocol draft-thain-support8-00 ARP8, ICMPv8, Route8 draft-thain-ipv8-mib-00 IPv8 MIB and SNMPv8 draft-thain-wifi8-00 WiFi8 Protocol draft-thain-update8-00 Update8 and NIC Certification
(www.ietf.org)
I'll make the popcorn.
@nuintari I couldn't make it through more than two minutes of reading the sheer contradictions.
I wish to give it no further consideration, except as an excellent example of how an onslaught of truly insane, possibly LLM generated slop is sufficient to tire out the BS-meters from anyone that still has a working one.
I wonder if anyone has ever done fondue cheese with popcorn.
-
@nuintari@mastodon.bsd.cafe why the hate to odd numbers in IP versioning?
@a There is no singular reason they seemingly get skipped. For one thing, they don't, IPv1-3, IPv5, and IPv7 were all concepts that never went anywhere. Anymore? People just pull this shit out of their asses.
IPv8 has already been proposed and tossed once before.
-
@nuintari Is it supposed to be twice as good as IPv4?
@toroidalcore It's twice as many bits, so it's 2^32 times better!
-
@nuintari I couldn't make it through more than two minutes of reading the sheer contradictions.
I wish to give it no further consideration, except as an excellent example of how an onslaught of truly insane, possibly LLM generated slop is sufficient to tire out the BS-meters from anyone that still has a working one.
I wonder if anyone has ever done fondue cheese with popcorn.
@litchralee_v6 Yeah, it's quite the mess, isn't it? We are just going to give every ASN an address space the size of the entire IPv4 Internet, but the minimal BGP announcement size is also supposed to be a /16, which I think they mean what would be a /48, but their LLM generator got confused between their new model and the existing v4 model and keeps saying /16, which would be 281474976710656 IP addresses as a minimum announcement size, which would limit the world to 65,526 BGP speakers.
Mind you I skimmed it, maybe they changed how masking works or something, I dunno. I think someone is taking this seriously, but holy hell, it won't go anywhere, not in this form.
-
@litchralee_v6 Yeah, it's quite the mess, isn't it? We are just going to give every ASN an address space the size of the entire IPv4 Internet, but the minimal BGP announcement size is also supposed to be a /16, which I think they mean what would be a /48, but their LLM generator got confused between their new model and the existing v4 model and keeps saying /16, which would be 281474976710656 IP addresses as a minimum announcement size, which would limit the world to 65,526 BGP speakers.
Mind you I skimmed it, maybe they changed how masking works or something, I dunno. I think someone is taking this seriously, but holy hell, it won't go anywhere, not in this form.
@nuintari Honestly, it's somewhat surprising they didn't reintroduce classful networking. Considering the trainwreck before us, they might as well have defined Class D, Class E, and Class F networks to be /96, /84, and /72, for no obvious reason whatsoever and in stark contravention to anything learned in the last 30 years.
Probably the worst part is that people who don't know better will think that 8 > 6 and therefore ask their network admins to implement this. God help these admins.
-
@nuintari Honestly, it's somewhat surprising they didn't reintroduce classful networking. Considering the trainwreck before us, they might as well have defined Class D, Class E, and Class F networks to be /96, /84, and /72, for no obvious reason whatsoever and in stark contravention to anything learned in the last 30 years.
Probably the worst part is that people who don't know better will think that 8 > 6 and therefore ask their network admins to implement this. God help these admins.
@litchralee_v6 I doubt this goes anywhere, it is patently ridiculous. It reads like every illogical complaint about IPv6 I have ever read.
-
So, I think they are serious.
Internet Protocol Version 8 (IPv8)
Internet Protocol Version 8 (IPv8) is a managed network protocol suite that transforms how networks of every scale -- from home networks to the global internet -- are operated, secured, and monitored. Every manageable element in an IPv8 network is authorised via OAuth2 JWT tokens served from a local cache. Every service a device requires is delivered in a single DHCP8 lease response. Every packet transiting to the internet is validated at egress against a DNS8 lookup and a WHOIS8 registered active route. Network telemetry, authentication, name resolution, time synchronisation, access control, and translation are unified into a single coherent Zone Server platform. IPv4 is a proper subset of IPv8. An IPv8 address with the routing prefix field set to zero is an IPv4 address. No existing device, application, or network requires modification. The suite is 100% backward compatible. There is no flag day and no forced migration at any layer. IPv8 also resolves IPv4 address exhaustion. Each Autonomous System Number (ASN) holder receives 4,294,967,296 host addresses. The global routing table is structurally bounded at one entry per ASN. This document is one of the companion specifications: draft-thain-ipv8-00 Core protocol (this document) draft-thain-routing-protocols-00 BGP8, IBGP8, OSPF8, IS-IS8, CF draft-thain-rine-00 Regional Inter-Network Exchange draft-thain-zoneserver-00 Zone Server Architecture draft-thain-whois8-00 WHOIS8 Protocol draft-thain-netlog8-00 NetLog8 Protocol draft-thain-support8-00 ARP8, ICMPv8, Route8 draft-thain-ipv8-mib-00 IPv8 MIB and SNMPv8 draft-thain-wifi8-00 WiFi8 Protocol draft-thain-update8-00 Update8 and NIC Certification
(www.ietf.org)
I'll make the popcorn.
@nuintari upside will be if it makes a few more people think “maybe IPV6 isn’t that bad after all”
-
R relay@relay.infosec.exchange shared this topic