Hi, On 5 Dec 2012, at 18:24, Vangelis Chaniotakis <haniotak@es.net> wrote:
Oh, speaking of globalreservationid!
we're only passing it around and persisting it not doing anything with it AFAICT.
- it's supposed to be a way to tie this connection with external services, right? - if so, the name is not quite descriptive of its function - it's also optional, while the name sounds terribly important - why a URI instead of a string? or key-value pair - there's only one of them, why not allow for a set?
It is supposed to be the ID for the global reservation. The aggregator NSA receives a request, generates an ID and uses this global ID to make connection requests to each of the participating NSAs. They generate a connection ID for their segment, but must be able to relate that to the global reservation ID. So yes, it does perform a very important global function :) It is indeed also meant for tieing in to other services. The URN is used to make it very clear that this is a network global reservation ID. Jeroen.