12 ms·
The IPv4 Cleanup Project
- mike_d 5y agoJust like weight loss can't be done with just diet or just exercise, promoting IPv6 isn't the only answer. We need proposals like this and we need to take on the engineering work to make class-E v4 accessible until 100% of the population has v6 connectivity.
- tie_ 5y agoSo the answer is pills that can damage your health while having no long-lasting benefit? One other hidden cost - all the body of knowledge (courses, tutorials, books, blog posts, etc) that we have accumulated over the years for IPv4 would now start being slightly incorrect and misleading. That's no longer the IPv4 that we know - it's rather something like IPv4.5. Instead of inventing new IPv4 mutations and pouring energy into getting them adopted across the Internet, causing incompatibilities and countless lost hours of debugging, adopt IPv6 instead.
- mike_d 5y agoWould you recommend any company take their website v6 only right now? What are we supposed to do until IPv6 adoption reaches 100%? Just say that only existing v4 holders can have dual stack sites?
- byhemechi 5y agothere's no way that this would ever work, so many programs just will not accept packets from class e ip space also, i lost 8 kilos by both eating and exercising less, so your metaphor isn't even true
- api 5y agoAnything extending the life of IPv4 is actively harmful. (Like I said last time this was posted.) The most important problem with IPv4 is that it mandates 1:N NAT configurations that break direct connectivity between devices on the Internet. Yes you can traverse NAT but it's an ugly and often unreliable hack. This of course is because the address space is too small for everything to have an IP, whether global or 1:1 NATed. Difficult peer to peer connectivity means everything has to have a server. You can't just write communication apps that... communicate. The added cost here is enormous both in money and in privacy/security. IPv4 is also too small for private networks. Corporate networks are often full of hideous hacks like multiple NATs that negotiate interoperability between networks with overlapping 10.x address spaces, "theft" of unused IPv4 space such as US DoD addresses, etc.
- perryizgr8 5y ago> Anything extending the life of IPv4 is actively harmful. +1 > Yes you can traverse NAT Not always. My ISP uses CGNAT, which means I have absolutely no straightforward way to break out. I'm confused why people are willing to develop hacks on top of hacks just to avoid using IPv6. It is really elegantly designed.
- yarosv 5y agoI'm not a network engineer. But I've yet to see a good way to protect ipv6 network. I don't want my local webserver develop on to be exposed to the internet. It's my understanding that default router configuration will do just that. I don't see a good way to deal with privacy issues. Ipv6 essentially gives a unique identifier for every computer in the household by default.
- kazen44 5y agoprotecting ipv6 Networks works just the same as ipv4 networks. by using firewalling. NAT is not a security mechanism. most consumer routers seem to block any incoming traffic from the outside world by default anyways.
- yarosv 5y agoI'm not trying to be aggressive here. But what's the actual end user difference between NAT and firewalled ipv6 for me and my local network then? I assume I could route now than one addresses for a specific port. On the other hand I have to pay for domain record to access my local resource without a struggle. Should I use ipv6 at home when my doesn't have one? I honestly struggle to find good information on the protocol that's decades old. It's either to deep for me to care for my needs or too shallow to understand why and how should I just it. Scaremongering is what I find on the internet. And no real benefits for me to update my hardware or find ISP that has ipv6.
- api 5y ago
- 0x0000000 5y agoThe price for IPv4 addresses is up about 400% in the last 18 months or so. Freshly available addresses would be very welcome.
- foobiekr 5y agoThese prefixes would mostly not work, however, so will not solve the problem. This smells of engineers saying “why not just do Y so we get X?” without realizing that in the real world, X is not an achievable state.
- whoknowswhat11 5y agoThis illustrates as I've said how out of touch IPv6 folks are. The demand for IPv4 is incredible right now. The value of a /8 went from $0 to close to a billion dollars. The claim that new IPv4 space has no value is ridiculous. These ranges don't have to be perfect. I think IPv6 folks just don't understand how high the demand for IPv4 is, it's gone UP since IPv6 came out and folks have realized IPv6 is going to be much much harder to adopt then expected. And this proposal does nothing to stop IPv6. You know your IPv6 proposal is bad when it depends on stopping others from improving alternatives :)
- kazen44 5y ago> The claim that new IPv4 space has no value is ridiculous. These ranges don't have to be perfect. yes, they do have to be perfect, because having a range which is not usuable by a part of the networks and devices that make up the internet drastically decreases their value. The reason IPv4 space is so valuable is because migrating to ipv6 still has a higher friction then ponying up money for additional ipv4 space. It will be a matter of time before this changes and implementing ipv6 is far easier in comparison.
- mentalpiracy 5y agoThe amount of money this IPv4 space is valued at now - while astronomical in comparison to past pricing, sure - might as well be $0 when you compare it to the colossal expenses in both funds and manpower to update literally decades of now-critical infrastructure that treated this address space as sacred. Galaxy brain magnitude of difference here. This analysis strikes me as exactly the same type of MBA-rot that chases quarterly earning reports over long-term business health. This sale benefits, in real terms, zero people, while imposing costs on almost every single existing user (whether they realize it or not).
- guardiangod 5y ago>0/8, 127/8, 224/4, 240/4 Why would anyone even bother. All the scripts and programs that were hardcoded to treat 127/8 as loopback and 0/8 as various default routes would need to be changed and more importantly, verified. You wouldn't want anything that's hardcode bind to, say, 127.48.47.218 as localhost to suddenly be routable from the internet. I vaguely recall Cloudflare uses a huge chunk of 127/8 as internal loopback addresses for their edge servers. Without Cloudflare's support this proposal is DOA.
- schoen 5y agoJohn Gilmore (who founded this project and whom I've been consulting for on it) has talked about this in the current NANOG mailing list thread about our proposals. He has several posts there, but the most relevant to your specific comments is probably https://mailman.nanog.org/pipermail/nanog/2021-November/216457.html https://mailman.nanog.org/pipermail/nanog/2021-November/2164...
- guardiangod 5y agoLet me perface this by saying thank you for being sincere and civil, because what I am about type might not be up to the standard you established. I read that email and there's a serious tons of hand waving and 'dude, trust me.' I am going to ignore "would be useful to a lot of people -- hundreds of millions of people who you may never know." There's no example use case of who the hundreds of millions of people might be, and how this proposal would benefit them. What are the benefits that the existing CG-NAT and ipv6 couldn't provide? I am also going to ignore "one-line patches is almost risk-free." Sure if all the software in the world is only Linux/Windows/BSD TCP/IP stack and no one build anything on top of the stacks, then the patch would indeed be only 'one -line'. What I really have a problem is 'simply include them in new releases of the various operating systems and router OS's that implement the Internet protocols.' I work for a _major_ hardware firewall company, and it is ridiculous the amount of effort we would put on our customers to upgrade their firmware. There are still hardware that run with 15 year old firmware (with all the accumulated CVEs). You are telling me it's easy to convince these people to upgrade their stuff? Are you serious??? 'People naturally upgrade their OS's every few years." Oh I guess we can ignore all the IoTs and middle-boxes on the interweb then. "We have tested major routers, and none so far require software updates to enable most of these addresses." As mentioned I work for a firewall company. I just logged into a sample firewall under my control- yes the configuration is doable. But in enterprise, everything needs to be rigorously tested or else the sysadmin's not gonna touch it. The sysadmins are certainly not going to waste a few weeks of their lives testing things that might bring down their entire network, and would only benefit the select few who managed to grab ahold of the new IPs. It's late at night and I don't want to continue. So here.
- schoen 5y agoI'm sorry we don't have a nicer landing page for this project. One of our drafts was posted and discussed on HN two days ago https://news.ycombinator.com/item?id=29246420 https://news.ycombinator.com/item?id=29246420 and as I mentioned in that thread, the complete set of four drafts is https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-lowest-address/ https://datatracker.ietf.org/doc/draft-schoen-intarea-unicas... https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-240/ https://datatracker.ietf.org/doc/draft-schoen-intarea-unicas... https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-0/ https://datatracker.ietf.org/doc/draft-schoen-intarea-unicas... https://datatracker.ietf.org/doc/draft-schoen-intarea-unicast-127/ https://datatracker.ietf.org/doc/draft-schoen-intarea-unicas...
- sneeeeeed 5y agoThis is a terrible idea.
- zinconfire 5y agoThe energy that is being spent convincing millions of nodes to talk to 127/8 might be better spent convincing those nodes to talk IPv6.
- yardstick 5y agoThere’s a lot less effort required to update an existing IPv4 system to accept a few more ranges than to entirely rearchitect a network to work with IPv6. Plus there’s a lot of energy in this world to do both without one taking away effort from the other. But as to the actual proposition, I would rather the 240/4 space was changed to RFC1918 private space, or at least half of it.
- svennek 5y agoReally? I for one am not looking forward to all the frankenbugs when new stuff on those IPs talk to old stuff (middle and endboxes)... The great part about IPv6 in that regard is that you are either capable or not, not mostly compatible as an older client would be with this "ipv4+" thingy..
- yardstick 5y agoIPv6 implementors are inconsistent in what they support. Eg Android and it not supporting DHCPv6 [1]. Also NAT in IPv6 is not as widely supported as it is in IPv4 (and yes NAT can and is used for reasons other than security, such as policy based routing and routers with multiple disparate WANs like Fibre and Cellular). Plus there will always be someone somewhere with a middlebox, be it IPv4 or IPv6. 1. https://lostintransit.se/2020/05/22/its-2020-and-androids-ipv6-is-still-broken/ https://lostintransit.se/2020/05/22/its-2020-and-androids-ip...
- dcbadacd 5y agoNot implementing DHCPv6 is not "inconsistent" it's from the start a thing you should NOT rely on existing.
- 5y ago
- DanAtC 5y agoI don't understand why two EFF-adjacent personalities have an interest in making more v4 addresses available which will ultimately end up in the hands of giant ISPs and corporations.
- jbverschoor 5y agoBecause of NAT, a lot of systems and networks are not secured properly. If suddenly everybody has an ipv6 accessible device, there will be sooo many hacks
- fuzzy2 5y ago> If suddenly everybody has an ipv6 accessible device, there will be sooo many hacks Not really though? Just because the router no longer does NAT doesn’t mean it’s no longer a firewall.
- jbverschoor 5y agoWho's going to configure this properly? Some apps will need to punch holes in the firewall.. It simply hasn't been tested enough. Especially in home / small office situations.
- fuzzy2 5y agoWhat even is there to configure? An IPv6-capable SOHO router ships with a “forward only related, established” config by default, to put it in IPTables terms. Most of the time, you won’t even have the option to disable this entirely. There is nothing to test either because this is exactly how SOHO routers have been working for decades.
- p4bl0 5y agoApart from 0/8 with 0.0.0.0 mostly, and 127/8 with 127.0.0.1 mostly, what are those other reserved address spaces used for?
- anthropodie 5y agoWhat happens when those additional 419M IPs get exhausted? Move to IPv6? Why not do it today?
- knorker 5y agoThere's no chance in hell class E, 127/8 or even 0/8 will work within 20 years. The effort is doomed. If you thought it was a lot of work to upgrade to IPv6, forget about it. - Hey ISP or cloud provider, do you want some of that sweet sweet class E? - Will users be able to connect to it? - Nah. Well, some will. As long as you're happy with people spending the next 20 years complaining about how "your servers are always broken", you can have some addresses. It's a complete waste of effort that should instead be spent adding support for IPv6. Spend huge effort on something temporary throw-away, or on something long term? The temporary thing will take at least as long to implement, and you will never know if you're actually done or not.
- whoknowswhat11 5y agoIt's really interest, I think it's partly this attitude by the IPv6 folks that have stymied IPv6 adoption. It's this - you are an idiot, this is a waste etc. The reality, out of the millions of users of IPv4 space, some will find some use for 0/8. Will it be worth as much as other IPv4? Maybe not. But hard to imagine it being worth zero. The other piece, if IPv6 is so great - then this does nothing to stop the rapid adoption of IPv6 by both the major players (cloud providers) and small players.
- knorker 5y ago> It's really interest, I think it's partly this attitude by the IPv6 folks that have stymied IPv6 adoption. If you don't like the answer the doctor gives you, the answer isn't to stop going to the doctor. > It's this - you are an idiot I didn't attack the person. Please stop misrepresenting me. You are the one getting personal here. > The reality, out of the millions of users of IPv4 space, some will find some use for 0/8. Who? Really. Who? To be even more specific: Who, who today is hungry for public IPv4 space, and doesn't really care if it's publicly usable or not? > Will it be worth as much as other IPv4? Maybe not. You're missing the point. Something that's "kinda broken forever" is much worse than not having it at all, when there is an alternative. If you can't get IPv4 for your cloud service, then you price the working addresses such that avoiding waste is a thing. > But hard to imagine it being worth zero. No, not zero. Just a worse value proposition than switching to IPv6, with a "good and working IPv4" proxy path in the mean time. > The other piece, if IPv6 is so great - then this does nothing to stop the rapid adoption of IPv6 by both the major players (cloud providers) and small players. I'm not competing. I'm saying it's a bad solution, and there's a better solution out there that's cheaper, more effective, and more long term. This proposal an investment in throwaway work, and I would recommend that nobody adopt it. Also note that at the rate addreses were allocated when we ran out, they were going at an /8 per 3 weeks. This is a huge investment to buy a month or two before we're right back in exactly the same spot? Clearly a bad idea. Client side: NAT. Solved. Server side: Who in their right mind would use 127/8 on their server? IPv4 is just not that expensive.
- exabrial 5y agoipv6 no doubt was designed without the mistakes that ipv4 learned the hard way. Everything from getting rid of useless (and dangerous) flags, to flow identification, is beautifully designed. But, there is absolutely 0 reason for Google, Facebook, etc to know how many devices are operating in your home, or which ones they are communicating with. And before the army of drones screams "ipv6 privacy extensions", the battle has already been lost. Unless every request to Google, Facebook, etc was made with a unique ipv6 address, you cannot assume the same level of privacy that an ipv4 NAT provides. Ipv4 makes Google, Faceebook jump through extraordinary hoops to track you and monetize your personal and private life. Ipv6 makes these things trivial (coincidently, both of those companies are pushing ipv6 the hardest despite owning huge swaths of ipv4 space).
- GoblinSlayer 5y agoPresumably you would have a wifi router in that case? Those work as NAT, even support port forwarding configuration.
- ddtaylor 5y ago> But, there is absolutely 0 reason for Google, Facebook, etc to know how many devices are operating in your home Considering every request going to their servers likely already contains a cookie that identifies them entirely it's extremely likely they already have this information.
- netflixandkill 5y agoIf you participate in facebook etc apps and services at all they have far more insidious and effective tracking and NAT isn't hiding you at all. Additionally the idea that it is granting you any measure of privacy is only true if you're behind a giant translation block with tens of thousands of unrelated people and a broad enough public range that connection correlation becomes impractical, compressing a single family or roommates behind a single public IP that changes maybe every few weeks accomplishes very little if anything. If you need anonymity that much for whatever purpose, depending on v4 NAT is dangerous at best and you should be looking into anonymous proxies or VPN providers (that also mask ipv6), Onion routing, etc.
- LinuxBender 5y agoNOBODY will like this idea, but if you really want to keep using IPv4, then: If the goal is to stick with ipv4 because it is easier then I think you would get more traction if you could convince governments to work with ARIN / RIPE / AFRINIC / etc... to do eminent domain forced consolidation and buy-back of horded IP space. Give companies, organizations, government DISA, DoD, Military and others a year to consolidate their actual usage into smaller CIDR blocks, then governments buy back the unused space at market value. I am not a fan of eminent domain but this would be a valid use of it and could actually happen, accepting there would be a myriad of law suits, stalling tactics and so on. Provide some incentive for people to willingly consolidate in a timely manor such as paying a higher market value for those that get on board early. As crazy and possibly unethical as that suggestion may be, I think it would at least get some momentum and you could possibly gain more than 419M IP's and have less network fragmentation. As a bonus, no need to update router firmware, IoT firmware, operating systems, application configurations, firewall OS, firewall rules and so on.
- eli 5y agoIsn’t the DoD actually using most of those addresses internally? It would take a lot of money and more than a year to change that.
- LinuxBender 5y agoYes. Mandate they encapsulate that internal traffic and egress / ingress through ipv6. I would bet some of this is already in place.
- GoblinSlayer 5y agoOr throttle ip4 traffic giving priority to ip6, and things will fix themselves.