13 ms·
Reclaiming IPv4 Class E's 240.0.0.0/4
- Latty 2y agoI'd really just rather get IPv6 working everywhere and not have to deal with NAT. Some more addresses just drags out the problem by reducing incentives to switch, it doesn't solve anything, which is roughly where the article seems to land: > If we are going to start using address space that might not work for all users, it would be wise to pick the address space that we already have a considerable head start on getting accepted: IPv6.
- gmuslera 2y agoThis. It will break a lot of existing applications, devices, firewalls, and have conflicts with companies that are somewhat already using them in a public or private environments. And if we want to do it anyway despite all the trouble, it will only push forward the problem a few months or years. In the other hand, IPv6 is already used by nearly half of internet, and probably most installed infrastructure supports it. And it have a lot of advantages over IPv4, starting with not having to use NAT.
- TheLoafOfBread 2y agoIf IPv6 would be created with a little bit more care for backward compatibility, it could have been years since last server stopped using IPv4. The whole IPv6 fiasco is self inflicted.
- loeg 2y agoYes, yes, but at this point those mistakes have been litigated sufficiently and complaining about them doesn't help solve any of the remaining problems.
- b112 2y agoSure it does. We can just move to ipv8, 5 octlets instead of 4. We can give 2.x.x.x.x to 10. to earth, maybe 100 to 110 for moon, mars, etc. 1.x.x.x.x will be for legacy stuff. If anything is trying to route to only 4 octlets, routers add a 1. in front of it. Bam, legacy solved. edit: I realised people don't see the big picture here. Step 1) We collectively engineer and deploy ipv8, along with RFCs explaining how future expansion works 2) We put all sorts of preparatory work, conversation into the eventual expansion into 6 octlets, from 5. We'll need that once we colonize multiple systems. 3) The RFC will state that "new planetary systems get space on 5th oclet, 1.200.x.x.x.x to 1.250.x.x.x.x. 4) As systems grow to need more than an ipv4 range, we transition them to their own 6th oclet. It's easy for them, because they can retain legacy 5th octlet headers. 5) We then collectively freeze our brains, so that in the future, once interplanetary, faster than light communication exists, we are thawed to deal with the 5 to 6 oclet transition! And we all become immortal. But no, that's fine, think small, stay non-immortal with your ipv6 Flanders!
- deleted 2y ago[deleted]
- ynik 2y ago> If anything is trying to route to only 4 octlets, routers add a 1. in front of it. Bam, legacy solved. Only for unidirectional UDP. How do you think the other side would be able to respond if it's unaware of the 5th octlet? Basically every protocol in existence requires two-way communication and there's no backward compatible way of providing that.
- b112 2y agoI covered that. Edge routers transition 1.x.x.x.x to x.x.x.x as a default, and x.x.x.x to 1.x.x.x.x. This is an interim change, so that ipv4 can communicate to ipv4 forever. Legacy systems can be supported on ipv4 only, relegating them (just as they are now!) to not having access to that new address space.
- growse 2y ago
- rcxdude 2y agoWhat kind of backward compatibility are you imagining? If you say "with ipv4 addresses", how are you imagining that would work?
- TheLoafOfBread 2y agoKeep the structure and services around IP protocol (DNS, DHCP, NAT), just with more bits for address. Do not try to reinvent the wheel and add unnecessary breaking bell and whistles which nobody asked for.
- jcranmer 2y agoAll of these things already exist for IPv6, although I don't know how much DHCPv6 is deployed in practice.
- baq 2y agoIt should be deployed everywhere where IPv6 is deployed and there's an IT department if only for logging/audit.
- kccqzy 2y agoStateful DHCPv6 does not get deployed because IPv6 purists at Google refuse to implement them on Android. And I in fact agree with them. And DHCPv6 isn't needed for logging/audit: the router always has an association of MAC addresses and IPv6 addresses even if hosts assign their own addresses with SLAAC.
- bigstrat2003 2y ago> Stateful DHCPv6 does not get deployed because IPv6 purists at Google refuse to implement them on Android. Which is absolutely ridiculous. Google should not be trying to dictate to their customers how to run infrastructure. If someone wants to use stateful DHCPv6 for their Android devices, that is their right and Google has no business standing in their way.
- icedchai 2y agoCan you describe how you'd make it more backwards compatible? I often see comments like this, yet nobody can work around the fact that you're limited by 32-bit source and destination headers in V4.
- jedberg 2y agoIt's pretty simple. If IPv6 headers were split into two parts, where the first part was the same as IPv4, and the second part had the rest of the bits, so you had say 8 octets instead of 4. The rest of the header would look like data to an IPv4 router. So your IPv6 address would be 1.2.3.4.5.6.7.8. The header would have 5.6.7.8 as the IPv4 destination. When it got there, that router would unpack the rest of it and send it off to 1.2.3.4.5.6.7.8. If that host had to talk to an IPv4 host, it would just use the IPv4 headers. Then IPv6 traffic could pass over IPv4 networks without any changes. The only constraint would be that each IPv6 network would have to have an IPv4 "gateway" address. Old IPv4 hosts wouldn't be able to talk to IPv6 endpoints, but at least this way the user could upgrade their own stack without having to wait for their ISP, and every network in between, to also upgrade. It's pretty much carrier grade NAT but from client to client without ISP support being necessary, which is the biggest bottleneck right now.
- andrewshadura 2y agoThis has been proposed many times already, and it actually wouldn't work.
- jedberg 2y agoWhy not?
- ianburrell 2y agoBecause the IPv4 host can't talk to new protocol hosts. IPv4 hosts can only do 32-bit addresses and don't know about the wrapping. If they did, they would be new protocol hosts. I had idea of putting the internal address for NAT in options so could be addresses directly. But too many boxes would need to be changed, and lots of unchanged boxes remove options. Plus, all the IPv4 applications wouldn't know what to do with stack of addresses. It would devolve to NAT.
- Macha 2y agoEarlier IP migrations were done when the internet was run by universities and government bodies who felt the need to migrate to a newer standard because there was a newer standard. IPv6 took longer because the internet is now run by companies that need to see a return on investment, and as long as IPv4 was working fine for their customers, didn't see a benefit to it. It's why IPv6 adoption only started taking off when the answer to "Our projected customer growth this year is 200,000, can we have 200,000 more IPv4 addresses please?" became "No".
- api 2y agoIt was created by people who were used to the Internet being an ultra high trust relatively close knit community of universities, research, government, and industry. Upgrades across the net had happened before just fine. This one should be no problem. This was around 1996, which is when the vertical growth phase took off. Too late.
- dboreham 2y agoThis was deliberate: the idea was that IPng wouldn't get adopted, or even traction in the IETF, if it didn't provide additional functionality/fix perceived problems beyond just address space exhaustion. Remember also that NAT wasn't really a thing at that time. It might have existed but wasn't widely used like happened subsequently. Source: was there.
- JoshTriplett 2y agoI can certainly understand that perspective. But from today's perspective, it seems like IPv6 adoption was slowed by ideological arguments like "people should use SLAAC, not DHCP". By all means introduce a new means of obtaining addresses, but let it live or (preferably) die on its own merits, rather than attaching it and a dozen other albatrosses around IPv6's neck. If IPv6 had started from day one by saying "just add an IPv6 block to your DHCP server and let any client that understands IPv6 get an IPv6 address", that would have been an easier sell.
- tonetegeatinst 2y agoThis. IPV4 is a mess.....and its extremely frustrating just how unsupported ipv6 is. IPV6 is one of those things where if isp,'s just switched over to it, I'd have so less nightmares caused by cgnat and that bullshit like how expensive static IP's are. Many its because I'm not working at a ISP or a teir 1 backbone but forcing the transition to ipv6 seems like overall it would be less of a clusterfuck than our current ipv4 stuff. I know their is stuff going to break, anytime changes are made at this scale it often has some hickups....but dear god I really hate how static IP's are so expensive, and how expensive a small IP block is. Also IPV6 is just an excuse to get fiber everywhere.....I hate how slow many services are.
- mike_d 2y agoPeople hail CGNAT and IPv6 as the savior but don't realize you still need v4 addresses to make it work. CGNAT at scale functions by assigning a range of ports on a shared v4 address to a downstream customer. You can normally get between a 1:8 and 1:32 "compression ratio." We still need to free up additional IPv4 to keep the internet growing. Don't let the "just switch to v6" crowd fool you, both solutions need to addressed in parallel.
- viraptor 2y agoThat's a really confusing comment. Cgnat is almost universally criticised. IPv6 doesn't need ipv4 addresses. Cgnat and IPv6 are not related.
- mardifoufs 2y agoMaybe they meant NAT64? Not sure though
- mike_d 2y agoIPv6 depends on IPv4 addressing if you have downstream devices that need to reach the entire internet. If you go to ARIN they have an explicit policy of allocating IPv4 blocks to facilitate IPv6 deployment. CGNAT is a term that broadly used to refer to carrier-scale solutions to deal with issues with number exhaustion and dual-stack deployments. What most people think "CGNAT" is, is actually NAT44. https://nfware.com/blog/why-cgnat https://nfware.com/blog/why-cgnat
- api 2y agoI am absolutely convinced that the main thing holding V6 back is not even that it’s a full shift rather than an incremental upgrade. It’s that the addresses are too long to easily remember or type and the text representation is unwieldy and aesthetically ugly. Anyone who has ever done net stuff for a living knows that you type or copy paste addresses constantly. Whenever I say this to V6 evangelists they say “we’ll use DNS” which is “tell me you’ve never been a net admin without telling me.” I’d love for V6 to get traction but I think something needs to be done about the usability issues before it will happen. Even little details like the fact that in no terminal does double clicking on a V6 address properly select it is a huge problem. Yeah you might be able to change that but that custom config won’t be there on the next machine, etc. Even seemingly simple usability problems are death to adoption.
- jauer 2y agoI’m a NetEng for a large (>1M servers, >100 POPs) network that is IPv6-only internally. It’s not hard to remember IPv6 addresses for DNS servers assuming your addressing plan reserved the right subnets for anycasted services. Remembering IP addresses stops being a thing pretty quickly. If anything the challenge shifts to remembering airport codes. If you are typing them by hand that often even in IPv4 networks I'd be worried about typos and insufficient automation. I think it’s more that small and medium organizations just don’t have any incentive to change (and plenty of incentive to not take the risk of change) leading to the numbers we see at https://ipv6-in-real.life/ https://ipv6-in-real.life/
- michaelt 2y ago> If you are typing them by hand that often even in IPv4 networks I'd be worried about typos and insufficient automation. Automation is all very well once the network link is up and working so you can reach the automation But the reality is you put someone who knows what they're doing in front of a machine where the network connection isn't working, the first things they're going to be doing is ifconfig and ping 8.8.8.8 - which they'll be doing from memory, because you can't google anything when your network connection isn't working. The fact that IPv6 will deprecate both ifconfig and 8.8.8.8 to me seems emblematic of why the adoption has been going so badly.
- vaylian 2y agogithub.com reachable via IPv6 when?
- eqvinox 2y agoWhen you set up NAT64... ... :-( ... goes to cry in a corner
- ta1243 2y agoI'd rather deal with NAT than have multiple IPv6 address ranges on my network, even if I could stop using ipv4
- mikl 2y agoThe absurd lengths this industry goes to, only to avoid the switch to IPv6. Wish the FCC would step in with a mandate or something, it’s just long overdue.
- xacky 2y agoNetworking software and routers without ipv6 should be considered a security issue at this point and should have CVEs assigned against them. It's amazing how we deprecated unencrypted http across the internet but still use the equivalent for ip addresses.
- john01dav 2y agoIpv4 is deeply flawed and needs to be replaced, but how is it insecure? CVEs are specifically for security issues.
- lagniappe 2y agoThis is NOT how the CVE system is used.
- DaSHacka 2y ago> It's amazing how we deprecated unencrypted http across the internet but still use the equivalent for ip addresses. This makes no sense, http is flawed because its unencrypted and allows MITMing information. IPv4 is flawed merely because it doesn't have enough addresses. How are these two comparable? Your proposed "solution" is overkill and is completely ridiculous.
- itchyouch 2y agoIt’s not a logical argument, but if we only take the part about the transition to https, the difference was that https and http coexisted with mostly full compatibility to go between the 2 for its whole life. And it lives at layer 4. A more cogent argument is that IPv4 and IPv6 have not fully coexisted like http/https, where you can pull the ipv4 rug out and every packet has an ipv6 path like http to https did. Also more profoundly, https conversion had the benefit of every operator being able to transition on their own time frame. And people can still opt to use http if they so choose. IP not having that luxury is a profound problem.
- binwiederhier 2y agoGreat article, thank you for enlightening us. > While there are somewhat ongoing efforts to see 0.0.0.0/8, 127.0.0.0/8 become routable unicast space I am curious about this statement. How can 127/8 ever become internet routable? It is after all used for the local host. Or am I misunderstanding something here?
- greyface- 2y agoMost deployments only use 127.0.0.1/32. Some niche cases use 127.0.0.0/24. Vanishingly few use more than that. Keep the /24 reserved for local use, and repurpose the rest for global unicast.
- loeg 2y agoMacOS gives the loopback 127.0/8: inet 127.0.0.1 netmask 0xff000000 As does Linux (Fedora): inet 127.0.0.1 netmask 255.0.0.0
- greyface- 2y agoThe whole /8 is "on-net" for the loopback interface, but that doesn't mean it's usable to applications. On macOS, I can't ping or bind to 127.0.0.2, for example. Linux's behavior of allowing the whole /8 to be used, even when only a single address is assigned, is a bit of an oddity here.
- akira2501 2y ago> I can't ping or bind to 127.0.0.2, for example. You can as soon as you define it as an alias. > Linux's behavior of allowing the whole /8 to be used, even when only a single address is assigned, is a bit of an oddity here. Per the RFC: "127.0.0.0/8 - This block is assigned for use as the Internet host loopback address. A datagram sent by a higher level protocol to an address anywhere within this block should loop back inside the host."
- 2y ago
- phildenhoff 2y agoIf an organization ever had the technical control over their network to make 240.0.0.0/4 usable, why would they not use IPv6 instead?
- bell-cot 2y agoAn org with that level of technical control might well be an extremely security-conscious org. And "No IPv6 Anywhere, Ever" would make it somewhat easier to keep things secure.
- phildenhoff 2y agoAh, for the companies with high technical control, but no technical competence! Of course :)
- bell-cot 2y agoIf your #1 goal is to keep the stuff you manage secure, then keeping that stuff as simple as practical is a pretty obvious strategy. If your #1 goal is to keep your 133t bragging rights, then there are no such things as unnecessary nor excessive complexities.
- DaSHacka 2y agoIt would presume its significantly easier to implement routing for a few more blocks of IPv4 addresses than switch the entire underlying infrastructure to IPv6, which requires different infrastructure than IPv4 to work properly (like dealing with SLAAC/DHCPv6 addresses, ICMP, and AAAA addresses)
- deleted 2y ago[deleted]
- loeg 2y ago> Since the internet was at the start not obviously going to be used, the minimum allocation size for an address block was a /8 at the start, later on we got “classful” allocations where a /16 would be assigned instead (this is why you often see /16s assigned to universities or institutions of similar ages), Classful allocation had /8s, /16s, and /24s depending on the numeric prefix (0-127 were /8, 128-191 were /16, and 192-223 were /24). https://en.wikipedia.org/wiki/Classful_network#Classful_addressing_definition https://en.wikipedia.org/wiki/Classful_network#Classful_addr...
- jcalvinowens 2y agoUgh, this is RFC1918 all over again, but worse. IPv6 has none of these problems by design: use it.
- benjojo12 2y ago(blog post author here) No in fact, it is so much worse! I do agree we should use IPv6, The ending of the blog post says as such :) > If we are going to start using address space that might not work for all users, it would be wise to pick the address space that we already have a considerable head start on getting accepted: IPv6.
- jcalvinowens 2y agoI'm yelling at the people doing this shit, not you :) Somehow it is getting more and more common. I stayed at a hotel last year that used 1.0.0.0/24 on its LAN (yes, '1' not '10', I couldn't believe it at first).
- ale42 2y agoThis was very common in the past. People abused 1.0.0.0/24 because it was unused. There was even one of the big ISPs in Italy assigning such addresses for their customers for CGNAT...
- sambazi 2y agodoes this fit in the greater 'enshittification' theme? subpar replacements w/o real alternatives
- schoen 2y agoHi everybody, I'm not connected with this presentation (other than having talked to Ben about it prior to his giving it, and I guess supplying some of the information on software that accepts 240/4) but I am one of the people working on the project that he describes/criticizes. Here is our current proposal. https://www.ietf.org/archive/id/draft-schoen-intarea-unicast-240-06.html https://www.ietf.org/archive/id/draft-schoen-intarea-unicast... People have been reacting to this with different forms of "just do IPv6" for many years. I guess we need an official statement about that somewhere. [Edit: other than these quick thoughts below...!] I personally think IPv6 is great (I was excited about it in the late 1990s when it was standardized, and gave some talks to promote it, and am happy to see it getting deployed and happy to find myself using it sometimes). I hope people will keep working on it and networks and services will keep adopting it. However, people's need for IPv4 address space depends enormously on other people's behavior. IPv6 addresses are not a good substitute for IPv4 addresses when you're providing a public service, if many of your users don't have IPv6. A high fraction of demand for IPv4 address resources appears to come from organizations and networks that already support IPv6, because they need dual-stack support for compatibility with other people. Even though IPv6 adoption has been happening, it's easy to imagine that it's "almost done" where that really doesn't seem to be the case. (This is complicated by having very different statistics in different countries: some countries are now almost all IPv6 traffic, while others have almost no IPv6 -- so people in different parts of the world often have rather different intuitions about it.) We still see enormous economic demand for IPv4 address space and projections that IPv6 adoption to a point where IPv4 would somehow no longer be useful or important is likely still decades away. If that's correct¹, we can still get a benefit from making 240/4 usable because that process can be substantially complete during a time when IPv4 is still extremely important. One thing that Ben (and one of the questioners at the end) argued in his presentation is that even if the adoption of IPv6 is unreliable or erratic, it might be more reliable than useful adoption of 240/4. (This was kind of phrased in the converse direction.) I'll have to think about models of that issue. Edit: We have been sad when seeing how proposals to make 240/4 usable were made in 2008, but not adopted at IETF. Among things that people said in 2008 was that IPv6 would make this irrelevant quickly. That turned out not to be right, but we lost years of opportunity to make 240/4 more useful in the meantime, where billions of devices shipped in the interim could easily have supported it by default. So, we still have the opportunity not to have the same sense of regret in 2035. ¹ I'm also aware that there are other projections here; I recently interviewed a prominent Internet greybeard figure who theorized that Internet infrastructure growth as a whole has slowed so much that IPv4 demand may be satisfied in the future out of gradual conversion of residential ISPs to using primarily carrier-grade NAT for IPv4, and then selling off their number resources. In this account, IPv4 will remain important on the Internet for a long time, but economic demand for addresses will decline because most users won't have native IPv4 at home or on their mobile devices (the latter already the case in many networks). The economic demand for IPv4 resources is something that has made reclaiming 240/4 appear worthwhile, so in this model it would become less exciting, even without having IPv4 "go away".
- ericvanular 2y agoSupposed "developer-first" companies like Stripe & Github not enabling IPv6 access to their APIs is preventing progress
- jiggawatts 2y agoNot to mention public cloud providers dragging their feet on implementing basic IPv6 functionality as if it was some sort of obscure feature instead of… the Internet protocol for the last two decades.
- jeroenhd 2y agoAll the cloud providers I rent services from offer IPv6. It's only the really big ones that seem to be dragging their feet. I suppose the multi-AZ stuff makes things more complicated, but my $5 VPS host had IPv6 like what, ten years ago? This does have one small benefit: since none of the large cloud providers seem to do competent IPv6, you can avoid scanners, scrapers, and other log polluters on personal services by just hosting them on IPv6.
- spacebanana7 2y agoIs anyone aware of why those decisions not to adopt IPv6 were made? Presumably there've been discussions at both companies about it.
- throw0101d 2y ago> Is anyone aware of why those decisions not to adopt IPv6 were made? Because they have all the IPv4 address they need and so do not see a shortage, unlike those that are not mega-corps and are struggling: > I work for a Native American tribe in the PNW. We scrambled to get the reservation reliable internet in the later part of 2019. We managed to cover most of the reservation with wi-max and wifi with a fiber back haul configuration. We are now slowly getting more stable and reliable fiber to the home(FttH) service installed to as many homes as we can, but it is slow process covering the mostly rural landscape doing all the work in house. […] > We learned a very expensive lesson. 71% of the IPv4 traffic we were supporting was from ROKU devices. 9% coming from DishNetwork & DirectTV satellite tuners, 11% from HomeSecurity cameras and systems, and remaining 9% we replaced extremely outdated Point of Sale(POS) equipment. So we cut ROKU some slack three years ago by spending a little over $300k just to support their devices. * https://community.roku.com/t5/Features-settings-updates/It-s-2022-and-still-no-IPv6/m-p/854673/highlight/true#M35732 https://community.roku.com/t5/Features-settings-updates/It-s... * https://news.ycombinator.com/item?id=35047624 https://news.ycombinator.com/item?id=35047624 Anyone who (a) got in early on the IPv4 address land grab, or (b) has buckets of cash, can 'safely' ignore IPv6.
- inopinatus 2y agoTo this day I maintain that a large part of IPv4 space wastage is due to the HTTP WG's longtime avoidance of adopting SRV or SRV-like DNS records or even the DNS itself as normative for HTTP/HTTPS, instead allowing the HTTP RFCs to just vaguely suggest that DNS might be one way to resolve the IP address of origin servers, whilst in practice squatting on the A (address) record like they owned it (and worse, all the apex records). Consequently inspiring a vast chorus of LIRs applying for /19 allocations over the years "for SSL hosting" and continuing to do so long past the introduction of SNI (RFC 3546). Saw this behaviour firsthand as a European LIR operator with friends at RIPE. Is it cracked down on now? Yes. Are there whole swathes of IPv4 space that remain unassigned or entirely unannounced? Yes. Does every large-scale DNS hosting service have some hackish way to workaround the prohibition of CNAME records at the zone apex? They sure do, and HTTP is why. Paul Vixie saw it coming, the very first example in the original SRV proposal (RFC 2052, 1996) is resolution of HTTP. Alas that this example was omitted in later editions. The new SVCB/HTTPS RRs (RFC 9460, 2024) are literally decades overdue.
- BeefySwain 2y agoI am trying to parse what this means, can someone ELI5?
- inopinatus 2y agoTLDR For years a combination of gaps in policy, disjointed standards development, hoarding behaviour, and administrative laxity, led to substantial wastage of IPv4 address space that persists to this day, in part because multiple independent website tenants sharing an IP address was (and often still is) difficult. Glossary DNS: Domain Name System, how computers discover (or resolve) each other's numeric IP addresses from symbolic hierarchical names. HTTP WG: HTTP Working Group, the standards committee(s) responsible for defining the application-layer protocols by which a web browser talks to a web server. Under the auspices of the IETF. IETF: Internet Engineering Task Force, the standards organization for the Internet. Most famous for being the entity that publishes TCP/IP and the cherries on top. LIR: Local Internet Registry, an entity that applies to be the holder of block-allocated IP address space. Typically ISPs and hosting companies that assign it for their use or onward customer use. RIPE: The European peak body, a Regional Internet Registry (RIR), responsible for (amongst many other things) allocating IP space to the LIRs, ultimately under license from the global steward IANA. Sibling of ARIN, LACNIC, AFRINIC, APNIC (North & South America, Africa, Asia-Pacific respectively). SNI: Server Name Identification. Before SNI was introduced to SSL/TLS, the only way to tell which HTTPS origin was being requested, was by server IP address. SRV: A specific type of record in the DNS that allows lookup of a service (e.g. IMAP mail, XMPP messaging, LDAP directories) for a given domain name, to return a set of hostname(s) that actually provide that service, and the ports on which it is available. This enables multi-tenant services on shared IP addresses and thereby conserves IP space. /19 network prefix: A large chunk of IPv4 address space, corresponding to 8192 unique IPv4 addresses. Refers to the first 19 bits of the block of (32 bit) IPv4 addresses being allocated. Back in the 90s a /19 was a common granularity of allocation from RIR to LIR and could be granted with a low bar to justification. Mathematically, 2^(32-19) = 8192. Address record: A specific type of record in the DNS that maps a hostname to an IP address. Technically referred to as an "A record" for IPv4 addresses, or an "AAAA" record for IPv6 addresses which are literally 4x the binary length. Allocation, Assignment, and Announcement: IP address space is allocated in blocks by RIRs to LIRs, who then assign smaller parcels of it to specific purposes such as retail hosting and internet access, and announce it at internet exchanges and to their peers for actual traffic exchange. Very often, the quantity of assignment failed to justify a large allocation, leaving space unassigned i.e. unused, and in some cases unannounced, but still hoarded, with incentives for hoarding becoming perversely stronger as the addresses ran out and the policy screws started to tighten ca.2005-2011. Apex: in "example.com" it is the "example.com" rather than "www.example.com". For marketing purposes, almost every entity wants their zone apex to be directly reachable as a website, which means placing an address record at the apex. This excludes using the apex address record for any other service but HTTP, which I have always regarded as downright antisocial. Since alias records (a.k.a CNAME records) aren't permitted at the apex, it also makes DNS management harder when you have frequent changes to make, as in the highly dynamic world of cloud-based services, or even just want to point your website at a third party hosting service without having to edit your zones whenever their IP addresses change. Normative: A formal declaration in one technical standard (e.g. SMTP) that it depends in whole or in part on another standard (e.g. DNS) for full specification. It is unusual for a TCP/IP-based IETF protocol standard to omit DNS as normative or otherwise specify how they use the DNS for discovery, but HTTP has always been super vague about it. Origin: Fancy word for your actual website. Or in the presence of complications like reverse proxies/load balancers/CDNs etc, the front of your service stack from the point of view of a web browser.
- teddyh 2y agoIf this proposal is accepted, it will make it less likely that people will simply continue to steal random unoccupied and/or unimportant ranges of addresses and reuse them for their own purposes, which in turn would make IPv4 interconnectivity more and more uncertain, which would probably drive IPv6 adoption… Hey, wait a minute… I’m suddenly not convinced this is a good idea in the long run.
- znpy 2y agoFor f..k's sake can't we switch to ipv6 already? Let's just put ipv4 on life support, reclaiming 240.0.0.0/4 is a bad idea.
- SirMaster 2y agoI was surprised to find that back when I went to college, every computer connected to their network, whether it be the laptops that each student had via the required technology package, and even personal desktop computers and gaming consoles and every device connected to the network in the dorms, every machine was given a public facing IP address without NAT. Even your phone or tablet on the campus wifi got a unique public IP... Of course there were firewalls in place and all the incoming ports were blocked, but doesn't that seem like a big waste of IPs? The university owns 155.92.0.0/16 and every machine on the network gets a 155.92.x.x IP address. https://ipinfo.io/AS11500/155.92.0.0/16 https://ipinfo.io/AS11500/155.92.0.0/16 Is this normal? Or shouldn't the IPs all be NAT'd behind a few public IPs?
- stouset 2y agoIf you own the public IPs, why not use them?
- SirMaster 2y agoSure, but should a school even be given all those IPs to be used like that? Seems like a waste to me to have it where every device on the campus network gets a public IP, like every students phone, laptop, tablet, desktop, game console, etc.
- stouset 2y agoToday, absolutely not. But the damage was done back when those ranges were doled out. That said at this point I kind of half-seriously prefer keeping the IPv4 space as exhausted as possible if it’ll even slightly drive adoption of IPv6.
- teddyh 2y agoWhy should every individual person have their own physical mailing address? Couldn’t they just get their paper mail at their workplace? Or is it a vital component of democracy and individual freedom that people can recieve mail and other missives independent of their workplace’s curious eyes and sufferance? Or voting. Should really everybody get a vote? Most people don’t really need to vote. This is evidenced by the huge numbers of people who don’t vote. And most people who do vote do it badly, anyway. /s
- deleted 2y ago[deleted]