

I like that none of my local devices are externally addressable unless an outgoing connection has been established.
This can also be achieved using (other) firewall rules.
but then it’s essentially just maintaining a NAT table without the translation piece.
So… a firewall?
NAT isn’t a security feature and shouldn’t be relied on for managing access to hosts.
It also breaks the assumption of IP that connections between hosts are end-to-end, which requires sophisticated solutions so that everything works (more or less).
I too employ NAT to make services accessible over IPv4. But only because it doesn’t work otherwise. Not because it “makes sense”. I don’t use it at all for IPv6.
Oh, this looks really interesting. You only need dedicated CPU cores, but the rest of the hardware can be shared? Better performance than VMs, including Xen? Still some security benefits due to the isolation between kernels? “zero-down kernel update”?
This reads phenomenal, even though I understand it’s just RFC at this point. Let’s see what comes out of it…