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@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg