5 ms·
http://cr.yp.to/djbdns/ipv6mess.html http://cr.yp.to/djbdns/ipv6mess.html (circa 2003)
by js2 13y ago
http://cr.yp.to/djbdns/ipv6mess.html http://cr.yp.to/djbdns/ipv6mess.html (circa 2003)
- gtirloni 13y agoThanks, very interesting read. While reading his argument about all the extensions that need to be done everywhere, I thought about this: since many protocols/etc have to be reworked, will that lead to consolidations (since some protocols will be left behind)? Can we say that currently the IPv6 Internet is a place (almost) free of legacy stuff?
- FedRegister 13y agoThat was always a question I had in the back of my mind. We have this huge address space. Why not reserve a single prefix that means "look at the lower 32-bits of this address and use it as an IPv4 address"?
- karlshea 13y agoThere are, there's a prefix that maps to IPv4 addresses.
- jewel 13y agoThis can be done by the ISP with a combination of DNS64 and NAT64.
- 1c4050b09 13y agoSo sort of exactly like 64:ff9b::/96 in NAT64?
- vklj 13y agoEvery IPv4 packet needs a source address. If the client is IPv6, what is the IPv4 source address? You would want to assign an IPv4 address to the client transparently; and, since they're scarce, share it with several clients. That's what NAT64 does.
- mSparks 13y agoWhy not just have the first 32 bits of ipv6 as equivelent to ipv4 so the ipv6 address of 66.249.73.108 is 66.249.73.108:0
- welterde 13y agoWhat does that gain you over the mapped suffix, where you embed the IPv4 address at the end? (which is used by NAT64, etc.)
- mSparks 13y agobecause as I understand routing is still done from the MSB. So you leave the IPv4 existing infrastructure in place with no modification, but all those /32 addresses now become useful and all the existing IPv4 infrastructure and routing paths still work. Rather than having to replace every single piece of hardware, software, nameserver and routing stack that works on IPv4. I could plug my IPv6 router into any ISP that gives a v4 address and have as many v6 addresses as could ever be needed. It makes no sense to me why you would route IPv4 addresses on v6 LSB, it completely ignores current internet infrastructure and routing.
- welterde 13y agoWhat you propose already exists and is called Teredo,6rd or other tunneling protocols (6to4/6rd is probably the best fit with getting a /48 per IPv4 address). Except they again map the IPv4 space into the suffix of the IPv6 address (or do no mapping depending on the protocol). But you don't want to do that forever as you are now paying for a IPv4 header PLUS some more headers instead of just one IPv6 header if you have native IPv6.
- giovannibajo1 13y agoThat covers ipv6 hosts sending a packet to ipv4 hosts. How do you propose they answer though? They can't put a ipv6 address in the ipv4 header. The full solution is NAT64.