192 karma · joined July 6, 2010
Versatile Commodore Emulator (VICE) dev team
david.q.hogan@gmail.com https://www.linkedin.com/in/davidqhogan/
It’s a chicken and egg problem. It would have been nice if everybody everywhere agreed to build and use an entirely new network at the same time, but that was never going to be practical.
The actual problem at hand was lack of address space, and I think this could have been addressed with a more viable upgrade path - turn every IP4 address into x number of addresses behind it, and allow retail ISPs to remain IP4 only.
I don't agree that it wouldn't have been easier to migrate. No changes would have been needed within retail ISPs for starters. Source code changes to existing IP4 stacks would have been minimal, without requiring a whole new stack like IP6. Practical migration requires only that the source and destination networks be IP4.4 aware.
The idea might make less and less sense over time, but if we'd done this 20 years ago we would have reliably had all the address space we needed 10 years ago, no further transition necessary. So much money spent on IP6 could have been saved, not to mention the opportunity cost of IP4 space being hard to get in recent years.
I think that's what TTL is for. Without it, it would be entirely possible to have infinite loops between IP4 networks.
Just on that point, it’s also worth considering what happens when hospitals are overwhelmed.
1. Include an extra 32-bits of address information as an IP options header. Call it an IP4.4 packet.
2. (I think?) IP4.4 packets would therefore happily travel over existing IP4 infrastructure.
3. Each existing IP4 address becomes a potential IP4.4 network with 32-bits of address space behind it.
IP4.4 aware routers at the network border could swap inbound IP4 destination with the .4 address before forwarding on to the internal network. Basically like NAT, but you can allow inbound connections without maintaining state.
EDIT: formatting
Unfortunately our government advice appears to be that we should comply if we "offer goods and services in the EU", or "monitor the behaviour of individuals in the EU.": https://www.oaic.gov.au/privacy/guidance-and-advice/australi...
I have no idea what would actually happen if they decided to fine an Australian entity.
What worries me is that it’s still early days for enforcement, but they’ve already handed out something like US$1.6B in fines. I assume they will only get more aggressive with this over time.
We could use some further optimisation in the emulated screen rendering code in VICE, particularly on ARM.
I think the problem is long-term co-operation rather than planning. The temptation of short-term gain is always too great for someone.