I am an undergraduate student where I decided to develop a firmware that would eliminate the security vulnerabilities that exist within the current technologies used. such as tunneling, translation and dual stack.
To do this I need to understand the packet transporting/routing differences between IPv4 and IPv6 in-order to provide a viable solution. But I couldnt find any resource that would compare these two protocols via diagrams and structures. I was hoping if I could assistance with some resources that i could use to better understand the differences of these two protocols.
I would like to first focus on the differences in IPsec.
i know that IPsec is added to the Packet on the Network layer of the OSI model. But how does the IPv4 and IPv6 differ from one another when it comes to IPsec?
how is the security info is added to both of these at start and removed from at the destination?
IPv4 and IPv6 "coexist" the same as Appletalk and IPX. That is "completely oblivious to each other". While they both start with eye-pee, and share a packet format (at the most basic level), beyond the version number in the IP header, they are completely alien to each other. Study how IPv4 works, then study how IPv6 works. They are far more different than their names suggest.
(I've worked with this stuff for decades, but I cannot point you to any single book (or webpage) that can give you everything you need to know. We're not assembling Ikea furniture here.)
No need for special firmware if you're trying to implement IPv6. People just need to accelerate the move to IPv6. How exactly do you think adding lines of code is going to eliminate security vulnerabilities? IPv4 and IPv6 are already in pretty much everything you buy these days. And IPSEC is built into the IPv6 protocol, but configuration is still required...IPSEC doesn't just happen magically.
The DNS64/NAT64 combination is excellent for allowing IPv6 hosts on a network to reach IPv4 hosts on the Internet. That's how T-Mobile does it for millions of customers. This problem has already been solved.