6 ms·
Enhanced IP: IPv4 with 64 Bit Addresses (2012) [pdf]
- dboreham 5y ago1992: https://datatracker.ietf.org/doc/html/rfc1347 https://datatracker.ietf.org/doc/html/rfc1347
- spodernet 5y agoCan't forget the SIP (Simple Internet Protocol) proposal https://datatracker.ietf.org/doc/html/rfc8507 https://datatracker.ietf.org/doc/html/rfc8507
- mhandley 5y agoOf course that SIP (not my one) and Paul Francis's PIP were what got merged to become IPv6. The rationale was that 128 bit addresses allowed all the flexibility of address hierarchies from PIP within a fixed length address. With hindsight, we've never really tried to use that flexibility in the real world, but the capability is there if we need it.
- pantalaimon 5y ago> With hindsight, we've never really tried to use that flexibility in the real world, but the capability is there if we need it. Maybe not in public networks, but if you run your own network you can easily make use of auto-subnetting. e.g. see [0], [1] [0] https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking_subnets https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_ne... [1] https://summit.riot-os.org/2021/wp-content/uploads/sites/16/2021/09/s03-03.pdf https://summit.riot-os.org/2021/wp-content/uploads/sites/16/...
- hyposcaler 5y agoThere was an IETF draft for this as well, but doesn't look to have really gone anywhere https://datatracker.ietf.org/doc/html/draft-chimiak-enhanced-ipv4-03 https://datatracker.ietf.org/doc/html/draft-chimiak-enhanced...
- d33 5y agoCurious why this hasn't taken off, it seems to make so much more sense to me. Let IPv4 addresses run out. Allow parties to trade them. Slowly migrate from "one IP per box" to "one IP per net" with what looks like NAT, but can easily be traversed if you understand the extension. And once we start running out of IPs again, rinse and repeat. What am I misunderstanding / oversimplifying?
- zokier 5y agoToo little too late. Even in 2012 it was obvious that ipv6 is the future; pretty much everything already supported it, maybe the hardest obstacle was overcome. Maybe 15 years earlier some alternative format could have gotten traction, but then dot-com boom was in full swing and nobody worried about future and ipv4 exhaustion.
- AndrewDucker 5y agoBecause it's not forward compatible - every existing device which speaks IP would need to be upgraded to talk the new way. Which means that, as you have to start over in a non-compatible manner, you might as well use the opportunity to make other improvements.
- ay 5y agoIPv4 options stopped being viable on the internet (everyone drops packets with options) sometime in early 2000s (the quickest doc with references I could find is [0] dated 2014, but I remember the practice started much earlier…), otherwise it looks like an interesting proposal at first sight. Edit: I didn’t read much into detail, assuming that the hosts that do not understand this extension could just ignore the option. If the scheme doesn’t work in this case as sibling comment suggests, then yeah that’s a problem indeed :) [0] https://datatracker.ietf.org/doc/html/rfc7126 https://datatracker.ietf.org/doc/html/rfc7126
- tialaramex 5y agoIt's fun with all these proposals that so many people think they make sense, presumably including their authors. This one has a bunch of grave problems. 1. Notice that the address space shortage is not in fact alleviated although it is shy about admitting that. Nobody who doesn't have addresses gets addresses from this scheme. Instead, everybody who already has addresses gets even more of the new addresses and the author simply hopes they'll choose to give them away to those who don't have any. You know, like that time Bobby Kotick got a huge bonus and so he gave the money to er... oh right, he just kept the money. 2. But wait, how would they give away these addresses? The author proposes they can just give away a /29 at a time. In fact, a IPv4 /29 is not routable as a global route, so this will not work. The smallest size you can carve out from the global routes is a /24 and every time you do this you're making things worse for everybody in the backbone game by increasing fragmentation, gosh they're going to be pleased about so much of this "charity". 3. OK, well maybe instead of giving away addresses, our Good Samaritans will give back their existing allocation and take only one /24 for their own network now that is plenty big enough with the new addresses. But that means they must renumber absolutely everything which is one of the things this proposal was supposed to avoid and all their services lose the ability to interoperate properly with everybody who didn't upgrade yet, getting a degraded "sort of like NAT" mode until everybody in the world upgrades. Suckers. 4. It doesn't bother fixing all the other related infrastructure. That work was done for IPv6. PKIX works for IPv6 (certificates for e.g. the DNS service 1.1.1.1 contain IPv6 addresses, no you can't just write any arbitrary text, that's not how it works at all), DNS works for IPv6, all the fancy modern stuff works for IPv6, but you need to begin over for this "Enhanced IP" and the paper neither proposes any way to avoid that, nor does it include all that work, so you're beginning very late in 2012. Still, there have been much worse attempted solutions written up. My favourites are the ones which don't realise addresses are just bits and propose we can fix everything by writing bigger numbers like 300.400.500.600 ...
- teddyh 5y agoWhat is the rational reason, if any, for bringing up things like these? The time to have this discussion would have been in like 1993 or so. Now, IPv6 is what we have, and the standards are what they are, flaws and all. The only reason I can think of is psychological: People don’t want to learn new things, so they find reasons to dislike the new thing to be able to pretend they don’t need to learn it.
- emptybottle 5y agoI think it could be argued that the flaws in IPv6 are significant enough to result in an scenario where IPv4 is never actually retired and therefore IPv6 is never fully adopted. Its been decades, but still IPv6 is deployed (at best) as a parallel network that effectively doubles management/maintenance overhead. And at worst sites just add an IPv6 reverse proxy.
- pantalaimon 5y agoWhat do you think are the biggest flaws in IPv6?
- exabrial 5y agoI've been advocating for this for a long long time. Just NAT to IPv6 or IPv4 and go about your business.
- feldrim 5y agoI believe that the comment is not a personal opinion but a reflection of the acceptance rate of IPv6. If most of the web still uses IPv4 and not using IPv6 is still defended with the "people against new things" arguments, it shows that there is at least one thing that prevents people from using it. Considering that the new kid on the block is 26 years old, I think, there is more than one.
- lostapathy 5y agoAny new protocol is going to have adoption costs. The "issue" with ipv6 is that for a lot of people/organizations, the tolerable cost of adoption is still pretty much zero. Adding yet another protocol to the mix would not make that better.
- kingcharles 5y agoA day late and a dollar short, as they say.
- yakattak 5y agoCan someone explain to me how about a decade ago we were going to run out of IPv4 addresses in a matter of months and we needed to switch to IPv6 or else, but now we’re still using it fine?
- akvadrako 5y agoThe price per IP used to be almost nothing, now it's about $5/month and will keep going up; you can see these costs clearly with inexpensive hosting providers like Hetzner. As a result many home and mobile users only get personal IPv6 addresses with IPv4 connections being tunneled over shared addresses.
- iso1631 5y agoNot sure who's charging you $5 a month, but $3.70 will get you a VM and an IP, and extra IPs are $1.60 a month on this site https://www.cheapvps.co.uk/plans-openvz.php https://www.cheapvps.co.uk/plans-openvz.php
- CodesInChaos 5y agoMany users don't even have a dedicated IPv4 anymore (dual stack lite) thanks to carrier grade NAT.
- junon 5y agoI would pretty strongly oppose the notion we're using it "fine". IPv4 address allocation requests are on waiting lists. As of November, almost all requests have stopped fulfilling. We've completely run out of them.
- p_l 5y agolots of multiple-layer NATs, plus some legacy blocks got sold to cloud providers
- throw0101a 5y ago> but now we’re still using it fine? You're saying CGNAT is fine? * https://en.wikipedia.org/wiki/Carrier-grade_NAT https://en.wikipedia.org/wiki/Carrier-grade_NAT That having to NAT on your home Linksys/Asus and then getting NATed again by your ISP is fine? If you want to allow a connection to your PC or gaming system, how do you hole punch a double-NAT exactly?
- 2Gkashmiri 5y agoi have a question, when iphone was introduced in 2007, 3G came AFTER that, then 4g and now 5g. why didn't the mobile revolution help move ipv6 adoption? i mean at the time, why wasn't 3G built on ipv6 instead of basing on ipv4? couldn't apple have forced websites to play nice with ipv6 to get more users from iphone crowd? android would have followed suit? i get the whole legacy thing but since transitioning to lets say gigabit internet and beyond, that is somewhat fresh tech so why wasn't that stack made ipv6 primarily and not ipv4? i am truly clueless on this
- zokier 5y agoMobile is leading the IPv6 transition, for exactly the reasons you think it is. It just happened bit later than what you expected. I'm pretty sure that vast majority of 5G deployments support IPv6.
- p_l 5y agoiPhone 2G was released when 3G networks were becoming common among better telcos. For critical period in the early 3GPP network stack, it was niche player. However, Mobile networks are actually biggest users of IPv6, especially if the rumour I heard about licensing being cheaper on IPv6 is true (IPv6 is also in many ways cheaper on backbone implementation). This is why Apple recommends IPv6 accessible sites, because for many mobile networks IPv6 is faster - it avoids multiple levels of network address translation through possibly limited number of gateways. The mobile stack itself doesn't really care for IPv4 vs IPv6 except for v6 making it much easier to build the network and having easier IP Mobility (keeping connections across moving addresses). Protocols run perfectly well on both v4 and v6 (SIP, IPsec, various other L4 and higher protocols involved)
- ksec 5y ago>3G came AFTER that, Oh my. 3G predate iPhone by a lot. There were 3G Smartphones ( Symbian ) or 3G Mobile phones years before iPhone. The first 3G network if I remember correctly "launched" before year 2000 in Japan. ( That is why some analyst suggest that iPhone was bringing the Japanese Internet to the world with touch screen. ) The 3G Spec ( Now known as 3GPP ) predate 2000. 4G was the first system moving from circuit switch to packet-based switching. As that was a lot on their plate already. Remember 4G was designed in an era where 3G was considered a flop. Billions were paid to buy spectrum and equipment but MNO for years were losing money. iPhone was the saviour to MNO as Apple managed to push ARPU instead of their death spiral. There were talks of a completely new network stack for 5G and later 6G. I think that is still an ongoing research. But without Smartphone I am willing to bet ipv6 would have been no where nearly one tenth of today's usage.
- mhandley 5y agoI wrote a proposal back in 1999 or so exploring IPv4-in-IPv4 as an alternative to IPv6. You would have used the outer IP header to traverse the internet backbone, and the inner IP header locally. It completely avoided the need to change any inter-domain infrastructure and, with some DNS-based gatewaying where the gateway to the Interent added/removed the outer IP header, could even be incrementally deployed to unmodified end systems (the idea was you would eventually modify end-systems/applications to add the outer header, as this simplifies applications and avoids the DNS hack). But in the end, IPv6 is cleaner, and it seemed better not to distract too much from progress there. If I'd known it would have taken another quarter century to make much progress, I might have made a different decision. There were quite a few "extend IPv4" solutions over the years.
- ArchOversight 5y agoISP's can already do that... by repackaging IPv4 traffic into IPv6 (when I worked at an ISP this was an experiment that was being done to test the viability to reduce IPv4 address requirements across the backbone, but you could also tunnel it over IPv4 I guess) so that the traffic traverses their entire network inside an IPv6 tunnel, and would get translated back to IPv4 on the edge. As a user you lose some visibility in terms of what routers your packet traverses, but the same can be said about MPLS tunnels/IPSec tunnels where your packet magically seems to have gone just 1 hop instead of the 10 it actually took.
- mordae 5y agoStill no HN over IPv6?