Global ID variants

[Ronald van der Pol <Ronald.vanderPol@xxxxxxxx>]

After today's discussion we seem to have a couple of proposals:

urn:glif:<domain>:<local>
urn:ogf:network:<domain>:<local>
urn:ogf:network:domain=<domain>:key1=<value1>:key2=<value2>:...:<local>
urn:ogf:network:<domain>:localkey1=<localvalue1>:...

question:
Do we want a scheme were a lightpath can have multiple globally unique IDs?
This would be the case where these are IDs for the same lightpath:
urn:ogf:network:domain=<domain>:key1=<value1>:key2=<value2>:...:<local>
urn:ogf:network:key2=<value2>:...:key1=<value1>:domain=<domain>:<local>
urn:ogf:network:key2=<value2>:domain=<domain>:...:key1=<value1>:<local>

I don't like this. This won't work in real life. Imagine trouble
tickets with a list of effected lightpaths. You would need to do a
difficult parsing of each name before you know it is one of your
lightpaths.

question:
Should we (GOLE operators) start using a simplified form of naming asap
in trouble tickets? We could start using <domain>:<local> now in trouble
tickets. When we need it in a web services context we can stick a urn
in front of it. We can decide on a urn later.

I think we should start with this because we need global identifiers in
operations now.

	rvdp

Attachment: signature.asc
Description: Digital signature