Lars,
"Revisitation" means being able to support larger virtual
topologies than you have physical resources for, e.g., deploying a
100-node ring on ten machines in a lab. This is done by hosting
multiple virtual nodes on a single physical node. (You "revisit" a
physical node multiple times for one overlay - the term may not be
perfect.)
Many existing systems that deploy virtual networks can only deploy
virtual nets that are at most as large as the underlying physical
resources, i.e., they can arrange a subset of the physical nodes
into arbitrary topologies by creating tunnels, but they cannot
create virtual topologies that have more nodes than available
physical machines.
So far I think I understand.
Revisitation is similar to VM, in the sense that both enable the
creation of virtual resources of apparently larger capacity than
the underlying physical resource. This more completely decouples
the two, increasing the power of the virtual abstraction. AFAIK the
X-Bone is still the only virtual nets architecture that support this.
Hmmm. Are you trying to say that since we have so few real IP
addresses available, we need this kind of virtualisation to give more
IP addresses per host? If so, I don't understand why? What do you
need that many IP addresses for each host?
(A different aspect of this decoupling between physical and virtual
resource would be replication of a single virtual node onto
multiple physical machines for fault tolerance. This isn't in X-
Bone yet, AFAIK.)
I still completely fail to see the utility value of this for anything
else but emulation kind of work. Or are you trying to split the two
roles of IP addresses by creating a layer of indirection within IP,
using virtual addresses as identifiers and physical addresses as
locators?
--Pekka
_______________________________________________
Int-area mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/int-area
