[Nsi-wg] Issue 49 in ogf-nsi-project: Missing information in detailed query?

ogf-nsi-project at googlecode.com ogf-nsi-project at googlecode.com
Wed Jan 25 05:51:30 EST 2012


Comment #6 on issue 49 by thost... at gmail.com: Missing information in  
detailed query?
http://code.google.com/p/ogf-nsi-project/issues/detail?id=49

I think the main lack is that in the stpList it is not possible to see  
which NSA is managing the segment. I.e., a segment from  
netherlight.ets:ps-83 to netherlight.ets:chi-82, can in theory be managed  
via the nordunet opennsa. Quite unlikely but possible. Not having this  
information makes it rather difficult to figure out the actual connection  
tree.

Furthermore there is the question of using URN or URL to reference to NSAs  
here. We cannot assume that a topology awareness is transitive, meaning  
that a URN reference such as urn:ogf:network:nsa:netherlight is not known  
at the querying client. Further we have no idea to tell if the client knows  
this or not, implying that we would have to use URL everywhere :-/.

Personally I saw three types of useful queries:

A: The state of the connection.

B: All locally available information for the connection (barring any  
security stuff). This is pretty much QuerySummary + managing NSAs for each  
segment.

C: Complete recursive information. Similar to the current QueryDetails.

A of course contained in B and C, and B in C.



More information about the nsi-wg mailing list