Re: IPv8 / BGP8 / CF
Jamie Thain via NANOG <[email protected]>
| Newsgroups | gmane.org.operators.nanog |
|---|---|
| Message-ID | <CAGPjif_f2DO3aQBvfL8ta6q8hGMaj64fto-X-dxy5zca9caL0A@mail.gmail.com> |
Job,
That is an interesting premise. But its wrong. That premise is that there
are only 2 ways to "add bits"
1. Dual Stack
2. Translation
and thats wrong a third way is
3. Encapsulation
In IPv8 it is NOT a new protocol it is IPv8 with the ASN numbers + others
as (Routing Numbers)
Each ASN / RN has any anycast IPv4 from every IPv8 router.
IPv8 client -- IPv4 -- Ipv4 -- ASN (Ipv8 -- Ipv4)
So for example, if you were Google 15169 and you wanted to get to
15169.20.20.20.10 you as the IPv8 client sees the next hop is an IPv4 hop,
and so you look up the Anycast of 15169, lets say its 20.20.10.10 and you
send the packet to that anycast ipv8 router, encapsulated in ipv4.
At that end it unecapsulates it,
And delivers it.
So Encapsulation is the key.
Jamie
On Wed, Apr 29, 2026 at 4:34 PM Job Snijders via NANOG <
[email protected]> wrote:
> I thought Brian's "Why IPv6 is so complicated" was interesting,
> especially the "Why adding bits isn't simple" section.
>
>
> https://github.com/becarpenter/book6/blob/main/01.%20Introduction%20and%20Foreword/Why%20IPv6%20is%20so%20complicated.md
>
> Kind regards,
>
> Job
> _______________________________________________
> NANOG mailing list
>
> https://lists.nanog.org/archives/list/[email protected]/message/5ZNXWVNJZ6TVZL4W5OXJ22RIJ5J6LUA5/
>
_______________________________________________
NANOG mailing list
https://lists.nanog.org/archives/list/[email protected]/message/W4FKOIUBAEPCLURFLNIDY56UAH6W4RR4/