Salting Type-1 UUIDs in a virtualized network
Publication Date: 2014-Mar-21
The IP.com Prior Art Database
Disclosed is a method of salting type-1 UUIDs in a virtualized network.
Page 01 of 1
Salting Type -
A hypervisor is designed so that every 6-byte media access control (MAC) address it assigns to a virtual host always contains some number of reserved (zero) bits at established offsets in the generated MAC address. The cooperating virtual host may then selectively set these reserved bits to qualify universally unique identifier (UUID) values it creates using the well-established type-1 UUID method. This provides the virtual host with a configurable partitioning of (seeming generic) 16-byte UUIDs. In a simple embodiment, the generated MAC addresses would always end with some number of zero bits, but in principle, these reserved bits could be located anywhere in the low-order three bytes of the MAC, as long as the virtual host componentry taking advantage of this idea knows which ones they are.
A type-1 UUID is a 16-byte value that is typically used as an opaque "key" into a related data store. It is usually represented to the user as a string value that decodes the 16 bytes of the UUID into 32 dash-delimited, lower-case hexadecimal digits (i.e., "95c4e2d8-3c00-11e3-9272-020000000001"). Notably, the least significant 6 bytes of the type-1 UUID contain the MAC address of the host system where the UUID was created.
Beyond the identification of the creating hosts' MAC address, other attempts to characterize (or group) UUID-referenced objects -- based solely on their type-1 UUID -- is inherently an "unsupported" operation. For that reason, nearly every use of a UUID -- even the simplest grouping operation or type-specific selection operation -- involves the comparatively expensive operation of look...