[gin-info] Site UniqueID

[JP Navarro]

Laurence,

I think using the domain name for UniqueID makes a lot of sense.

Grids and most organizations are hierarchical, so I think would also be
helpful to suggest that the root elements of a UniqueID must be  
registered
domain names, but that higher level element don't have to be.

Example UniqueID: dtf.uc.teragrid.org

teragrid.org is registered
uc.teragrid.org isn't registered but hosts do use that domain
dtf.uc.teragrid.org is the name of a cluster, but the name doesn't  
resolve to an IP address

This should be a valid UniqueID. The registered teragrid.org ensures  
no global
conflicts. The teragrid.org organization should coordinate how to  
manage UniqueID space
under teragrid.org with no constraints on the number of levels,  
domain registration,
or IP resolution.

Does that make sense?

JP

On Oct 26, 2006, at 5:18 AM, Laurence Field wrote:

> We have shown that for the "grid-on-a-map" use case we MUST have the
> following attributes
>
> UniqueID:
> Latitude:
> Longitude:
> Location:
>
> SHOULD have the following attributes.
>
> Name:
> Description:
> Email:
> Web:
>
> and CAN have optional tagging attributes.
>
> On question that remains is what should be the format of the UniqueID.
> This is important as when we have interoperating grids, the rules to
> chose this UniqueID in the different grid might not be the same and
> hence this could case a clash.  This is a similar problem to the VO
> naming issue which came up in the gin-auth group.  In the past a
> suggestion was made that this should be the domain name of the site.
> What are peoples views on this? Do they think that this is a good idea
> or can anyone suggest a better alternative?
>
> Laurence
>
> --
>   gin-info mailing list
>   gin-info at ogf.org
>   http://www.ogf.org/mailman/listinfo/gin-info
>