I'm sorry for not paying attention for a while, Tony, but I think we can improve on the wording by reducing it.

On 4/8/09 5:52 AM, Tony Li wrote:

Hi all,

As the conversation has died down, I'm going to guess that we've converged. The consensus check can be found here: http://doodle.com/9sybb8dmk5phvp99

Please vote for or against these definitions:

locator    A locator is a name for a point of attachment within the
       topology at a given layer.  Objects that change their point
       of attachment(s) will need to change their associated
       locator(s).  By default, a locator refers to layer 3.  It
       is also possible to have locators at other layers.
       Locators may have other properties, such as their scope
       (local or global (default)) and their lifetime (ephemeral
       or permanent (default)).

I propose generic definitions and then applying them in specific cases. Hence...

A locator is a value or string that specifies location of an object within a physical or logical topology.


identifier An identifier is the name of an object at a given layer;
       identifiers have no topological sensitivity, and do not
       have to change, even if the object changes its point(s) of
       attachment within the network topology.  Identifiers may
       have other properties, such as the scope of their
       uniqueness (local or global (default)), the probability of
       their uniqueness (statistical or absolute (default)), and
       their lifetime (ephemeral or permanent (default)).

An identifier is a value or string that references a specific object or group of objects.


The discussion of lifetime is relevant in the context of binding an identity to various properties. Some properties are permanent, and some are ephemeral. I will probably always have the same blood type, but my location changes. In the case of a host, its name may stay the same, perhaps even its distinguished name, but its private and public keys may or may not change, even when its address does change.

In this discussion please keep in mind both host names and how GSLBs tend to work.

Eliot
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg

Reply via email to