2 ms·
Some interesting information from the author, Jamie Thain, where they introduce the idea on nanog: https://seclists.org/nanog/2026/Apr/96 https://seclists.org/
by mmooss 6mo ago
Some interesting information from the author, Jamie Thain, where they introduce the idea on nanog:
https://seclists.org/nanog/2026/Apr/96 https://seclists.org/nanog/2026/Apr/96
I joined this list because, as part of IPv8, I am creating a BGPv8. Inside
BGPv8, two new protocols CF (Cost Factor), weigh cost factors along the
routes to produce a better metric. It's a hybrid of EIRGP mixed with BGP to
create better engineering results.
I also as part of CF created Sun Tzu which is the protocol that watches CF
and gives you a CF score of reliability. Do I trust my partnership with
you?
Now, beyond an on-slaught of IPv8 is stupid, IPv6 solves every problem,
etc, etc. That's not my discussion point. My point isn't "should I even
propose IPv8" my point is what would be the best result for operators?
So the things to know, IPV8 is NOT a 64 bit addressing system.
It is a 32 bit routing system with a 32 bit addressing system.
A Routing Number = ASNs plus others.
8.8.8.8 would become 15169.8.8.8.8
https://www.ietf.org/archive/id/draft-thain-ipv8-02.html https://www.ietf.org/archive/id/draft-thain-ipv8-02.html