Fred Baker allegedly wrote on 06/11/2010 01:02 GMT+02:00: > This one gives me some pause in the context of a virtual machine in a > cloud computing environment. I rather like the idea of associating > identifiers with an application or set of applications, and only by > extension of that referring to physical or virtual machines. For > example, in cloud environments, if a process or set of processes > moves from one machine (physical or virtual) to another, it would be > nice to be able to move all of its/their sessions with it/them.
Fred, you're right, I hadn't noticed that. Identifiers are used in many ways, particularly for different session instantiations. The definition here has a particular scope, and the scope should be explicitly stated. swb > > On Jun 11, 2010, at 6:18 AM, RJ Atkinson wrote: > >> D) An "Identifier" is a topology-independent name for a logical >> node. Depending upon instantiation, a "logical node" might be a >> single physical device, a cluster of devices acting as a single >> node, or a single virtual partition of a single physical device. >> An OSI End System Identifier (ESID) is an example of an identifier. >> A Fully-Qualified Domain Name that precisely names one logical node >> is another example. (Note well that not all FQDNs meet this >> definition.) _______________________________________________ rrg mailing list rrg@irtf.org http://www.irtf.org/mailman/listinfo/rrg
