[Nsi-wg] Query types

[John MacAuley]

The summary query as defined returns the globalReservationId, connectionId, connectionState,  path, and some of the other reservation information.  This is fine for a Requester Agent that just wants to see the current status of the reservation.  Basically, it can determine the current state of the connection as understood by the Provider NSA.

The existing detailed query does the recursive traversal of the reservation tree with each NSA populating its view of the reservation.  Remember that each NSA has a completely different set of connectionIds for the overall reservation, which each NSA will put into the query response as it goes up the tree.

Your comment of the summary query being a depth=0 is true, and the detailed (recursive) query is depth=n where n is the number of NSA in the longest branch of the reservation tree.

When I say "Will query reservation detailed information held in the target NSA only.  This will include child NSA connection segment information (new connectionId, path segment, etc.) and the target NSA's version of the connection segment state." I do not mean a detailed (recursive) query of depth=1.  I still mean depth=0, but we want to return the connectionId information the provider NSA created when fanning the connection segments out to the children NSA.  This is not returned in the summary query, but is important if someone wants to walk the tree.

I could put this information in the summary query, but I thought keeping it lean would be  better idea.

John

On 2012-05-16, at 4:47 PM, Jerry Sobieski wrote:

> Johns
> 
> Why differentiate between a "detailed" query and a "recursive" query?  
> They return the same thing.   If you only want detail to a particular 
> level, then put a depth parameter on the Query so that it knows to only 
> go so deep recursively.   If you only want detail from a single NSA, 
> depth=0 (or 1 depending on how you want to interpret it).   The 
> recursion stops when the stack gets so deep.
> 
> Are you planning to walk the tree yourself?    The reason we defined the 
> recursive query was that the notion of walking the tree via independent 
> agent got roundly criticized in Salt Lake City - no one wanted to do 
> that.   People were upset that they would have to work to get path 
> information.  So we landed on a recursive query where authorization 
> would follow the same criteria down the tree and the whole result would 
> be returned with one pretty bow on it.
> 
> J
> 
> 
> 
> On 5/16/12 11:16 AM, MacAuley, John (John) wrote:
>> Peoples,
>> 
>> Can I propose we support three Query operation types?  Currently we have two (Summary and Details) or which no one has implemented the recursive Details.  I think we should revise the definition to the following:
>> 
>> Summary - Will query reservation summary information held in the target NSA only.
>> 
>> Details - Will query reservation detailed information held in the target NSA only.  This will include child NSA connection segment information (new connectionId, path segment, etc.) and the target NSA's version of the connection segment state.
>> 
>> Recursive - Will perform a recursive query to build detailed reservation information for all child NSA involved in the connection path.
>> 
>> Sound good?
>> 
>> John.
>> _______________________________________________
>> nsi-wg mailing list
>> nsi-wg at ogf.org
>> https://www.ogf.org/mailman/listinfo/nsi-wg