u/ybx332

Recentlly I'm learning the history of the IP protocol, and find out during 1990s, there're IPv7(RFC 1475), IPv8(here I mean RFC 1621, not rencently suspicious vide-drafted document) and IPv9(RFC 1347).

How does IPv6 finally win over other protocols? And why is IPv6 extended to 128 bits? I found out in the early version for IPv6(simple Internet Protocol, RFC 8507), the address length is 64 bits.

Is there any collection for all those kind of historic discussions?

Yesterday I ask a dumb question, but later after tracking packets on the router, I find out I miss something. The router will response RS with RA, but only if the RS includes Source Link-Layer Address.

I don't know why, but it seems like Debian GNU/Linux doesn't include that field in RS packet. So how can I configure network-manager (or something else) so the Source Link-Layer Address can be included in the RS packet?

I know that 464XLAT can enable IPv4-only application to work on the IPv6-only network.

Is it possible to deploy a Nat46(IPv4-IPv6) translation on the gateway so device that only work(e.g. some IoT device) with IPv4 can work on the IPv6 network?

If that's possible, we may be able to finally run IPv6-mostly network at home(phone/computer working with 464XLAT, IoT device working with Nat46+Nat64+DNS64) and specifically use a gateway to put all unsupported device under that.

How can I do load balance with multiple upstream ISPs so I can control the data path when the packet passes the gateway?

Since one of the main goal for IPv6 is end-to-end connection, under this situation, how can I do load balance?

BGP isn't an option since I'm considering home user or small business user, who get their prefix directly from upstream ISP.

This is the ISP I'm currently using. When looking through the chart, I find it very interesting to see there's a massive drop from over 20% to almost 0%. And they provide the user a public routable IPv4 address.

What's the reason behind this decision? Why do they choose to give up IPv6?