perfsonar development work

[Loukik Kudarimoti <>]

Sorry for the delay in response Roman.

Because the protocol is agreed with JRA4 guys, I would like the SQL MA 
to *definitely accept the current value* (i.e. make no changes) but 
ideally accept both (the old as well as the new) so that transition for 
clients becomes easy.

However, from release management point of view, when we stop supporting 
the old eventType value, we will probably have to think about bumping up 
the perfSONAR bundle version number.

Loukik.
ps: I prefer: http://ggf.org/ns/nmwg/topology/l2/3.0/link/status


Roman Lapacz wrote:
> Roman Lapacz wrote:
> > Question to people who are working on L2 path status stuff:  what 
> > eventType do you want to have? Seeing metadata configuration I would 
> > take http://ggf.org/ns/nmwg/topology/l2/3.0/link.
>
> Hi,
>
> So far I've got no responses to this mail. Does it mean that we want 
> to keep (in SQL MA) 'Path.Status' value for eventType element? If yes 
> then it does not follow naming rules we agreed on recently.
>
>
> what about :
>
>  http://ggf.org/ns/nmwg/topology/l2/3.0/path/status
> or  http://ggf.org/ns/nmwg/topology/l2/3.0/link/status
> or
>  http://ggf.org/ns/nmwg/characteristic/path.status/2.0
>
>
> (in case of no responses I assume that we want to keep 'Path.Status' :)

> Roman