Identifier locator addressing

Posted Sep 12, 2015 21:07 UTC (Sat) by kleptog (subscriber, #1183)
Parent article: Identifier locator addressing

This is a really awesome idea. Next step would be to give each (Docker) container a 64-bit identifier and you can use this to provide all the virtual networking you need to be able to migrate containers between hosts.

Though it will take a little while to get this version of the kernel deployed wide enough to be able to rely on it...

Identifier locator addressing

Posted Nov 2, 2015 18:58 UTC (Mon) by jcm (subscriber, #18262) [Link] (1 responses)

Now that's a smart idea

Identifier locator addressing

Posted Nov 2, 2015 23:43 UTC (Mon) by Lennie (subscriber, #49641) [Link]

It's such an obvious use case the draft mentions containers only 5 times. ;-)

Also mentions: virtual machines aren't the obvious use case.

Anyway, I need to find some time and read all of it.

It seems to me:
- it's similar to DNS name which points to an IP-address. I wonder if it can point to multiple IP-addresses.

- it's also similar to DNS because it looks like a central service can be used to answers queries about it.

- it's not similar to using routing on every host.

- it's more useful than DNS because you can keep connections open when migrating processes from one machine to an other.

- assume it's not tied to layer 2 and works across layer 2 domains.

But hey, I still need to read it properly. So maybe I'm wrong.