[gin-auth] Agreement on VO naming convention ?
Dane Skow
skow at mcs.anl.gov
Wed May 10 04:50:32 CDT 2006
Am I correct in reporting that we reached consensus on the VO Naming
convention below (at least as our first round attempt) ? Looks that
way to me reviewing the list (thread from mid March), but I'd like to
double check before claiming so publicly.
> VO Naming
> ---------
> The VO name is a string, used to represent the VO in all interactions
> with grid software, such as in expressions of policy and access
> rights.
>
> The VO name MUST be formatted as a subdomain name as specified in
> RFC 1034 section 3.5. The VO Manager of a VO using a thus-
> formatted name
> MUST be entitled to the use of this name, when interpreted as a
> name in the Internet Domain Name System.
> This entitlement MUST stem either from a direct delegation of the
> corresponding name in the Domain Name System by an accredited
> registrar for
> the next-higher level subdomain, or from a direct delegation of the
> equivalent name in the Domain Name System by ICANN, or from the
> consent
> of the administrative or operational contact of the next-higher
> equivalent
> subdomain name for that VO name that itself is registered with such an
> accredited registrar.
>
> Considering that RFC1034 section 3.5 states that both upper case
> and lower
> case letters are allowed, but no significance is to be attached to
> the case,
> but that today the software handling VO names may still be case
> sensisitive,
> all VO names MUST be entirely in lower case.
Cheers,
Dane
More information about the gin-auth
mailing list