This[0] change is interesting for home deployments of IPv6: If your ISP changes advertised prefixes occasionally (which mine does), it was until now not practical to assign/use addresses with fixed host suffixes, e.g. for internal services, because you couldn't write firewall rules using those addresses (part of the address could just change and there's no automatic update of the rules).
The change now enables you to write firewall rules that use a placeholder for the ISP-assigned prefix. The rules should update automatically after a prefix change.
(What has always worked is using the fc00 or fd00 address spaces for local fixed assignments, but pfSense has had problems with that setup as well in my experience)
All the passport categories you quoted (BOTC, BOC, BPP, BS) relate to former colonies (think the status given to inhabitants of Hong Kong after it was turned over to China).
Sadly, depending on the ISP, the prefix is not necessarily static and may change on reconnect (for example, Deutsche Telekom will only keep the prefix static for business accounts). This is completely arbitrary and makes relying on GUAs for internal addresses problematic.
It’s too bad that we are inheriting the static IP policies from IPv4, because ISPs want to upsell.
VMS isn’t an IBM mainframe OS, though. I think typical native VMS machines are much closer to normal enterprise servers than mainframes, so virtualization would make sense.
Right, it’s a great system! Concerning envelopes, here in Germany most mail I get is in DL envelopes, which also require the double fold. C5 is mostly used if double folding doesn’t work due to thickness.
https://github.com/optics-dev/Monocle