Re: proposal for the introduction of Global Identifiers for lightpaths

[Mathieu Lemay <mlemay@xxxxxxxxxx>]

Hi Ronald! :P

I have question about the URN naming scheme.. why is it limited to URN and not URIs? I just wanted to comment that it's fine for management purposes but simply what to make the distinction about the "Endpoint" definition in applications.

I find that scheme and host location to be important. When using URIs you simply have
URN as the scheme when doing management display or transient service (Resource ID), however it is inadequate to access directly the resource...

What that means is that the same resource may have the following access mecanisms in different contexts:

1) urn:glif:northernlight:G6O76GQ 
- Here this kind of ID are useful when looking at "indices" in a resource repository. However it gives the application no idea on HOW /WHERE this resource can be accessed. So this cannot be a service / resource endpoint but can be part of the datamodels.

2) x-jms://northernlight:xxxx/resources/lightpaths/glif/northernlight/G6O76GQ
- This would be the equivalent "routing" for messages going through JMS for the same resource.

3) http://www.northernlightserver.com/resources/lightpaths/glif/northernlight/G6O76GQ
- This would be the RESTful address to this resource or could also stand as the WS-Addressing Endpoint for SOAP services...

Notice that URIs can also have fragments thus:

http://www.northernlightserver.com/resources/opticalswitch/glif/canarie/ome-ott01#CardX

Regards,
Mathieu

----- Original Message -----
From: "Ronald van der Pol" <rvdp@xxxxxxx>
To: all@xxxxxxx
Sent: Friday, August 22, 2008 10:22:59 AM (GMT-0500) America/New_York
Subject: [GLIF all] proposal for the introduction of Global Identifiers for lightpaths

All,

During the Tech WG meeting in Honolulu in January a Task Force for
Global Identifiers for lightpaths was setup. The task force was
asked to make a proposal for a naming scheme for lightpaths.

Attached is the proposal of the task force. This proposal will be
presented at the GLIF meeting in Seattle in October. But we like
to get feedback from the community before the meeting. We hope
to reach a decision in Seattle because the operational need for
global identifiers for lightpaths is high. For outages and
announcements of planned work we need a way to uniquely identify
the lightpath(s) we are talking about.

Please give us your feedback.

	Global Identifiers Task Force