Re: IPv8 / BGP8 / CF
Jamie Thain via NANOG <[email protected]>
| Newsgroups | gmane.org.operators.nanog |
|---|---|
| Message-ID | <CAGPjif8ePkw=2rsy2jhV6VbVtotcDZvQ0cQx3DMFBB3-Pc39VA@mail.gmail.com> |
Shrihari, The point I'm trying to work thru right now is the fib has a field to mark forwarding for v4vpn type ii and if for the asn i make a vrf = asn and an rd of asn:65535 i might be able to avoid tunneling and use the silicon while in transition. Ipv8 is not a 64 bit address its an 32bit asn postal code. And a 32 ipv4 address. Jamie On Wed, Apr 29, 2026 at 7:36 PM Jamie Thain <[email protected]> wrote: > Shrihari > > Let's think about it for a while. There are two ways to transport things > in an ipv8 network. > > 1. Inside the asn and it's basically ipv4 with a path set so it takes a > lookup to the next ipv4 hop but at the ipv8 router inside the asn it makes > a decision on the ipv4 address destination part and sends it to that > encapsulated address. > > So basically the loopback of that ipv8 address. > > 2. Outside the asn it send it to the ipv4 anycast address. > > There are 2 more lookups but the superscalars are not aware of it. > > It's not 64 bits of address it's area codes plus address. > > So what do you think? > > Jamie > > On Wed., Apr. 29, 2026, 6:09 p.m. Shrihari Pandit, <[email protected]> > wrote: > >> Jamie, >> >> You should have spoken with the hyperscalers driving industry growth. >> Apple, Google, Mirosoft, Amazon. Most modern silicon and routers are built >> around them. >> >> 1. Modern routers are built on merchant silicon ASICs (Broadcom >> Jericho/Tomahawk, Cisco Silicon One, Marvell Prestera, etc.) >> 2. Majority of these chips implement forwarding using fixed pipeline >> stages. >> 3. Lookup are done in TCAM (SRAM) structures pre-optimized for specific >> key widths. >> 4. v4 lookup = ~32-bit key, v6 lookup ~128-bit key. Hard=ware pipelines >> are dimensioned for these two widths. >> 5. IPv8 implies exceed entry width or require multi-stage lookups, >> reducing scale, imo. >> >> You have to realize that forwarding is not implemented in software. This >> is not an incremental evolution like IPv4 to IPv6. >> >> Shrihari Pandit >> Stealth Communications >> +1-212-232-2025 >> *stealth.net <http://stealth.net>* >> >> >> >> On Wed, Apr 29, 2026 at 2:23 PM Jamie Thain via NANOG < >> [email protected]> wrote: >> >>> Hi All, >>> >>> My name is Jamie Thain I'm the creator of IPv8. It's not a hoax. >>> >>> 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? >>> >>> I believe that since IPv8 solves the duopoly problem, it will replace >>> IPv4. >>> >>> 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://l.shortlink.es/l/3ae384c1b8e2eb92749595407c5cf9b87ea3372a?u=12457652 >>> > >>> >>> >>> So each ASN in the world will have 3 Billion available addresses. >>> >>> There is a specially reserved group of internal ASN 127.x.x.x so each >>> corp, >>> org, has 16 Million areas of 3 Billion addresses, to replace 10.x.x.x and >>> 100.64.x.x.x >>> >>> I'd appreciate your thoughts on it >>> >>> Jamie >>> _______________________________________________ >>> NANOG mailing list >>> >>> https://lists.nanog.org/archives/list/[email protected]/message/KPDE4FNBRLQYZOVF5FUAAGJCBSKNS42Q/ >>> >> _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/EIVSNE525CR7I5CLB5DYCOK5JDSXDBUR/