926 karma · joined March 31, 2013
The inverse situation (IPv6-only client but IPv4-only server) is not really an issue, since for that situation NAT64 works, since you can embed IPv4 addresses into IPv6.
The only way C (ipv4-only) could communicate with S (ipv6-only) is by either allocating a dedicated ipv4-address to S (doesn't have to be directly connected to S - it can be sent to some translation box that does SIIT) or by upgrading C to support ipv6 and tunneling it (6to4, 6rd, teredo, etc.).
A typical ISP will get allocated a much larger allocation like a /20, which allows them to allocate a /56 for each of their customers while still having a few bits to play with. But all starting with the same <isp_network> prefix.
With IPv4 you will have many separate fragmented networks that have no numbers in common. And this will only get worse over time.
It may sound like a great plan as long as one doesn't look too closely at the details. IPv4 has fixed 32-bit addresses and one cannot cram more than 32-bit of information into a fixed 32-bit field. But one would need to do that for it to be forward compatible, since how would a IPv4-only client open communications with a expanded address space server?
One idea is to only upgrade the client and server and tunnel the expanded address space packets over IPv4. IPv6 has that - that's how it was bootstrapped before native IPv6 connectivity was a thing.
Also having 64-bit for the network address (and 64-bit for the device) does have certain benefits that make it easier to use than shorter addresses in practice for a single entity, since one can hierarchically model the network and do things like <my_network>:<site-id>:<vlan>. So even in absence of DNS one doesn't quite have to remember 128-bit of information for every device.
Most of the other criticism is not relevant anymore, since we now have a lot of transition technologies that allow IPv6 clients to interoperate with IPv4 servers (this way around is possible since IPv6 is a superset of IPv4). Overall we are now much further into the IPv6 migration than djb ever envisioned.
IPv6 is as backward compatible as is possible within this constraint. You can embed IPv4 space within IPv6, there is NAT64, tunneling IPv6 over IPv4 and many other transition technologies. It's not possible to design a protocol that is any more backwards-compatible.
[1] https://wiki.gnome.org/Apps/Polari [2] https://thelounge.chat/
Starlink doesn't have nice overview of actual specs of future satellites, so I can only use what people have figured out or what they have published. But you are right about the number of satellites, I looked at the wrong column (it was for phase 1 and not 3), so density will indeed be much higher, so from that perspective it will be somewhat more capable (depending on fast/slow their rollout is). And it's not clear if it would actually be cheaper for SpaceX to have such customers (since some of the traffic would go to the rest of the internet - requiring ground station resources) or go elsewhere on the planet (filling up inter-satellite capacity), but that's not too much different from how regular ISPs have to plan (some customers are cheaper for them than others).
For it to be really viable as a backbone it would need to be able to do several 100 Gbit/s from one location and that Starlink cannot do (or is built to do). A single satellite has less than 100Gbit/s of RF capacity and you will only have a couple visible above you at any one time. And after that bottleneck comes the inter-satellite link capacity bottleneck which is less than half of that if the information I have found is correct (4 links à 10Gbit/s). I don't think they will be able to sell more than 10 GBit/s service to anyone and that only in not so populated areas.
A single datacenter can reach low Tbit/s of connectivity _alone_ _today_. I don't see how it could make any dent whatsoever in the backbone market.
The other usecases are a different discussion and not as dependent on very high bandwidth numbers.
And nevermind that Starlink will run out of ground station / inter-satellite link capacity long before reaching the theoretical maximum.
And if any downtime for upgrades is unacceptable one can go for distributed storage solutions like ceph, seaweedfs or minio. Or simply 1:1 mirror everything to a second machine (which you want for disaster recovery anyway) and switch over during the maintenance period. And since for this specific usecase the server(s) would only serve as CDN origin, a brief downtime might even have very little actual impact.
For applications a subset of the IPv6 address space is set aside for IPv4 connections. So applications only need to support IPv6 and can communicate with IPv4 destinations using ::ffff:<ipv4-address>, so for example ::ffff:8.8.8.8 is a valid ipv6 address. But that still requires the host to have a IPv4 address for this to work (it's only so applications can support both while only requiring support for one address family).
For IPv6 hosts connecting to IPv4 hosts there are different methods that translate IPv6 to IPv4 (NAT64, SIIT, etc.), but most (if not all) just embed the whole IPv4 address space inside IPv6 (and again you can have something like 2001:db8::8.8.8.8) and then translate based on extracting the IPv4 address from the IPv6 address. And in combination with DNS64 you can have ipv6-only hosts that can communicate just fine with IPv4-only hosts (all ipv4 traffic gets routed via NAT64).
The problem is however the inverse. IPv4 is not forward-compatible. A IPv4-only host can only ever form outgoing connections to other IPv4 hosts, since there is no way to put more than 32-bits of information into the 32-bit destination field of the IPv4-packet. You can of course expose certain ipv6-only hosts to the ipv4-internet using for example SIIT, but that requires a 1:1 mapping between the IPv4 and IPv6 host. If you don't have that explicit mapping, how would a gateway know which IPv6 address you meant?
Only way around that is sniffing the communication (say some cloud service that some IoT device connects to) - which would also give you enough information to send your own packets through the NAT/firewall too. Not very feasible for the average attacker and assumes that the device initiates connections in the first place. If it doesn't, good luck finding it remotely.
Because that's what's required to make it fully interoperable. Anything else and it's not a pure IPv4 network anymore and you are in the exact same situation as we are with IPv6.
Did they though? Looking at the gas futures chart it's not obvious to me at all. The prices suddenly spiked much higher when NS1 was suddenly shutdown. After the explosion they actually went down slightly. They did profit, but just from the actions from the Russian side (which were earlier in time).
As for whatever you mean with competitor coming online. Towards Germany the flows from Norway didn't change that much after the invasion, Europipe II from Norway to Germany was already maxed out since January 2021 pretty much.
My personal belief is that we will never know who actually performed the acts of sabotage. But taking some Biden soundbites, mixing it with some public information and some hand-waving doesn't produce any actual evidence about who actually did it.
And the rest is all putting the cart in front of the horse. Would it look any different if Russia (or anyone else) were the culprit? No, it wouldn't (since otherwise the fact it's classified itself leaks information). Maybe the investigation just yielded nothing conclusive? Which given the location and event (big explosion and lots of gas output making sure everything gets nicely distributed elsewhere) wouldn't be that surprising?
In addition the bad-trigger scenario would imply that the explosives and triggering mechanism remained in place on the remaining pipe, which would require the US to rush there to remove them or trigger the missing one to avoid terrible diplomatic consequences if the unexploded device were to be discovered.
[1] https://www.theguardian.com/commentisfree/2014/may/20/why-di...
But given that and that Poland initially agreed to the delivery and only afterwards started changing their tune, I don't think the PR angle is that far-fetched?