Ugh
-
Ugh
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)
-
Ugh
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)
-
@da_667 JFC this is just IPv6 with more requirements.
-
@da_667 JFC this is just IPv6 with more requirements.
@da_667 IPv8 == IPv4+IPv4
wtf are these people thjinking?@
-
Ugh
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)
@kajer I am willing to volunteer for my company's project to change over, but only if I'm allowed to call it "PROJECT MORE CORN!!!"
-
@da_667 IPv8 == IPv4+IPv4
wtf are these people thjinking?@
holy shit, :RIP: the entire network when you local zone server gets popped.
17.2. Tier 2 - L2 Network Device
L2 devices MUST implement: 802.1Q trunking, VLAN auto- creation on tagged traffic, management VRF (VLAN 4090), OOB VRF (VLAN 4091), switch port OAuth2 binding, LLDP, NetLog8 client, ARP8 (management plane only), ICMPv8 (management plane only), PVRST, Zone Server as PVRST root capability, sticky MAC binding, Zone Server MAC notification.
17.3. Tier 3 - L3 Network Device
L3 devices MUST implement: All Tier 1 requirements, eBGP8, IBGP8, OSPF8, IS-IS8 (available), static routes, VRF (full), XLATE8 (mandatory on edge devices), WHOIS8 resolver, ACL8 gateway enforcement, Zone Server services (if Zone Server role), PVRST root capability, switch port OAuth2 binding support.
17.4. Spanning Tree - PVRST Mandatory
... -
holy shit, :RIP: the entire network when you local zone server gets popped.
17.2. Tier 2 - L2 Network Device
L2 devices MUST implement: 802.1Q trunking, VLAN auto- creation on tagged traffic, management VRF (VLAN 4090), OOB VRF (VLAN 4091), switch port OAuth2 binding, LLDP, NetLog8 client, ARP8 (management plane only), ICMPv8 (management plane only), PVRST, Zone Server as PVRST root capability, sticky MAC binding, Zone Server MAC notification.
17.3. Tier 3 - L3 Network Device
L3 devices MUST implement: All Tier 1 requirements, eBGP8, IBGP8, OSPF8, IS-IS8 (available), static routes, VRF (full), XLATE8 (mandatory on edge devices), WHOIS8 resolver, ACL8 gateway enforcement, Zone Server services (if Zone Server role), PVRST root capability, switch port OAuth2 binding support.
17.4. Spanning Tree - PVRST Mandatory
...LOLOL
OOB VRF (VLAN 4091)ummmm, since when is a vlan "out of band"
Yeah, okay it didnt say airgap, and vlan4091 would not be involved in L3 traffic flows, but damn, defining vlan numbers for management ports seems, a little ... strict. Give me my dedicated mgmt0 interface any day.
-
Ugh
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)
@kajer I actually can’t tell if this is a shitpost or if it’s legit.
-
R relay@relay.infosec.exchange shared this topic
