RE: please comment on global identifiers proposal

["Tom Lehman" <tlehman@xxxxxxxxxxxx>]

Ronald,

I do think we need to be more precise in Section 4 regarding the format of
the Global ID.  

So editing slightly what you presented below, how about this:

--------------------
"Sourcing organisation" should generate a global identifier by:

i)setting the first part of the global identifier to the identifier of that
organisation; the organisation picks an id as long as it is globally unique.

ii)it sets the second part of the global identifier to some internally
unique naming scheme

iii)the first and second part are separated by a colon ":". There should be
only one ":" in the entire Global ID.

v)The format of the global and local parts of the ID are determined by the
originator, with the following restrictions:  The form is a text string up
to 63 characters drawn from the alphabet (A-Z), digits (0-9), minus sign
(-), and period (.).  No blank or space characters are permitted as part of
a name. No distinction is made between upper and lower case. 
--------------------

In iii above, I changed the delimiter to be ":" instead of "-" because, iv
allows "-" as part of the name.

the description in v is basically the requirements for the dns hostnames as
defined in rfc 952,1123 (snippets below).  minus the restriction on the use
of periods(.)

So with this scheme, the current GOLE names on the GLIF web site work.  And
someone like DRAGON-MAX could use DRAGONMAX:5702 or
dragon.maxgigapop.net:5702, as they wish (with 5702 being the local part)

What do you think about this?

Tom


RFC 952
1. A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24
characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and
period (.).  Note that periods are only allowed when they serve to delimit
components of "domain style names". (See RFC-921, "Domain Name System
Implementation Schedule", for background).  No blank or space characters are
permitted as part of a name. No distinction is made between upper and lower
case.  The first character must be an alpha character.  The last character
must not be a minus sign or period. 

RFC 1123
The syntax of a legal Internet host name was specified in RFC-952 [DNS:4].
One aspect of host name syntax is hereby changed: the restriction on the
first character is relaxed to allow either a letter or a digit.  Host
software MUST support this more liberal syntax. Host software MUST handle
host names of up to 63 characters and SHOULD handle host names of up to 255
characters.


> -----Original Message-----
> From: Ronald van der Pol [mailto:Ronald.vanderPol@xxxxxxxx] 
> Sent: Wednesday, August 06, 2008 9:44 AM
> To: Tom Lehman
> Cc: global-id@xxxxxxx
> Subject: Re: [global-id] please comment on global identifiers proposal
> 
> On Tue, Aug 05, 2008 at 13:01:44 -0400, Tom Lehman wrote:
> 
> > Ronald, All,
> > 
> > I have one question, hopefully a clarification.  
> > 
> > With the recommendation in section 4 to use the Sourcing 
> GOLE Naming Scheme,
> > the list of globablly unique GOLE names are as listed on 
> the GLIF web site.
> > 
> > 
> > My assumption is that if a circuit starts on a network 
> which is not in that
> > GOLE list, then the global id will still be based on the 
> sourcing domain
> > name.
> > 
> > For instance if we have circuit which has the following path:
> > 
> > Internet2DCN-MANLAN-NETHERLIGHT
> > 
> > Is it ok to use a name for instance:
> > 
> > dcn.internet2.edu-5705
> > 
> > since that represents the source domain?  
> > 
> > If so, I think we need to include in the recommendation, 
> something to the
> > effect:
> > 
> > "if the source domain is not in the GOLE name list, then 
> globably unique
> > names can be formulated by using the sourcing domain dns 
> name information,
> > as described in Section 3.2 for instance."
> > 
> > or should we just add the name "dcn.internet2.edu" to the 
> list of GOLES
> > listed on the GLIF web site?
> > 
> > Tom
> 
> Thanks for your reply.
> 
> This is something we need to discuss and get consensus about.
> 
> I was thinking that the first part is always a GOLE id.
> 
> Currently, many lightpath requests are still done by end-users by
> sending emails to dozens of people and organisations. I think the
> GLIF community would like end that practise and professionalise by
> adopting the "sourcing organisation" setup procedure as mentioned
> in the document:
> http://www.glif.is/working-groups/tech/fault-resolution-0.9.pdf
> I think this was decided at the interim meeting in Minneapolis.
> 
> Then the question becomes "who or what are the sourcing 
> organisations".
> I think I agree that it is more than just the GOLEs. It most probably
> are also the NRENs like Internet2, Canarie, SURFnet, etc.
> 
> So, are we saying that the "sourcing organisation" should generate
> a global identifier by:
> - setting the first part of the global identifier to the identifier
>   of that organisation; the organisation picks an id as long as it is
>   globally unique.
> - it sets the second part of the global identifier to some internally
>   unique naming scheme
> - the first and second part are separated by a hyphen.
> 
> Should we restict the global identifiers to alpha-numerics plus the
> hyphen and have them case insensitive? This means "dcn.internet2.edu"
> is not a valid string.
> 
> Do we allow multiple hypens in a global identifier? That would mean
> that it is not possible to distinguish between first and second part
> by just looking "left" and "right" of the hypen.
> 
> In your example could the global ID be something like:
> INTERNET2-XXXXXX
> or
> INTERNET2DCN-XXXX
> where XXXXXX is the second (local) part?
> 
> 	rvdp
>