This is not true, and you obviously have not read the specification. In IPv8 when a station ARPs it ARPs using ARP8 and if there is no response 50ms later it ARP4. If that station replies than IPv8 sends IPv4 packets to that station for the remainder of the ARP time out session.
Except for the r.r.r.r section of the header the rest of the payload IS ipv4.
So to encapsulate between an IPv4 network and an IPv8 network all there is from 4 to 8 add 0.0.0.0 as the source, and asn as the destination. From 8 to 4 remove the 0.0.0.0 as the ASN destination and forward the IPv4 packets.
When you need to traverse from 8 to 4 (or several 4s) to an 8 each ASN has an IPv4 anycast address that is on every IPv8 router and the packets are sent to that address, allowing them to find their way through the internet without tunnels.
It is the absolute compatibility of the payload of IPv4 and IPv8 that makes this easy and teniable.
That's a good question and the core over-states it.
The east-west means that natively clients don't arp and icmp from each other they do it from ACL8 on the GW. Your printer registers, you mark it anonymous, anyone can get to it, and when you arp for it, it answers.
But when you have 2,000 clients on a vlan and you want 1999 of them to only reach the internet and not each other, you make one rule at the ACL server.
It means everything goes to the ACL8 server for a decision even on the local network.
I understand that you don't understand yet, as there is 8 more documents. To clarify it all. First of all at ARP8 it sends ARP8 and 50ms later it sends ARP4 and if the client marks it. An IPv8 only ever sends IPv4 packets to an IPv4 client.
The goal is to clean up the disparate services and get them under control. The spec doesn't demand sweeping new architecture, a company could exist on IPv4 using bootp until 2100, it allows for it.
OAUTH replaces RADIUS and that should of been clearer.
NetLog replaceslog.
CF is hard calculated like EIRGP but you can put cost factor on it like OSPF. If you can think of a better way, let me know.
PVRST I am thinking about that, the issue is the root. MST doesn't work, PVST is too slow. I am hoping to trade with CISCO and they make it open. Most vendors make it in compatible mode now. Arista, Juniper, HPE/Aruba, Extreme Networks, Dell, Huawei.
The Core Draft, only has existed for 4 days. There is a tremendous amount of support for it.
OAUTH and JWT are used for Card to Zone Services, so OAUTH replaces RADIUS.
The addresses of the Zone Server are not hard coded it is the highest and the second highest in the network as it should be.
All of the configs, for users, servers, network cards, updates are now standard protocols, built around OAUTH2.
The problem I'm working to solve is not address exaustion, its improved manageability.
This is not true, and you obviously have not read the specification. In IPv8 when a station ARPs it ARPs using ARP8 and if there is no response 50ms later it ARP4. If that station replies than IPv8 sends IPv4 packets to that station for the remainder of the ARP time out session.
Except for the r.r.r.r section of the header the rest of the payload IS ipv4.
So to encapsulate between an IPv4 network and an IPv8 network all there is from 4 to 8 add 0.0.0.0 as the source, and asn as the destination. From 8 to 4 remove the 0.0.0.0 as the ASN destination and forward the IPv4 packets.
When you need to traverse from 8 to 4 (or several 4s) to an 8 each ASN has an IPv4 anycast address that is on every IPv8 router and the packets are sent to that address, allowing them to find their way through the internet without tunnels.
It is the absolute compatibility of the payload of IPv4 and IPv8 that makes this easy and teniable.